Pretty cool. There's been a push to make HTML run everywhere, but this proves you can make X run on HTML. Maybe someday we'll code apps in Objective-C/Java that run in the browser, all inside a canvas.
That would be a sad day. Layers upon layers of complexity, abstraction, technologies, etc. Please make it easier. More simple.
Webkit.js
101–106 of 106 posts
Re: Webkit.js
#102Why? Not being dry/evil, simply just interesting in whether this project has practical offshoot or is pure fun (..)?
http://en.wikipedia.org/wiki/Brainfuck
so the reasons all the same.
Re: Webkit.js
#103Earlier quoted context omitted.
What exactly are iOS users missing in Safari, in your opinion, that they would get from Firefox? I can see that Chrome has some cool sync features if you're into that sort of thing. But it still uses WebKit. And from what I've observed, people seem happy with the "Chrome" app in the app store, even though it uses a handicapped renderer. (Although in iOS 8, it won't be handicapped anymore, and will be as powerful as n…
The funny thing is that the "RAWR NO SAFARI, ONLY CHROME!" people don't seem to realize that both are WebKit at the core. Sure, some features are in Chrome first, but that's only because Apple is very cautious when releasing the new features to the general public.
Re: Webkit.js
#104Very nice and with JS support it would be perfect! I wonder if this is a solution to potential XSS attacks with embeded iframes or embeded user-generated html+css+js.
Re: Webkit.js
#105Why? Not being dry/evil, simply just interesting in whether this project has practical offshoot or is pure fun (..)?
Doing this in the browser might be a little silly, or at least I can't immediately think of a good use, but I think using this in a node.js program as an easy way to template something out and render an image/pdf locally could be useful.
Re: Webkit.js
#106I've been watching this project hoping that eventually PDFs could be rendered on the client.