One could make the same argument to enforce company-wide return to office on grounds that work from home represents lost opportunity for serendipitous conversation around the microwave. If you want Serendipity, look up Stephen Cosgrove.

OTOH, you can quiet quit or just ignore the policy and force HR to either pay severance or run around collecting paperwork to fire for cause. If the latter, look out for the lawsuit alleging (probably factually) that the whole thing is a constructive layoff.

Or they were raised in a polite world where you are expected to hold the door if you know someone is right behind you, not just walk through and let it close like an animal. The last thing the world needs is more policies training people to have main character syndrome.

The manager that didn't set up an employees only chat roulette server?

It'll never happen because the law favors big capital. If the new owner wants to leverage it, they need to either honor the original deal struck with buyers or do a full buy-back.

Full release of technical documentation including source should be a requirement of bankruptcy.

A tablet with its official keyboard sold separately tends to be more expensive than an entry-level laptop.

Several American public schools are experimenting with making the introduction to computer science course a requirement for high school graduation. (See "Should High Schools Require a CS Course Before Students Graduate?" from July 2023.) If the operating system of a tablet is inadequate for a student to complete a course required for graduation, that makes the tablet less valuable to a high school student.

They knew that a broken BRCA2 increased the risk of cancer. The missing link was that high glucose leads to high MGO which inactivates BRCA2.

They started with cells where one copy of the gene is bad in order to more easily see any effect. It is quite possible that given a bad enough type II diabetes, the same effect can happen even with 2 good copies of the gene.

Nor is Pillow Python. However, Pillow routinely has significant changes from one major version to the next. Installing a newer version of Pillow than some system package expects could easily break that package. (This is why PEP 668 happened.) Likewise, installing from source a newer major version of a library than some C program expects could break that library.

HTTP has the "If-Modified-Since" request header, which instructs a server to process a request only if the requested document has changed since the provided date. It also has the "If-None-Match" request header, which does the same thing for "ETag" values.

(I did not use the <code> element in this post where the HTML spec states that I should have because Slashdot issued a diagnostic "Filter error: Invalid HTML tag usage".)

I don't understand how C is any different in this way. SDL major versions 1, 2, and 3 all have serious breaking changes.

Gnome might not be the best example. At least TWO distros were inspired by the desire to avoid Gnome shell. At least one to avoid SyetemD. Linus had to yell at the SyetemD people to stop them from crapping up the kernel.

The recent debacle with the xz based security hole explains well why Debian likes to think twice about updating package versions.

We need to anounce the coming of the salt shaker to get those slugs moving.

Until they use their tablet to browse the website of the game they want to buy and see "Linux and Windows: Buy Now / Consoles: We are seeking a publisher." A newly established indie studio's games aren't on consoles until the console maker approves a studio's request for a devkit. That in turn doesn't happen until the studio brings two or three games to market on a competing platform, which usually ends up being Windows.

And write long-form articles for a website on what? Learn concepts of computer science on what?