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.

… hell, it’s on fire! ;-)

Well, at least they are consistent.

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.

Failing to provide the name of the person in the body of the email is incomptetence.

Fox included the disclaimer about contact email… but IMO the person who built the mail merge was incompetent and that will not prevent ICE from coming after Aldo.

Not if cheeto is hiring.

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

If you convert the chemical energy in a unit of coal to heat (burn it) you can calculate how much energy exists in that coal, measured in appropriate units (e.g. kWh). That is evidently what this author is trying to dumb down as “invested energy”. The amount of energy extracted as electricity is typically 40% of that… the rest ends up as heat which is much less useful than electricity.

I agree that this is not particularly useful in discussing the merits of different energy sources because good design tends to do as well as is practical and the supply of fuel and negative impacts of that process can’t vary dramatically.

This has always been a risk for artists working for powerful people. It doesn’t necessarily end well for the artist.

A policeman? is that unusual?

TIL. tho maybe TMI.

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.

Oh, my, what a surprise! /s

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.

As you add more compute per user interaction (“smart” features), you increase power consumption. To keep an 18hour discharge cycle, you have to have more battery. Since phone thickness is a negative marketing feature but increased screen size is a positive marketing feature, you end up with bigger phones.

Every time they reduce compute power consumption, feature inflation overtakes the gain and more power is needed over time. Try turning on battery saver in the morning… even with “normal” use the battery will last significantly longer due to disabling background power consumption.

So optimistically assuming that Trump will follow through.

Cops without oversight end up veering off course. Things can get worse.

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.

Oh! I know! I would have to first install them, roght?