Thank god. Now if all goes well people can stop talking about that really buggy and awful fork.

On the one hand, I love Rust, love seeing Rust winning, on the other hand: the cynical part of me observes this as a way for them to say it's safer to use, somehow. In the sense that people fling Rust around in a kind of showey way.

Already we've been seeing projects fuck up with isolation irt MCP servers, so this is the backdrop to observe this kind of change.

I know this is blasphemy, but why not Go? Why Rust? I love writing Rust CLIs, but somehow I feel the personal arguments I make for such things don't really hold up in industrial settings like this (in particular, a small open-source CLI project that interacts with networking).

There's nothing wrong with using Rust here (Rust is great for business logic!), but the choice here almost makes me suspicious of the motivations.

Also there's existing Rust solutions in this area! Namely: https://github.com/sigoden/aichat

I don't really enjoy using AI when coding, but aspirationally, I'd rather support other projects than OpenAI, who is only a nonprofit in concept and is actively attempting to become a for-profit, whilst behaving like a VC funded startup.

(Not to mention the fact that mainline models are explicitly developed with the intention of destroying labor, in general)

My feelings exactly, stated a lot better than I could have managed.

God I love this publication to death. I've actually bought some of the ebook compendiums.

I was merely pointing out that these opinions, whatever they really are, have more publicity from people criticizing the founder.

Why yes, friend, I will just conveniently pretend that you bringing that up is completely outside the context of whether or not to seriously consider the criticism.

And if you are trying to make a point of whether or not the ideology is seriously impacting the project, you need-only take a casual walk through the issue list, and find (among other evidence) that a suggestion to move to codeberg was criticized for... "DEI". Wow. How technically-focused.

The best from your point of view would be not to speak about it.

You are getting more and more incoherent the more of these replies you churn out. What, precisely from my point of view (which I guess apparently you know very well? the irony...) here implies that "not talking about it" is the best choice? That's absurd.

I find it very important to understand the motivations, technical and ideological, behind a project.

If it were true, all this hatred against the project would be pointless.

I don't spend any effort talking about in any other respect than telling people that they should likely disregard if for both technical reasons (it cuts out Xwayland, his commits frequently lead to very blatant regressions that are nontrivial, etc.) and ideological (his terrible, awful politics and motivations for making the project, to begin with!)

The reason I replied to your comment is mostly out of idle curiosity and a deepseated longing for genuineness and critical thinking of other people that I have not yet managed to kill (despite its impracticality in the modern age).

Free software is all about freedom, and diversity means freedom of choice. If you don’t agree with that, you miss the all point.

This is all such a massive and disheartening reduction of what software freedom is. I hope that you eventually manage to think less shallowly about this.

Tell me, do you have any particular, material distinction you are making by making a choice between desktop protocols? The desktop protocol is a purely technical thing, and I have not heard a single peep out of you in regards to specifics.

To elaborate, in Xorg, it is a very monolithic beast. It is very convoluted in its purview and carries a lot of preset implementation of its various facets. It contains an entire networking stack for deciding how to communicate windows over a network.

It is significantly less flexible and modular than Wayland, because in Wayland basically everything of significance is decided by the compositor.

This, ironically to your point, actually gives you more choice and freedom in how things work (this is also why tiling window managers love wayland to death, it's pretty easy to just build upon the basic wlroots implementation!). So I have to ask you, frankly, what in the fuck do you think you're actually saying right now?

The issue, in this way, is that you only seem to care about software freedom in the sense of the abstract concept rather than the reality. You seem to think of software freedom in the sense of "I either build and install this package, or I build and install this one", with an all-consuming disregard for the technical aspects of freedom. Which is impractical, and arguably antithetical to the very process of trying to foster software freedom to begin with. As evident by literally everything to do with this situation. My lord.

Predictable AF, unfortunately

A really shitty one. (As in, completely removes Xwayland, and results in obvious regressions.)

This isn't coherent, and even if it was, the burden of stance interpretability is context-dependent.

He is the one with the politically charged README that reads plainly like the thoughtless garbage MAGA types in America put out. I mean cmon man, "[...] we'll make X great again"?

Also your shallow and brainless dismissal of all this criticism coming from his "detractors" (and who would not become a "detractor", after actually investigating his terrible dribble?) is defeated easily by just reading the actual words he said.

As in, for instance, the original source of his garbage antivax posturing that he posted in the linux kernel mailing list: https://lkml.iu.edu/hypermail/linux/kernel/2106.1/04542.html .

These are not alleged opinions, he's just full of shit.

And this isn't even mentioning the fact that Xorg is going to be dead, should be dead, and will continue to die. And good riddance, too! Terrible and borderline unmaintainable.

The argument that choice diversity is good inherently is stupid, too. Wayland is a god damned protocol! There is no reason to have lots of diversity there! It has no tangible benefit.

There are already many different compositors that implement the Wayland protocol, and there are also many 3rd party extensions! Can you think of a single, material benefit to simply having different basic desktop protocols?

Energy and water costs for developmenr and usage alone are completely incompatible with that. Come back in 20 years when it's not batshit insane ecologically.

Not to mention reducing power usage of programs isnt going to be very feasible based on simply an LLM's output. LLMs are biased twoards common coding patterns and those are demonstrably inefficient (if the scourge of web apps based on electron is any tell). Thusly your code wouldn't work well with lower grade hardware. Hard sell.

Theoritically they could be an efficient method of helping build software in the future. As it is now that's a pipe dream.

More importantly, why is the crux of your focus on not understanding the code you're making. It's intrinsically contrived from the perspective of a solarpunk future where applications are designed to help people efficiently - without much power, heat, etc.. weird man

True. I wish expectations aligned more with this kind of practice... I see a lot of people thinking in binaries about these kinds of issues: that either we should just trust (insert company here) completely or distrust... People should learn to demand accountabillity and transparency instead of just eating corporate drivel or becoming skeptic of Anything Ever.

What in the fuck?

It just kept going. Calling customers "zombies"..... bannung people from using chrome to access website, banning "regular reddit users"...... banning particular countries for pettt grudges with like, a few individuals???

Sunshine (the server) and moonlight (the client)