And they are free to continue adding features and maintaining their preferred software choices. Nobody else seems to want to do it. IIRC the X11 maintainers are the same people who started Wayland.
> Once we are done with this we expect X.org to go into hard maintenance mode fairly quickly. The reality is that X.org is basically maintained by us and thus once we stop paying attention to it there is unlikely to be any major new releases coming out and there might even be some bitrot setting in over time. We will keep an eye on it as we will want to ensure X.org stays supportable until the end of the RHEL8 lifecycle at a minimum, but let this be a friendly notice for everyone who rely the work we do maintaining the Linux graphics stack, get onto Wayland, that is where the future is.
But we were talking about Wayland here. You're free of course to fantasize about hypothetical scenarios or propose features to software nobody wants to maintain.
Why don't you propose a protocol to solve the issues you have? If it solves a problem other users have it would get adopted I'm sure (except maybe GNOME).
I'm not a Wayland developer but it's what I observed in the issue tracker of my WM. A limitation is often overcome by a protocol and a basic implementation after. If you put the work in, the wlroots and KDE people are always very nice and will help you get started.
I guess that's my cue to leave front-end programming forever, and my current job (I'm not joking). I've been through too many cycles and it will never end. There's no way I'm staying for whatever crazy migration my company is going to go through again. And we have apps written in every single JS framework ever conceived. Time to learn COBOL.
And when they raise the price to 20x or start doing something shady you can just move everything to a cheaper and more ethical competitor. Except that you can't.
Very interesting. I wonder if there's a killer feature that would appear when you follow that line of thought. So even if adoption looks like 60~70% users and 30~40% enterprise, if you're indispensable to either of them, it would still prevent a take over because of the network effect. And the fact that you have an API that developers can trust would solidify the position even more.
If that feature ever surfaces I hope it doesn't involve blockchain or machine learning.
Honest question.
What's stopping Matrix from being adopted by, say, Google or Facebook, and then pulling a XMPPEEE?
Imagine Matrix gets really popular, more even than Discord. So they offer their own "version" but add features like free 250GB on Google Drive or things like that. After they get everybody on board they do what they do best and cease control of it.
> UPDATE - 14 Sep 08:03: Blizzard is investigating and they will be looking to overturn the bans if this is indeed the case. There appears to be at least five reports of bans so far and does indeed seem that the most likely explanation is a false-positive from Blizzard's anti-cheat technology having issue with DXVK.
So what you're saying is that money from a paid service going to Mozilla's pocket could be a new potential revenue stream? I can't believe nobody noticed that.
I don't think Firefox ever touches your user.js, I've never seen that happen or anyone complaining about it. And then it overrides prefs.js generated settings. The only time I encountered problems was with a big update failing to replace a couple of prefs.js entries, and it was some really obscure settings.
Don't get me wrong, I think MicroG is a great project and could work for many people. I already have to maintain a lot of Linux related stuff and I really don't want to worry about my phone too. The apps or workflow changes completely when you get rid of Google. I need to be able to trust that making the switch will be permanent, these things add up quickly (time). Death by a thousand cuts.
But if my phone fails it can put my job or even my life in risk. I can't affort to play cat and mouse with Google or the edge cases from and between MicroG and custom ROMs. I took a quick look at their issue tracker and it looks like these things still happen occasionally. As expected because no code will be good enough to fight malice in a platform you don't own.
Google already locked down Android pretty badly. Many important apps require the Play Store and all that Google stuff to be installed or to be fully functional (e.g notifications). MicroG is not enough for my needs and they introduce new things like SafetyNet to make things even worse. To me that's WAY more important than Google being installed by default or not. They can't lose until you fix this.
> https://blogs.gnome.org/uraeus/2019/06/24/on-the-road-to-fed...
> Once we are done with this we expect X.org to go into hard maintenance mode fairly quickly. The reality is that X.org is basically maintained by us and thus once we stop paying attention to it there is unlikely to be any major new releases coming out and there might even be some bitrot setting in over time. We will keep an eye on it as we will want to ensure X.org stays supportable until the end of the RHEL8 lifecycle at a minimum, but let this be a friendly notice for everyone who rely the work we do maintaining the Linux graphics stack, get onto Wayland, that is where the future is.
But we were talking about Wayland here. You're free of course to fantasize about hypothetical scenarios or propose features to software nobody wants to maintain.