Everything was simple and straightforward except for updating an app after new release before the distro maintainers updated it in repos (which often took months).

Have you thought about why Switch is the best selling console in the current generation even though it’s by far the weakest in performance?

Who cares what OS the AWS machines are running? I can’t touch it, it’s completely inaccessible for me and other clients. I can only touch the services which AWS provides. I wouldn’t know the difference if it was running windows, since the OS is completely transparent, basically a hidden implementation detail.

You keep making the assumption that AWS == EC2, meanwhile it is just one of many services AWS provides.

Abstracting away is costly. You can target only the lowest common denominator. The abstractions are going to leak. It’s like the criticism of ORMs, only worse since SQL is at least standardized.

Too bad that Purism’s stated values are the opposite of their real business practices.

I don’t know iMessage, but some of the more advanced features in WhatsApp/Messenger are great. I use shared location almost daily, voice messages are great too.

Does anyone know what level of interoperability is required? Like basic text, pictures, emoji… or every feature including things like location sharing?

Impossible in the timeframe. There’s a reason why ASML is the only producer on this level.

I’m in a golden cage where my job earns about twice or more of what a large majority of remote jobs offer (available where I am, which is Europe).

I guess I could get very lucky and find a great paying remote job, but I feel like I could lose in the end.

People still want the money, tho. It’s the main reason I’m staying in my no-remote job.

I’m curious where did they get those numbers. Producing a limited number of chips is one thing, scaling to tens of millions is another. Especially regarding the lithography machines which China bought before the sanctions from ASML, but can’t buy anymore.

Programs shouldn’t get confused since RAM/swap is transparent for them.

RabbitMQ is more expensive on AWS than e.g. SNS/SQS. It’s not a coincidence, you’re trading lock-in for a cheaper price.

The increased complexity comes from the fact you will need some components which exist in either managed, but vendor lock-in form, or you need to spin them up / managed yourself.

Being cloud-agnostic also means additional cost/complexity.

Sometimes the only way to win the game is by not playing it.

I used GNOME for close to 20 years, but finally dropped it with the release 40. I’ve had enough of them breaking features.

By that time KDE finally stabilized and it does everything I want, my way.

The biggest issue was the phone - Librem 5 - many customers waited 4 (or 5?) years and what they got was underwhelming. Purism originally provided “refund anytime” policy, but once customers started using that they lied they didn’t promise that (disproven with wayback machine). The only reliable way to get the money back is to sue them in small court. They also had some other shady stuff.

I have a small app on the play store. It’s finished, has a small user base and doesn’t really need updates.

But I’ll now let google delist it. The API level isn’t even the main reason, it’s the other X warnings which jumped at me when logging into developer console about new rules and guidelines I need to satisfy. I’ve had enough of the hamster wheel.