Mechanize

Probably when you installed the second linux you overwrote the boot loader instead of adding a new UEFI entry point.

But I've never had a Mac, so take this with a pinch of salt, and honestly considering things can change based on what, in which order, and how you installed things.. it could be something else.

Unfortunately, in general, people tend to just read, vote, and then forget about it without checking back: that's why I always try to add some source or ways to verify what I post.

And - in this specific case - probably some people just like LTT, I assume.

Linus is an investor in the framework company: Source on the framework forums that links to the video on youtube

Currently they have direct shipping for some EU's members (Germany, France, Ireland, Netherlands, Austria, Italy, Spain, Belgium) Source

And I think the shipment costs are currently already in the price for the laptop Source

But I've not bought one so I don't have direct experience

Because, as pointed in the page, Servo is being developed as a(n embeddable) Rendering Engine, not as a full blown end user Browser.
Its alternatives are not Chrome, Safari or Firefox, but Webkit, Blink and Gecko

There's an example GUI called Servoshell, but it is more of a testing ground and example on how to embed the engine in an app than a serious alternative to anything currently in the market.

Already this kind of work is difficult and daunting. Adding to it a full GUI would make it completely impossible for the current size and financial backing Servo has.

Big words aside it just means that Servo wants to be only one of the parts that compose a real browser: the one that takes HTML, Javascript, WASM and translates them into the things you see on your monitor. All the user facing functionality are left to the devs of the app that embed it.

I feel there's some kind of miscommunication going on here.

Probably I'm not understanding what you are putting forward, but to be clear: They are not doing this because they want to. They are doing it because they are forced to do it by the DMA.
It's true that allegedly they were working on some kind of interoperability layer already. For years now. But no evidence of it being more than lip service to avoid being regulated has ever surfaced - as far as I know.

Which would have been in line with your "Do Nothing".

as an unwilling Whatsapp user the ability to migrate without having to convince all my social circles to do anything but check a checkbox sounds like a huge step forward.

That's the point. I feel it will not be a "simple checkbox", and they will make it the most obnoxious process they can using the Best Dark Patterns the industry has to offer.

Already the general public is not interested in the alternatives or the concept of interoperability - wanting something that Just Works™ - putting in front even the smallest step (and some scary text!) will make the percentage of willing people become even lower.
And that's not all. As it is portraited in the article by the Threema's spokeperson it is pretty clear that Meta will just try to make the maintenance of the communication layer as cumbersome as they can - both technically and bureaucratically.
They are explicitly the ones keeping the reins of the standard, the features, the security model, the exchanged data and who, how and when will be approved.

So from one side if they make it hard and scary enough to tank the use rate, they will have the excuse of not being there enough people to give priority to fix it or add features, and from the other side if maintaining the interoperability will be difficult and time consuming enough, the people and businesses from the alternatives or wrappers will not have the incentive to do or keep doing it for the long haul. As we can already see in the article.

Is it better than nothing? Sure, probably. Will it be a slow cooking, easy to break, easy to get excluded from, just bare minimum to comply to the letter but not the spirit of the law? I feel that's a pretty good bet to make.

Let's be clear: I will be extremely happy if all the red flags and warning bells that I saw in the article will just end up being figments of my imagination. But yes, I'm very pessimistic - maybe even too much - when I see these kind of corporate speech and keywords.

“One of the core requirements here, and this is really important, is for users for this to be opt-in,” says Brouwer. “I can choose whether or not I want to participate in being open to exchanging messages with third parties. This is important, because it could be a big source of spam and scams.”

Let me translate this for you: "We will make users hop on the most cumbersome, frustrating and inefficient way we can think of to enable interoperability. And making it defaulted to off will mean people using other apps will need to find other channels to ask for it to be enabled on our users' end, making it worthless.

And don't forget: we will put a bunch of scary warnings, and only allow to go all in, with no middle ground or granularity!"

Great stuff, thank you. I can't wait.

“We don't believe interop chats and WhatsApp chats can evolve at the same pace,” he says, claiming it is “harder to evolve an open network” compared to a closed one.

Ah, so they are going for the Apple's approach with iMessage and Android sms. Cool, cool.

I hope my corporate-to-common translator is broken, because this does just sound bad.

Let's go with a great classic:

Any foundation model is trained on a subset of common crawl.

All the data in there is, arguably, copyrighted by one individual or another. There is no equivalent open - or closed - source dataset to it.

Each single post, page, blog, site, has a copyright holder. In the last year big companies have started to change their TOS to make that they are able to use, relicense and generally sell your data hosted in their services as their own for the intent of AI training, so potentially some small parts of common crawl will be licensable in bulk - or directly obtained from the source.

This does still leave out the majority of the data directly or indirectly used today, even if you were willing to pay, because it is unfeasable to search and contract every single rights holder.

On the other side of it there have been work to use less but more heavily curated data, which could potentially generate good small, domain specific, models. But still they will not be like the ones we currently have, and the open source community will not be able to have access to the same amount and quality of data.

It's an interesting problem that I'm personally really interested to see where it leads.

Give technitium a go, my woes diminished drastically with that.