zlacker

[parent] [thread] 19 comments
1. jorvi+(OP)[view] [source] 2026-01-26 17:49:40
The way out of this hole is by the EU mandating a 5, 10 and 20 year plan for getting off US tech and pivoting to open source.

Start with a target small municipality in each country. Switch to SUSE (with a desktop that supports Active Directory), Collabora and what not. Then switch the mail stack. Then the files stack. Etc.

Next step is scaling it up to a small city, then a big city, then a province, and finally the whole country.

Parallel to this you do the universities and militaries.

The beauty of this is that the untold tens (hundreds?) of billions € in Microsoft / Google / Amazon support contracts will now instead flow into open source support contracts. Can you imagine the insane pace LibreOffice would improve at if a few billion € in support contracts was paid to Collabora each year?

One thing the government would have to resist is thinking that open source is 'free' and that they can cut their yearly spend on digital office stuff to the bone.

replies(5): >>McDyve+C1 >>theweb+g7 >>omnimu+6g >>SirMas+Jq >>youngt+s31
2. McDyve+C1[view] [source] 2026-01-26 17:56:27
>>jorvi+(OP)
I see a "top-down" approach, actually.

Government and public services change to (ideally) open source, and "impose"/"require" downstream compatibility.

This would create the incentive and make change easier

replies(1): >>Vespas+291
3. theweb+g7[view] [source] 2026-01-26 18:19:58
>>jorvi+(OP)
> The way out of this hole is by the EU mandating a 5, 10 and 20 year plan for getting off US tech and pivoting to open source.

I agree. All this hem and hawing will not get them anywhere, and will just have Microsoft again dropping bundles of money at the foot of officials to "pretty please don't switch awawy."

Mandate it, top down, make it law, then officials have the legal mandate to fall back on to tell Microsoft and the others to pound sand when they come knocking with the briefcase full of money.

4. omnimu+6g[view] [source] 2026-01-26 18:59:16
>>jorvi+(OP)
The problem is that european politicians don't want to kill the tech $$$. They just want to bring the revenue home. They don't understand that they will never make EU big tech and that their only feasible path forward to get rid of US tech is also the path that kills the goose.

But that process is inevitable, it's already happening. What is not inevitable is hardware sovereignty. If EU doesn't have some form of hardware independence then they might just end up forced to use the US software stack.

replies(2): >>jorvi+Vt >>pbmons+8v2
5. SirMas+Jq[view] [source] 2026-01-26 19:52:31
>>jorvi+(OP)
Good luck getting the EU off Android and iOS?
replies(2): >>Epa095+as >>tdrz+0C
◧◩
6. Epa095+as[view] [source] [discussion] 2026-01-26 20:00:08
>>SirMas+Jq
It would take Samsung (or what's left of Nokia) a whole 10 seconds to produce a Google-free phone based on the Android Open Source Project (AOSP) if there was a market for it. Which it might soon be.
replies(2): >>SirMas+QC >>palata+i42
◧◩
7. jorvi+Vt[view] [source] [discussion] 2026-01-26 20:09:47
>>omnimu+6g
> If EU doesn't have some form of hardware independence then they might just end up forced to use the US software stack.

In a multipolar world you don't critically need that if you can order your hardware from party I when party C or U shuts you out.

Remember that China is running their own Android island with Huawei and Xiaomi. Yes, a lot of Chinese people flash the Play Store, but it isn't strictly necessary. Not hard to imagine the EU and India creating their own islands too.

Kind of wicked we have to think this way though. I much prefer a world with the maximum healthy amount of open trade and travel.

◧◩
8. tdrz+0C[view] [source] [discussion] 2026-01-26 20:50:27
>>SirMas+Jq
There's /e/OS, a fork of Android
replies(2): >>bigyab+aC >>palata+t42
◧◩◪
9. bigyab+aC[view] [source] [discussion] 2026-01-26 20:51:09
>>tdrz+0C
Also Sailfish, which supports running Android apps: https://en.wikipedia.org/wiki/Sailfish_OS
◧◩◪
10. SirMas+QC[view] [source] [discussion] 2026-01-26 20:54:15
>>Epa095+as
So AOSP would survive fine after stopping taking in new code from Google?
replies(1): >>Epa095+mS
◧◩◪◨
11. Epa095+mS[view] [source] [discussion] 2026-01-26 22:16:05
>>SirMas+QC
What scenario is this?

If AOSP is suddenly the only acceptable smart-os on phones for 600 million people, I think it would work out yes.

replies(1): >>SirMas+KL2
12. youngt+s31[view] [source] 2026-01-26 23:10:32
>>jorvi+(OP)
Given how software is largely delivered via SaaS models these days, I'd start with a Chrome OS competitor as a client

And then build out Google App suite, Office 365 exquivants

◧◩
13. Vespas+291[view] [source] [discussion] 2026-01-26 23:43:58
>>McDyve+C1
Yeah "all bids for government contracts must" is a really powerful sword.

It pushes money into the market, creates skills and business and, crucially can look beyond quarterly profits (for better or worse).

replies(1): >>carlos+2y1
◧◩◪
14. carlos+2y1[view] [source] [discussion] 2026-01-27 02:52:50
>>Vespas+291
Yes! We must mandate that all loyal citizens have to use Arch Linux and Vim. Severe punishment and long prison terms for any other distro or text editor.
◧◩◪
15. palata+i42[view] [source] [discussion] 2026-01-27 08:12:30
>>Epa095+as
They "just" have to make a phone that can be supported by GrapheneOS.
◧◩◪
16. palata+t42[view] [source] [discussion] 2026-01-27 08:12:57
>>tdrz+0C
And GrapheneOS.
◧◩
17. pbmons+8v2[view] [source] [discussion] 2026-01-27 11:28:47
>>omnimu+6g
> The problem is that european politicians don't want to kill the tech $$$. They just want to bring the revenue home. They don't understand that they will never make EU big tech and that their only feasible path forward to get rid of US tech is also the path that kills the goose.

Not necessarily. Red Hat is a billion dollar company just on FOSS support services and consulting. And if you put hundreds of thousands of clients on a completely novel FOSS stack, you're going to need several of those.

◧◩◪◨⬒
18. SirMas+KL2[view] [source] [discussion] 2026-01-27 13:22:52
>>Epa095+mS
Isn’t that the scenario in this post? Cutting all ties with US companies. So they would stop using code written by Google. Isn’t most of the AOSP code written upstream by Google?
replies(2): >>Epa095+Og3 >>jorvi+Mx4
◧◩◪◨⬒⬓
19. Epa095+Og3[view] [source] [discussion] 2026-01-27 15:47:22
>>SirMas+KL2
That might be, but with hundreds of millions of paying customers there is a market, and it will be filled. Maybe by some of the tens of thousands of European developers currently working for Google in Europe, or the other American companies.

Continuing a already existing open source OS is far down on the list of challenges.

◧◩◪◨⬒⬓
20. jorvi+Mx4[view] [source] [discussion] 2026-01-27 20:50:02
>>SirMas+KL2
AOSP is mostly licensed Apache and LGPL. The repos have probably been cloned a million times. Although Google has taken large swathes of the project (like the launcher or Settings app) behind closed proprietary doors. But that is not a huge obstacle, there are already plenty of decent open source launchers.

The most important thing would be a (drop-in) alternative for Firebase Cloud Messaging. Without it, you can say bye bye to any decent battery life.

[go to top]