For the same reason I think software developers have the right to choose to release under copyleft, I think they have the right to release under SaaS or copyright. I don’t think it is fair to take those rights from them. (I may choose to avoid SaaS or other proprietary models where possible, but I am not pure about it… I just do so recognizing that proprietary tools are a band-aid and could become unusable when any upgrade or TOS changes.)

As one example, keep in mind that some governments may choose to punish a software developer for making “offensive” (by whatever their standards are) content, and rather than fighting a losing battle in one jurisdiction so you in some other jurisdiction can keep using that controversial software the developer may just choose to cut their losses and turn it off for everyone. If you force them to release it anyway then said punitive government may continue to hold the developer responsible for the existence of that software.

There are rights and responsibilities associated with a proprietary model… and IMO you (and your permissive government) should not be overriding those rights for your own short-sighted benefit.

A) this issue applies to all kinds of software.

B) procuring software is a two-way street … the producer assigns terms by which access is obtained, and you agree to those terms in exchange for that access. If the software is SaaS then if the producer chooses to shut down the service then you are SOL. If the software is provided with a long list of terms via Steam, then you are basically buying SaaS with local caching and execution. Maybe don’t reward producers by agreeing to one-sided deals like SaaS?

This kind of headache is what prompted Richard Stallman to come up with the idea for the GNU license. Maybe you think that is too radical… but maybe imposing your ideas of what licensing terms should look like on (only?) game developers is radical also.

They are a record of the process of adding to the Linux kernel. Such background can be used to trace the history of contributions if those contributions turn out to have had malicious intent or were derived from code that came from sources that were not compatible with the GNU license that the kernel is released under.

Samsung and Pixel, but various earlier models with micro-USB also. The plugs on my nightstand chargers have also tended to loosen up over time, but since I don’t unplug those as often they don’t seem to be the weak link.

All my old devices become un-chargeable due to USB-C plug wearout. Even with wireless charging I cannot avoid sometimes needing a wired full charge.

Just a note: Windows software for controlling hardware is highly likely to assume a)direct access to the hardware (sometimes mediated thorough ancient APIs and assuming the existence of defunct expansion slots) and b) assume meatspace time can be counted using OS timing ticks (which get stretched out as modern VMs timeshare with other processes underneath the virtulized hardware). It is awfully tough to replace them sometimes.

Stick with Windows. Microft will deliver paradigm shifts and you will have no say in the matter. They are already removing options for disabling Copilot, and for all the promised backward compatibility they are letting go of features that lots of old Windows software depended on, as they introduce features similar to ones in Linux. I cannot really fault them for all of these changes, but the difference is actually one of choice and privacy, and not really the one you seem to think it is.

It is not recursive though. A directory is a special kind of inode that enumerates file inode numbers and when that list changes then the contents of that “directory inode” change. But if /home/user/.bashrc is deleted then the timestamp for /home will not be affected because the timestamps are associated with inodes rather than directory entries (assuming no symbolic links are involved).

https://www.redhat.com/en/blog/inodes-linux-filesystem https://en.wikipedia.org/wiki/inode

Just to second that, the model series is Latitude, not Inspiron. and yeah, the i5 processor options I got over the years beat the i7 on processing power. The Precision models are a step up, but not any kind of low cost and seem not quite as tough.

Maybe if enough people file feedback on the name change they will reconsider. At least they will have a glut of feedback to deal with.

Bash is always there, and bash scripts and snippets are precise. Describing gui manipulations when the GUI keeps changing is also quite hard… what if the person you are interacting with has a 2-yo system and you have the bleeding edge? Even knowing which menu the settings are in can be frustrating for the helper.

Windows users (e.g. me at work) get grumpy when Microsoft starts changing the menu structure after keeping it consistent for 20 years and start thinking of powershell scripts to create consistency between our engineering workstations.

They are text files. If there is anything weird about them it is that they are indented with spaces and if you are inconsistent with indentation they won’t read into the yaml import function, but I can’t imagine why vim or nano would have a problem with opening them. Maybe the ones you were using were not actually yaml.

Totally lost me. Why the hate on YAML?

This is a false equivalence. The content of the art discussed here has no labels or logos. As soon as you posit the existence of such content, IMO you are in a different conversation.

I stopped buying phones from carriers 15 years ago for this very reason.

Stumped? This [theorem]https://en.m.wikipedia.org/wiki/Pythagorean_theorem) is a contender for most different proofs.