3 ms·
> An OS on an OS, in a document reader Versus an interpreted language executed in a runtime running on a virtual thread of an OS running on top of a BIOS over
by feoren 2y ago
> An OS on an OS, in a document reader
Versus an interpreted language executed in a runtime running on a virtual thread of an OS running on top of a BIOS over a glorified calculator!? Insanity! Whatever happened to good old-fashioned pen and paper!?
There's nothing wrong with the model of delivering your software as a small program to run in a sandboxed browser environment. WASM, canvas, WebGL -- you can do nearly as much on the web as native nowadays, with a dead-simple deployment model. One of the only type of programs that's much harder to make in a web application is malware. Calling a modern browser a "networked document reader" is as silly as calling a modern computer a calculator.
- collingreen 2y agoThe DOM seems fair to call a networked document reader. You've suggested a different build target for what would have been native apps - I think you and OP meet in the middle a bit; you get the power of non-html app development. OP laments the overhead of having to shove that into the existing web model designed for documents; you appreciate the sandboxing. I think you have similar opinions that mostly overlap, regardless of insults about statements being silly.
- dullcrisp 2y agoYou’re assuming that teaching fleshy monkeys to smear their gunk on glorified bathroom tissue was ever a good idea.