"On Linux under Wayland" is a big part of the problem. On X11 a significant part of missing "GUI-exposed-as-api" is present.
If we concede (and I think otherwise) that we need a FOSS operating system and desktop experience to be fully on par with competitors and offer agentic-first options, I think that an open-minded developer (or one that can afford to run a fairly good LLM on local machine), presented with the problem, can see evidently that said roadblock doesn't exist: X11 can stop being a maze, or thousands of Wayland apps can be forked to make them expose an API, the FUSE filesystem kind of API.
I don't care much about agents though, I sure see as potentially useful some desktop assistant, and that is that.
Wayland is a major regression for accessibility. People have been raising that for years, but always shouted down by the brigade with the motte-and-bailey seesaw between “Wayland replaces X11” and “Wayland is just a protocol”.
There's too much splintering in the community now and the incentive drawbridge for FOSS feels like it's closing. Many of the older maintainers who carried projects for decades are starting to step away due to age, burnout, or simple exhaustion.
It feels nowadays that if someone genuinely puts the effort into untangling a codebase, fixing the long-standing issues and navigating the maze of legacy paths, the backlash and politics around it leaves the project deflated and unappreciated. The reaction around Xlibre shows how hostile these situations can become. Personally, I still prefer Xorg in many ways, even if Wayland is technically the newer direction.
FOSS was a powerful ideological concept in the 90s when most software was proprietary and corporate-controlled. The 2000s felt like real growth and experimentation. Today, a lot of it feels fragmented, cynical, and increasingly institutionalized. Another problem with FOSS is that projects usually end up in one of a few states, a strong “dictator” model where someone drives the direction through sheer effort and resources,
a loose community model where everything gets patched together by committee or eventual corporate stewardship.
Or someone gets frustrated enough to fork a project, but then these forks are often treated socially as hostile when that was the core ideology of FOSS.
A lot of modern “FOSS” infrastructure are effectively: corporate-funded, corporate-prioritized or community-accessible rather than community-directed. It's free in the sense of that you can download the source, compile it yourself but for yourself to contribute unless you have the resources, is hard and time consuming. So you end up following the path it's taking.
If the corporations benefiting from these ecosystems consistently reinvested back into the communities maintaining them the FOSS landscape would look very different if not more healthier, more sustainable, and far less bitter.
The ofac is a list under the dept of Treasury. Bessent. So, it's one of those cases where the difference doesn't exist, if you say here Trump or "The project 2025 cabal" it's the same.
In the last years a market for "no code" software has sprawled, just etch the interface on a tables SPA, plug Okta, plug your backend or Firebase to their apis and you should be set.
You can also find dozens of drag n drop builders and block editors working for modern frontend dev, there are a lot for React for example, just vibe code the components.
So did I. I know Gemini the protocol exists, but the reality is, in almost every context "Gemini" is so much, much more likely to refer to Google's LLM that I'm taken aback when it doesn't.
I don't know about GTK (and frankly hope anything will be ported to something else and the whole GNOME project get nixed), about QT they recently implemented a QPA.
https://codeberg.org/vimpostor/qtarcan
That's a folk music wave, a conscious soul album, conflated with more pop social commentary. Not much protest songs. Products made out of popular discontent.
Now if you said Woody Guthrie... But in pre-war times was there a non-mainstream?
The only thing that this may say is that in USA the regime fights dissent in mainstream media. Like, if you want to catch signs of a product made out of popular discontent, you can't e.g. find in UK charts the Sleaford Mods or Kneecap?
In European nations who aren't English-first-language it's quite widespread around university students and people that outgrown Whatsapp, it isn't very much different than using a Discord groupchat (and you lose less important stuff in Telegram). Admittedly a bit is for network effect around "grindset" jocks but it isn't very much different than using discord or Meta messenger or Slack, just a freemium SaaS that the project doesn't support firsthand so if "our server" is down, "theirs" maybe is not.
I say they are all the same although Telegram's insecurity is proven, they still are the same overall for a FOSS project.
It's not so much about security, as FOSS conversation groups would be open to anyone anyway, but it's not a good look for a project to use a tool that is known to be quite shady while there are FOSS tools, or simply tools with a better reputation. Also the project group seems to be french, not english-first-language, and Telegram is absolutely not well seen in France, not used by much more than a few percent
If you say "shady" because CEO is a Russian in Dubai and for years nobody really knew how the hell could he sustain the company, yeah you're right.
About the FOSS alternatives you're right, but to use a closed source SaaS is just a choice people make because they are not confident in their own infra.
If it's "shady" because of cybercriminals, I insist in saying that it's the same than using Discord (pedophile rings) or Whatsapp/Meta messenger (extensive history of terrorists, gangs, traffickers of any kind).
It beats WA on UI in most cases (especially on desktop), has open source client, much better groups/channels for one-to-many, many-to-many communications. Has bots support like I never seen on WA.
>You are responsible for testing the code you write, not the one that actually runs.
Hipp worked as a military contractor for battleships, furthermore years later SQLite was under contract under every proto-smartphone company in the USA. Under these constraints you maybe are not responsible to test what the compiler spits out across platforms and different compilers, but doing that makes the project a lot more reliable, makes it sexier for embedded and weapons.
Nah, libxslt is a spinoff of Expat, at the very least (and mozilla mantains its own xslt library) there's a full implementation by the standard writer called Saxon[0]
I don't care much about agents though, I sure see as potentially useful some desktop assistant, and that is that.
reply