Ftumch

I don't think that's the whole story. Like with all of their products, the primary goal of big tech here is to maximise engagement. More engagement means more subscriptions. People are less likely to keep talking to a chatbot that tells them they're wrong.

The situation would probably improve somewhat if AI companies prioritised usefulness and truthfulness over engagement.

Because your taste in music is bad and you should feel bad!

I'd argue ultimately most human conflict is caused by population pressure and limited resources.

Depends. If you use Google docs or the browser version of Office 365 (or whatever it's called now) you'll be fine. If you want to use an offline document editor, you'll need to be technical enough to understand the difference between file formats like doc, odf and pdf.

If you receive a doc file, edit it in LibreOffice and send it back, the recipient might complain that the layout has shifted slightly.

If you need to be absolutely sure the recipient gets the document layed out exactly as you created it and they don't need to edit it, exporting to pdf is a good option.

If you need to send or receive Excel/spreadsheet files you might have a bad time, I think. Though interoperability there may have improved since the last time I tried that sort of thing.

Before switching to Linux, download the Windows/Mac version of LibreOffice or OnlyOffice and see if it suits your needs. If not, it should be possible to run Office 365 on Linux using Wine or Winboat. However, Wine might not work or require too much tinkering for the average noob. Winboat should be more foolproof, but will increase the startup time of the application because you're running it inside a Windows VM.

Robot, experience this tragic irony for me!

I don't disagree and I definitely trust a Finnish company founded by former Nokia engineers a lot more than Google or Apple. But I think there is a lot of overlap between both the "buy European" movement and Fediverse users and those who prefer open solutions wherever possible. A lot of those people would prefer a solution where the userland and/or kernel and/or SDK is completely open source. They will have to weigh their options based on the fact that while SailfishOS is more open than Android or iOS, it is not fully open source.

By the way, it is also worth noting that unlike Google, so far Jolla has been moving in the direction of open sourcing more components of their OS. No one can predict the future, though, and some people would prefer to avoid any possible future vendor lock-in.

While SailfishOS seems neat, it's worth noting that some components, like some drivers, the homescreen UI, the compositor, some QML components and the Android compatibility layer are closed source. The rest of the software stack seems to be based on open source components from desktop Linux. The package manager uses RPM.

In 4D space-time, assuming light travels a fixed distance for every perceived unit of time, I think that would slow the speed of light over time. Since light would have to travel further along the t axis, it could cover less distance along the X, Y and Z axis.

Disclaimer: I am not a scientist

Dead satellites do add a much larger risk than satellites that can be steered, sure. If we stopped steering all our satellites right now, I believe it'd only take a few days before a collision occurred.

However, every satellite in orbit adds to the risk, especially if a chain reaction starts happening and it becomes very hard to avoid the shrapnel flying around. Or if a once-in-a-century-type solar flare takes out a bunch of satellites.

Edit: Basically, the best way to prevent Kessler Syndrome from occurring, is to keep the number of satellites in orbit below the threshold where it could occur.

Only a few minutes left. See you on the other side, guys!

There's another problem that nobody mentions. Putting thousands of additional satellites into space would seriously increase the risk of Kessler Syndrome occurring.

Better to use winget, though. That way you don't even need to bother with Edge's initial setup screens.