I dont think this is a reasomable counterpoint because the target audience in question would also vastly prefer shit as simple as an mspaint illustration or a dithered irl image.
Also, it is quite feasible to find royalty free images, and I have no idea where you're getting the impression it is not. There are a host of images that provide licensing metadata. Google image search and co. can find these. It's simply a matter of verifying the license authenticity.
It's just fundementally stupid.
Thank god. Now if all goes well people can stop talking about that really buggy and awful fork.
If I had a nickel for every time someone ignored me just to say something I directly address...
You are pretty blatantly referencing X11 Forwarding / Network Transparency.
I can't reasonably assume you actually read anything I say, but to briefly reiterate:
Checkout Waypipe. Here's a direct quote from the README:
Waypipe is a proxy for Wayland clients. It forwards Wayland messages and serializes changes to shared memory buffers over a single socket. This makes application forwarding similar to ssh -X feasible.
Have you tried this? What is disatisfactory about it? And if all else fails, is there really ANY problem with simply using VNC/etc? What real-world problem do you have that is uniquely solved with this?
What? I've gotten RDP, VNC, and SPICE working fine on Wayland. And if you need app-level displays then waypipe worked fine the last time I used it. I've been running Proxmox containers with Wayland just fine, too.
Any particular use case that benefits from what Xorg was uniquely capable of networking-wise (network transparency, afaik?) of is quite niche and development effort twoards that end has always reflected that!
I've not been able to find the git or project repo/writeup of "Wayland on Wires". Though i do vaguely feel like I saw it somewhere.
But I suppose me and my ongoing computer science degree and shared family hobby of IT simply hasn't reached Real Linux User levels yet. I must sharpen my Bash Blade for another 1000 years...
Since that's the case, I suppose I must defer to your Infinitely Endless Wisdom as a True Linux User. I beg of thee, answer my Most Piteous Questions...:
"Linux as a desktop is BAD!"
"Evidence?"
"I failed to make a slideshow in a buggy application. :'("
In all seriousness, though, wtf? You could have pulled from any of the well-know papercuts and instead you balk about a broken application? Lmao?
My vibeo gaem crashed on Windows once. I guess I should hold Microsoft personally accountable for it....
For the record, I've used Linux throughout Highschool, Community College, and College. No issues with basic software functionality, really.
The worst and only issue I've had in that regard is self-inflicted because I decided to run LibreOffice via Wayland, which has an ongoing bug that makes scrolling laggy. That's it.
The larger issues with Linux as a desktop is software compat (Wine) with Windows for nicher use cases (requires debugging and a bunch of setup), certain drivers (cough cough Nvidia cough cough), and general dumbass-proofing.
Can we just let this shit die already? If you're unsatisfied with Wayland make extensions to the protocol or make a new one.
Why in the fuck are so many people obssessed over a piece of software that contains an entire networking stack and has a security model so bad that it lets literally every application keylog you constantly?
It is self-evident that free software with open licensing and no strings attached is a superior and more beneficial ownership model than closed source paid licensing. That part I don't think anyone needs to be convinced of.
As someone who has both technical and nontechnical people in their family, I call bs. Even if it is partially self-evident (in the fact that you dont need to sign into an account or pay for it), the details, and more importantly the weight, of FOSS is often lost on people.
I've had to watch some of them walk into a rake and bruise their foreheads several times over before really absorbing it.
It's something people need to really read up on before true comprehension. That, or get burnt really really badly.
Ideology? Politics? Tomato tomatoh in my eyes. At the very least, they're nearly inseperable (think: DMCA, copyright law, etc.)
Go is a simpler-to-read language that does not involve lifetimes (as you know, it is GC'd). For a lot of smaller projects like this, the boringness of Go is preferred. Less mental bandwidth required.
I'll admit my definition of "industrial" here was vague, but I think you can get my point. I'm not trying to say that Rust isn't good in a business setting - my job also has Rust in the code!
However, for these purposes, most of the benefits of Rust in this situation are already provided by Go.
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.
There is no such thing. Every "generic, terminal-based installer" is in reaity a script that was intentionally made to target many multiple distributions.
And do you know what most of them do...? Use the inbuilt package manager of your distro.
That and set up some systemd services and PATHs, sometimes.
You're such a fucking goober.