> No, it never was intended like that. That some people build infra/business around it is something completely different, but swarm was never intended to be a kubernetes contender.
That would be news to the then Docker CTO, who reached out to my boss to try to get me in trouble, because I was tweeting away about [cloud company] and investing heavily in Kubernetes. The cognitive dissonance Docker had about Swarm was emblematic of the missteps they took during that era where Mesos, Kube and Swarm all looked like they could be The Winner.
remember when you agreed with me that it was maybe regretable that the Favorites space was removed in favor of a process that required multiple clicks? and now it's months later and Element still has this redesign shipped, with every single one of the original flaws mentioned, still present.
I think Matrix has a lot of smart people involved, and I can't believe I'm saying this, but dear god, are you hiring for a TPM, by chance?
Every, single, time I have to go "Home" -> "Expand" -> "Favorites" to do what used to take one click, I lose a bit more faith in Element/Matrix.
Though, y'all did finally fix the notification sound that made me want to kill myself every single time it violated my ear drums. Only took.... 4 years? for that?
What were meant to be fast-follow fixes to the new left panel after it shipped in September ended up getting starved out by deadlines for paying customers, frustratingly. The work is happening now however.
It blows my mind how many stories hit the front page, every day, that bottom out on whining about proprietary software. I've literally been talking about the Win10/11 whining for 3+ years, and yet EVERY. SINGLE. WEEK THERE ARE MORE.
Lawnchair is *EXCELLENT*. I say that as a former Nova Launcher user. And Lawnchair is fully OSS and actively developed.
I just cannot fathom people who enjoy this non-stop BS rollercoaster and are happy to be passed from OG dev, to scummy publisher, to ??? publisher. And all just be happy about that instead of ... why am I even typing this shit. The people that care, care and use OSS or migrate when the writing is on the wall. The people that allow themselves to get jerked around and just take it are going to keep just taking it. And whining about it, while changing none of their behavior.
(Totally not related; see HN and the constant cycle of people shitting on decentralization and then being pikachu-shocked when proprietary centralized services do what they always do).
(Though, it's nice to finally, finally see a predominance of anecdotes of Linux experiences that aren't based on 3 year old distro ISOs. EDIT: 3 is generous, I saw people talking about a 20.04 LTS spin less than a year ago and acting like that was indicative of Linux on Desktop).
To be fair, I'm probably just way off base here. A company whose focus is absolutely not an Android Launcher surely won't enshittify or sell it in due course. Surely. Surely, surely, surely. Right? Like last time?
Props for doing the research and posting the links - I stand obviously corrected. I get why they did it, but it also leaves a bad taste in my mouth. :( Sigh.
"The devs of x11" is a wide category, considering how many X11 devs weren't even born when X11 was first written. Plenty of X11 devs objected to Wayland and tried to patch X11, but when half the devs decide they want to write a replacement and put the original into maintenance-mode, there's not much you can do.
You could fork it. X11 hasn't shipped a major release since 2005, the likelihood of a complete overhaul making it upstream was slim to none even in 2009. X11 developers were better-off focusing on stability, and the Wayland devs moved on. There was no conspiracy to kill either project.
So what is it, in one comment you say there were plenty of x11 devs who objected to wayland (please name and show the posts) and on the other hand you say there were not enough to keep an xorg fork going?
People are arguing that fixing the issues in X11 would have been much easier and less work than making wayland. So why could those half of x11 developers who left make wayland while the other half that was left over could not even make one release?
Valve ships a Wayland compositor that just runs XWayland for apps and doesn't even expose the Wayland socket by default. I'm really not sure how we're supposed to count that.
reply