3 ms·
You don't necessarily have to touch the markup directly, your app can essentially be pure JS (or compiled to pure JS) that paints it all into the DOM dynamicall
by blasdel 17y ago
You don't necessarily have to touch the markup directly, your app can essentially be pure JS (or compiled to pure JS) that paints it all into the DOM dynamically (see http://cappuccino.org/ http://cappuccino.org/)
You don't need a server-side language if the app doesn't really need to communicate with your server. You can do everything client-side with LocalStorage (SQLite) and cached assets. If the page has the right metadata on it, "Add to Home Screen" saves the whole app locally.
And there's no reason why the server, if it needs to exist, shouldn't be executing the same language (see http://nodejs.org/ http://nodejs.org/)
The modern web is the platform. There are nice local platforms, but your "write once run anywhere" 'native' app isn't going to fit in on any platform that actually gets used.
- krainboltgreene 17y agoI don't want to use Javascript. I want to use to be able to use any language to write web applications. Any one language. :/ I think we're really choking ourselves as hackers if we let Browsers either end up as completely JS or the hacked together combination of (poorly enforced) HTML, (ugly syntax) CSS, and Javascript
- mooism2 17y agoWell, that's easy: just write a compiler for your favourite language that outputs javascript (plus glue to integrate with jQuery/MooTools/whatever).