X.Org is dead already. You all just don't know it yet.
Indeed. Just like BSD!X.Org is dead already. You all just don't know it yet.
And World of WarcraftIndeed. Just like BSD!
WPF is open-source but is kind of deprecated (in typical Microsoft ways, similar to VB6)
In terms of enterprise (stuff that keeps things ticking), .NET/WinForms doesn't quite have the same market penetration as Java/Swing. KDE is of no real relevance for the industry.
I'm surprised Wakefield is taking so long for Wayland to be honest. Linux is a key platform for Java, alongside AIX, Solaris and other classic commercial UNIX.
I think that would be a good approach. I am surprised that no API / abstraction libraries for X11->Wayland have appeared. Perhaps with more time. Weirdly Wayland is *still* in the market penetration stage.Maybe some brave soul could spin off Weston into an API based compositor as a drop replacement in for the swaths of existing X11 WMs on FreeBSD. Who wouldn’t want a stable API/ABI to develop on? That’d be interesting.
Works just fine here.https://x.org seems to have disappeared https://mastodon.decentralised.social/@wezm/114386105983566716
We depend, but to the least extent. Linux today is fragmentation. Corporations fight for the crowd. They don't need individual freaks. Any bank fights for the crowd. Any social network fights for the crowd. They need the masses. From the masses - profit. There are also hipsters. These are the people of the system. This is a glossy youth subculture. They also get their profit. But it is impossible to ignore Wayland completely. This is not an ecosystem that is alien to me today. Wayland does not yet have a corporate core. I am not an expert, but I did not notice that Wayland poses a threat to us. Correct me if I am wrong.Now big corporations are funding and steering Linux, Wayland and systemd and as with the likes of Microsoft, it's all about manipulation and coercion : "software XYZ is EoL, it won't be supported, bugs won't get fixed" etc. In short - free software developed with a corporate mentality and corporate money.
Yes, that's for sure. But our task is not to miss the "moment". I look and see that the work on promoting Wayland is going quite successfully, despite the second-order problems.link seems to be aimed at Gnome Fedora users.
Thank you. You understand the essence of the "money-people-services" movement well. And you described it well. Moreover, briefly and clearly. But speaking directly on the topic, I draw conclusions for myself: in 3-4 months, I will be crawling from X to Wayland. Moreover, I consider sway and other tilings to be more promising WM than traditional, stack ones. The paradigm of the classic desktop is no longer relevant for me. I am already designing a rigid pragmatic and minimalistic machine for myself. I am not saying that I am not a user of the "desktop" concept. But these things: X, GNOME, KDE and XFCE, have become fat. On forums people write that even LXQT DE has become fat and unwieldy...It is better to break yourself and reconfigure today than to run with suitcases along the platform with sweaty armpits, catching up with the train...A big promising thing is jails. An important topic is launching and working of the browser in jail. And then we'll see.It's never that simple to see clearly where money comes from and whos money is going where.
Then we will fix the abstraction layers. No-one will write code directly for Wayland (just like no-one writes code directly for X11 these days). Gtk, Qt and things like that will always be able to have X11 support. Just like they will always support Win32, Cocoa, etc.Thanks for the article. But they can also "teleport" basic user programs to Wayland. Then we won't be able to use anything under X. And FreeBSD programmers won't do it. What to do then?
You can always patch X11 support back into Gnome, right ?Sure, the Gnome people might threaten to do it as a way to push Wayland whilst it is struggling to gain a foothold but ironically, its not actually up to them.
Sure, the Gnome people might threaten to do it as a way to push Wayland whilst it is struggling to gain a foothold but ironically, its not actually up to them.
We don't really care about Gnome. But the Gtk project is now under their umbrella. That is the one to reinstate X11 support if they ever stop maintaining it.You can always patch X11 support back into Gnome, right ?![]()
Strangely I do maintain a fork of Gtk2 (that sits ontop of SDL2 for some graphics related simulations). Yes, it was a fair amount of work but luckily X11 support is already in Gtk3+, all we would be doing is reverting their breaking commit.Unless someone decides to fork gtk2, who's going to maintain it here? The committers aren’t going to bother touching GPLd code outside of drivers. The toolkits and apps are whats at stake here, less so DEs. its either fork the toolkits or write our own Wayland backend for them and browsers.
I think these are a good example. The sheer volume of very complex patches required to currently build these browsers, absolutely dwarfs what X11 needs for it to be supported inside Gtk. It shows that it will get done. Its not like we all need to support ALSA for our audio, "just coz Linux does" right? Why should graphics be any different?Firefox/Chrome (who are RedHat loyalists) decided to stop future X11 development, FreeBSD is pretty much screwed.