

I am sure that will stabilize the economy. /s
I am sure that will stabilize the economy. /s
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.
This is th trouble with rule-by-self-interest… eventually different people’s self interests clash. Now what was the solution in the constitution? oh, yeah, rule by laws… but that clearly didn’t work… /s
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.
maybe something like https://a.co/d/9eG6erY
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
On average maybe, but no individual is average and Lenny is growing.
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?
Agree. For clarity, the circuits that show the low-voltage status are much less hungry for current than the circuits that measure weight. So no, having enough battery to report low voltage does not imply that there is enough to make an accurate weight measurement.
the ones that lost? those generals?
When you come across some Python code for something written 5 years ago and they used four contributed packages that the programmers have changed the API on three times since then, you want to set up a virtual environment that contains those specific versions so you can at least see how it worked at that time. A small part of this headache comes from Python itself mutating, but the bulk of the problem is the imported user-contributed packages that multiply the functionality of Python.
To be sure, it would be nice if those programmers were all dedicated to updating their code, but with hundreds of thousands of packages that could be imported written by volunteers, you can’t afford to expect all of them them to stop innovating or even to continue maintaining past projects for your benefit.
If you have the itch to fix something old so it works in the latest versions of everything, you have that option… but it is really hard to do that if you cannot see it working as it was designed to work when it was built.
bit of a cutthroat way to characterize what you “like”. Might actually make the interviewer downvote you for threatening their position.
Having used the web version of Office at my job, I know I would not pay for it. It is compatible-ish, but severely lacking in features, enough so that I don’t trust it to render properly or maintain the formatting entered using the desktop app. If that is good enough then there are lots of alternatives.
There are thousands of programs for Linux… but you should be warned that relatively few programs run natively on both Windows and Linux. In some cases there are ways to run “Windows programs” on Linux, but in general such successes are special cases. If you absolutely must have Windows you can run it in a virtual machine… but you will most likely be happiest with Linux if you aren’t chasing after such things.
I use Windows for work because our IT department only supports that… but I use cygwin and wsl to get a smidgen of my familiar Linux tools that I use on my personal computers.
IDK… that word checks out in this case.