Comment by sudo_cowsay
14 hours ago
Not that easy. Also, they have "priorities." Although their priorities are different than the users'.
14 hours ago
Not that easy. Also, they have "priorities." Although their priorities are different than the users'.
Just throw some tokens at the problem. I’ve vibed up a Rust Crux hybrid app that runs well on macOS, iPad and wasm and does some pretty complex xml manipulation and other document work. Absolutely smokes electron and you get native UI.
Ref: https://redbadger.github.io/crux/
On top of everyone else’s great points, if you make your own “fork” of something, then you have to consistently maintain it. Which can be done with tokens, but an extra cost with something that’s not as user tested.
I’m not talking about forking, but using standard libraries and native frameworks instead pretending electron is a desktop app.
1 reply →
one does not just "throw tokens" at a problem, Ai is not that capable, and we are talking about MS Office file format, likely a NP hard problem
But in case they succeed the return on image will be astonishing.
4 replies →
I mean, aside from all the NP Hard sub problems (I might not be reading your satire though), the real hard problem is that a "product" is not just software, but an ecosystem and a promise of maintenance of the abstract user experience & quality of it.
AI is especially good at ports like this where there’s a known and well tested surface area.
3 replies →