4 ms·
I take umbrage with your PHP reference... JavaScript the language is pretty damned consistent, and nice. The browser APIs, that's a different story. As to Pho
by tracker1 8y ago
I take umbrage with your PHP reference... JavaScript the language is pretty damned consistent, and nice. The browser APIs, that's a different story.
As to PhotoShop or GarageBand, I think there's some more flushing out to do as far as APIs, and frankly that kind of stuff might be workable with WebAssembly. It would take a lot of effort to convert everything, also, not sure if you can use WASM in WebWorkers, but that may be more ideal. As to the cost, are you meaning overhead, or programming cost?
I'd guess a not insignificant number of "native" apps for mobile are at least partly framed web apps. Also, I would probably just reach for React Native and re-use as much as possible, which would still leverage JS for most of it.
In the end it depends... you get a LOT from web applications today. I see it as a bigger boost for internal/corporate/enterprise applications. Because you don't have to manage wide infrastructure and updates in nearly the same ways, you can simply do server deploys and be done.
Also the 1996 apps reference was in that most UI toolkits default to looks that haven't changed much since 1990's and aren't skinnable in the least. I remember the late 90's and early 2000's, litestep and winamp were two of my favorite things. I know that was user customizations of apps, over developer/designer. All the same, maybe I want my site/app to look like Material Design over Bootstrap, or something else.