It's not, I'm not sure why they picked that example. It does look like QT has made some advancements in their accessibility story for web but Discord's web client is still just React, and even their new Rust app uses GPUI and not QT.
The basic accessibility provided by a DOM-driven app with no intentional aria accommodations blows QT's canvas-driven fake web compatibility out of the water.
Your 20-50 cent customer does the same thing but prices it for Gates at 140,000. Rinse and repeat and Gates ends up paying 20-50 cents for a banana from somebody that isn't you.
What would stop Bill Gates from spending $150K+ on just growing his own bananas and then selling them for a market clearing price at modest profit and therefore putting your banana pricing scheme out of business?
This is a wholly unrealistic way to do business lol.
Might be worth a refresher on the guidelines, or at least a thoughtful examination of why this completely unrelated topic lives rent-free in your head.
The appeal is that it's not React, aimed mostly st people who have a grievance against React for one ill-informed reason or another. In time it will either become React by another name or die out.
Look at the average React site in the wild, and notice that it is dog slow due to the various performance bugs it exhibits. Apparently nobody can get it right.
There are very many highlight performant sites built on React, and very many sites that are homespun or built on other frameworks that perform badly. It's a scapegoat.
It's fascinating to see retrofuturist ideas being built in real-time. Being able to translate your thoughts instantaneously to cogent written text and using it to make a PowerPoint is almost painfully analogous to e.g. cassette futurism, or like 50s visions of the future where we have gigantic video screens but they're still CRTs.
The year of Linux desktop will come after the desktop is no longer relevant, but I'll be honest, I've been AI-pilled, and it's never been a better time to run a Linux desktop. Instead of going sleuthing every time I hit a papercut that previously I'd have spend hours consulting a how-to or a wiki to find the subsystems and config files to fix the problem, I can now just describe the problem to an AI agent that runs around on my system that just fixes it while I go off and do something else.
I'd love to see a screencast of this working if you're so inclined one day to make a walkthrough. If it's mostly walking away, that's even better because you could show the prompt and a before/after of it working. (Just a casual observation, and less of a request, not trying to assign work :)
I've seen so many people claim this is the future we're living in, but I've never seen it actually work as described. It's always more hand holding than I'm willing to put into an llm
reply