The requirement should be that any time an employer makes a demand of an employee's time, they pay.

FA waiting on your plane to arrive that's 6 hours late? Pay up.

15 Apple store employees lined up and waiting to get searched by a single manager after a shift? Pay up.

Require an employee to respond to phone calls or issues after hours? That's not "after hours", that's hours. Pay up.

Make an employee commute to an office for a job that can be accomplished from home? Believe it or not, pay the hell up.

Making demands of a person's time for a job is part of the job. They should be compensated for it.

Second. John Barnett was the first in early March.

https://knowyourmeme.com/memes/are-you-going-to-sleep

https://www.buzzfeed.com/maritsapatrinos/conversations-you-have-with-your-own-brain #4

It's exactly this. The policies put in place by "healthcare administrators" (MBAs and such with healthcare flavoring, not people that actually know how to care for people's health like doctors and nurses) are designed to process the most patience in the least amount of face time possible, so that each doctor and nurse can see more patients per day, meaning more office visit fees, meaning higher profit. My dad calls it the "cattle shoot" and I feel that's a pretty apt analogy. It's the same general reason that fast food restaurants and pharmacies and department stores are perpetually understaffed: fewer staff members means lower "overhead" costs.

Yes.

https://www.cnn.com/2024/02/23/us/alabama-ivf-embryos-supreme-court-ruling-legislation/index.html

This is called "Embrace, Extend, Extinguish". Microsoft coined the term internally for their responses to open standards in the 90's and 00's.

https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

Yes. I'm not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).

Nominally, a decent bug report should have:

• the steps that got you the bug
• whether you can reproduce the bug
• what you expected to happen instead of the bug

Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!

Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.

Lots of discussion here of Zed being macOS-only. Multiplatform support is being tracked in this issue for Linux, Windows, and web:

https://github.com/zed-industries/zed/issues/5391

Well, I guess I'll be disabling my Telegram account finally. The only thing left that I was doing on it was automatic notifications from the services on my home NAS. Not sure what I'll do instead. Maybe Matrix?

When has being ineffective ever disqualified someone from Congress?

... I started writing this reply to be funny, then I realized it's basically true, then I got sad.

Linking outside of their website would reduce engagement, thus ad revenue. I'd put money on this is why so many news sites rarely link out anymore.

Here's the list: https://en.wikipedia.org/wiki/Jus_soli#Unrestricted_jus_soli

If I'm counting correctly, 34 countries with unrestricted birthright citizenship, and 40 with restricted.

https://scp-wiki.wikidot.com/scp-2316

Edit: if you prefer TheVolgun read it to you: https://youtube.com/watch?v=dh_GCH7kc4Q

It's available in the API and in some apps. I'm using Memmy for iOS right now and I get both.

As I understand it, planning new, grid-scale nuclear power plants takes 10-20 years. While this isn't a reason not to start that process now, it does mean something needs to fill the demand gap until the nuke plants (and other clean sources) come online to displace the dirty generation, or demand has to be artificially held down, through usage regulation or techniques like rolling blackouts, all of which I would imagine is pretty unpalatable.

Yup. I was curious too.

https://m.imdb.com/title/tt1615550/

Friends don't let friends recognize the bodies in the water. ;)

Maybe now, but definitely not originally. Apple grew the Maps ecosystem originally for feature parity reasons, not privacy ones. That's at least a bit more similar to the Search situation.

Turn-by-turn was the killer feature back in iPhone 4S time frame, and Google refused to allow it iOS, shipping it only on Android. Apple had some geographic features (reverse geo lookup specifically, iirc) prior to this in-house and had started developing their own maps because of the longstanding tension with iOS and Android, but Apple rushed to get turn-by-turn directions out the door in mid-2012, which is partially what caused it to launch pretty half-baked. Google introduced a dedicated Google Maps app on the iOS App Store in late 2012 with turn-by-turn in response to losing millions of daily-active users to the launch of Apple Maps.

Here's a retrospective from 2013 by The Guardian on the whole thing with a lot more detail:

https://www.theguardian.com/technology/2013/nov/11/apple-maps-google-iphone-users

Now, Apple has run a web crawler since at least 2015:

https://www.engadget.com/2015-05-06-apple-web-crawler.html

Apple has been steadily building up its search expertise for the last decade. Notably, it acquired Topsy back in 2015, which was a search engine mostly based on Twitter data:

https://www.businessinsider.com/apple-shuts-down-topsy-the-200-million-mystery-laid-to-rest-2015-12?op=1

... then launched a few web-based Spotlight search integrations a few years later (which I can't find a good source for) which integrated common web searches for things like weather and news directly into Spotlight.

IMO, based on the above (and maybe a bit more), Apple's explanation in the article doesn't tell the full story. It doesn't want to build it, but it could. This is more is about Apple wanting to keep extracting the money from Google and not having to build another also-ran service to directly compete.

Yup. Some are doing well (like Microsoft with Halo, surprisingly...), others are actively denying doing anti-cheat on Linux. Here's the website to track them:

https://areweanticheatyet.com/

I have run Fedora for over a decade and switched to Bazzite a couple years ago for my desktop (Fedora still on my server).

In short, yes, but I wouldn't recommend it. You can learn what you need to directly on Bazzite. If you're looking for help, Bazzite is most similar to Fedora Silverblue (not regular Fedora) under the covers. The differences between regular Fedora and Bazzite are substantial enough that you'll run into some things you'd need to research twice, once for Fedora then again for Bazzite. Keep it simple and just use Bazzite.

If you want or need a distribution with a different focus, you should look at the other Universal Blue (ublue) options. Bazzite is built on ublue for gamers, but uBlue also builds for other use cases. Aurora for general desktop, Bluefin for workstation, and uCore for servers.

https://universal-blue.org/#images