Comment by cpursley
13 hours ago
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.
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.
Ah good point, I thought this was coming across from the "recreate" your own approach. I would fully agree with you on using native frameworks, though the eletron desktop is a great "entry" onto desktops ensuring companies only have to update 1 source, as opposed to natives everywhere.
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.
Can you expand upon this?
2 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.
*that only microsoft has access to.
These guys puposely obscure controls and understanding of these products 100% to prevent you doing a port.
Just go open a microsoft word doc in the browser and look at the dom.
Despair! Horror!
1 reply →
"ports like this" skips the part about Microsoft/enterprise software having a known and well tested surface area, the few examples we've seen are exceptional cases I suspect