Comment by cpursley

13 hours ago

I still don’t understand why with all their cash these companies dont redo their apps in Rust or native. They are all so heavy and dog slow. There are already some very fast cross platform (wasm too!) libraries that can do what poppler does as well as parse and produce various office file formats. Because 2gb is crazy town, these things could be around 100mb, just throw some tokens at the problem.

You should go actually try to make any basic automation work around these systems.

They purposely obscured, google doc is another example they completly hide the dom!

I spent months fighting word processing systems and ended up shipping libre. There's almost zero alternatives without that becoming your entire company.

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.

      2 replies →

What % of time, for a an average session, do you think is app overhead vs waiting for tokens? And there's your answer for why it's not a priority.

What makes you think Rust is automatically better?

(Also, "Rust or native" is a strange dichotomy. What's not native about Rust?)

  • I think “or native” is a gesture at swift/objc for mac and C# or whatever people write windows apps in.

  • Rust or native is objectively more performant and have smaller binaries than these web apps in Halloween costumes…