• 0 Posts
  • 59 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle

  • bisby@lemmy.worldtolinuxmemes@lemmy.worldlow effort maymay
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 days ago

    The thing I hate about the “value your time” argument is that windows is shit.

    Let’s be generous for a minute and assume that windows and linux have the same amount of problems. Someone who is on windows for the past 30 years has 30 years of acquired knowledge and will probably know quickly how to solve it on windows, but not linux. Someone who is on linux for the past 30 years has 30 years of acquired knowledge and will probably know quickly how to solve it on linux, but not windows.

    So the entire argument is just “but I have muscle memory tied to windows, and I already know how to solve those problems, but I dont know how to solve the linux ones, so they take me a lot of research and time to solve, therefore all linux problems always take a lot more time to solve”

    On windows, I have to spend time fighting BSODs and finding out where to download software from that isn’t just bloated up with viruses, and how to run registry hacks to get rid of start menu ads and to stop microsoft from phoning home. None of those things i have to do on linux.

    On linux, today my biggest issue was figuring out how to change the keybinding for taking a screenshot… And that was an easy issue, but it’s also not even possible on windows.

    So I guess different types of problems. My “wasted” time is customizing my OS/environment so it works the way I want it to, not trying to fight back any ounce of control.


  • Sure. but there are plenty of reasons to not read other than “uneducated”. And associating ability to focus with intelligence and education isn’t fair either.

    If an American couldn’t tell me how many states there are, I would question their intelligence or education.

    If an American told me that they don’t read books, I would just assume they find books boring.






  • IMO it doesn’t matter. People don’t read news on updates. Should they? Yes. Do they? No. Should they have to? Also no.

    Linus’s point is to never blame the end user for something the kernel changed. If you want software to have widespread adoption, adding homework to simple updates isn’t how you do it. People don’t want a hobby or something to babysit, they want an operating system. Debian will go out of their way to make in-release updates go as smooth as possible, but are willing to through out entire parts of functioning packages between releases.

    But this isn’t even about breaking things for the end user. This will create excessive amounts of noise on the upstream repo. People will say “Hey! My keepassxc broke!” and they report it to keepassxc, and not to Debian. To which keepassxc just has to constantly reply “no, debian changed this on you, this is not a bug.” If Debian had to deal with the fall out of their own decisions, I would say “yeah, im not sure if i agree with the decision, but oh well”… But they are increasing the workload for other teams.

    It is already happening. The debian dev’s stance is “This will be painful for a year.” But it will be painful for keepassxc, NOT debian. The keepassxc devs asked them to not do this. Debian’s response might as well be “Im inflicting this pain on you, even though you’ve asked me not to. But on the plus side, it won’t hurt me at all and it will only last a year for you.” If they really have that much disdain for the project, they should just stop packaging it altogether.

    So yeah, debian has the legal right to do whatever they want because keepassxc is open source. but “just because I can, and you cant legally stop me, and its extra work for you, not me” is kind of a jerk move. This is what drives FOSS contributors to get burnt out and abandon otherwise good projects.


  • It’ll also break all your keepassxc plugins soon. Because debian version to version compatibility is not a priority. They also don’t care if them breaking something triggers a ton of upstream bug reports, because it will only “be painful for a year”

    Linus for the kernel has a strict “don’t break userspace” policy, and Debian has a “break things whenever you want, and just blame the user for not reading the news file” policy.


  • Definitely make sure you think through all the physical security implications of having your house automatically unlock in any scenario.

    Have the house auto unlock when getting home on a bicycle, sounds convenient until, as you point out, they could get stolen and now the thief has a convenient way to unlock your house. So you would not want that.

    You would definitely not want the house to STAY unlocked when something like a tag is in range. If your kid is home alone, you want them to be able to re-lock the house (or in general, you want to be able to lock your house while the kid is home).

    Whatever solution you wind up with, you are going to be trading physical security for ease of use (and complicated fun task). Be safe. Make sure the tradeoffs are actually thought through and worth it.




  • I use wayland, but be warned that there are downsides.

    X11 is 40 years old. Which means that even though it has 40 years of bad decisions baked into it, it also has 40 years of features and tooling built around it.

    And in some cases, things are purposefully broken in the name of security as mentioned above. Writing a keylogger on X11? Easy. Every app can watch the keyboard even when they aren’t in focus. So if I type my password into firefox, Discord can listen. Hope you don’t have any malicious apps just patiently listening to all your keystrokes.

    Getting rid of input listening sounds great! … Except for the concept of global keybinds. Have a Push to talk button in discord that you need it to be able to listen to while youre playing a game? Sorry, the game is in focus, so discord can’t see ANY of your input. Including the push to talk button. Different wayland servers have different ways of handling this with their portals. Some don’t have it at all. And the ones that do don’t always have great solutions.

    One major issue that has been in wayland debate hell… how do multi-window apps communicate with each other. For example GIMP. The editor window is a separate window from the toolkit which is a separate from the layer view. GIMP on X11 knows where all of its windows are because it can see everything. if you wanted GIMP to save all the window positions, it could. GIMP on Wayland has no idea where each window is relative to each other. Each window knows its own size and shape. And thats it. It doesnt know where on the screen it is. Which means it doesnt know where it’s other sub windows are relative to itself. Which means GIMP on Wayland can’t really save the window positions for next run. Wayland is working on a protocol for handling this, but its been caught up in debate hell last I saw. This is a prime example of a thing X11 had. And Wayland will someday have, but the 40 year headstart and disregard for security gives X11 a huge headstart.

    Most of these problems have workarounds and solutions, but you might find yourself in a situation where you do in fact need to implement a workaround instead of having everything Just Work.

    “Better” means different things to different people. Architecture and security and technologically? Wayland is better. Just Works and its what your apps were probably built to run on so less weird edge case issues? X11 is still better just due to inertia. (And again, I use Wayland, I’m willing to deal with the workarounds, but you do you).


  • The most commonly cited monitor in recent years for this is “AW3423DWF”… Which is AlienWare 34" (no idea what 23DW is) Freesync. I assume the 23DW has a point to it too.

    Point is, people see a lot of characters and complain when in reality it is exactly what you are referring to. The name is an encoded version of its capabilities. Its just that the encoding isn’t always clear because if every company used the same encoding they would have the same name. and if there are 2 similar monitors you would need to have every feature in the name to differentiate them, so the shorthand encoding becomes necessary. (Eg, AW3423DW and AW3423DWF only really differ on freesync vs gsync, thus the F at the end)

    Edit: W is for WQHD: 3440x1440



  • A spectrum is usually drawn similar to the one on the left. But the point of a spectrum is that its not “where on the spectrum are you”… It is not one point on the spectrum. As drawn on the left, the spectrum represents possibilities. Normally a spectrum would be drawn to indicate how much of each possibility a thing covers.

    Eg, the spectrum for light emission of a lamp might be :

    Which means it has a bit varying of every color but is heavily green and orange, but probably looks just like white to the naked eye. Swap “green” for “language” etc and you have a spectrum.



  • Its enough for me too. But not everyone has the same use case and environment. I definitely see why someone would want this.

    What I disagree with is that it needs to communicate to the internet to do this. It adds delay and potential for outage if your internet is out. But they do this so they can force you to get their app and milk you for extra data to sell. Internet capable smart devices are to harvest data not grant features. Features could be done better by ZigBee and a hub, but that doesnt grant the device a way to phone home