Can't wait for JS support so I can:
Webkit.js
31–40 of 106 posts
Re: Webkit.js
#32Earlier quoted context omitted.
Because competition in the browser market is vital to keep the web platform progressing and to prevent a single party from controlling web standards. Do you remember the dark ages when IE ruled the web and things like HTML5, canvas, webgl, etc... couldn't happen?
>competition in the browser market is vital to keep the web platform progressing and to prevent a single party from controlling web standards I don't see much difference between a single party and a cartel of 3-4 parties. They are all mega corporations that don't share my interests and even when there are several parties any one effectively has veto power over any changes to standards. The push for browser-as-OS is o…
> You don't get any browser choice at all when your hardware is running ChromeOS or FirefoxOS
Both browser based OS's are still in their early phases. What if the hardware could run both, just as easily as you could put whatever flavor distro of linux on your desktop?
There's too much closed source OS specific drivers to really allow you to run whatever OS you want on whatever hardware you want; and everyone is disincentivized unless money is involved. But what if drivers were open source? I'm not sure how to incentivize that (the community fixing shitty GL driver implementations, maybe), but I would bet you it would be a hell of a lot easier to get you favorite software running on your favorite hardware if they were.
Right now, closed source drivers are a thorn in the side of users having choice. With the rapid progression of the Mesa project in particular, when hardware manufacturers come around to releasing their drivers, then ChromeOS, Firefox OS, and Tizen will be poised and in a good position.
Re: Webkit.js
#33Earlier quoted context omitted.
Most iOS devs aren't clamoring for alternative browser engine implementations because they're happy with the objective C runtime. Web developers shouldn't be happy with only having one browser implementation available because there's no competition on iOS. Safari on iOS can lag in features and not care because there is no competition on iOS. Chrome on iOS offers nothing in the way of additional html5 APIs and is just…
> if we could ship an alternative browser engine implementation with competitive JIT'ing JavaScript engine Which is not possible on FirefoxOS. So I don't see how 'open' wins here (I'm using 'open' as the GP used it: a marketing buzzword synonymous with Mozilla).
I agree that "FirefoxOS will host Safari / Chrome apps, before iOS will allow a Firefox." doesn't lead to "Open FTW." I think Open still wins, for other reasons I've been trying to document. [0] Firefox OS is still young, and if it can establish meaningful marketshare, it puts Mozilla in position to change the industry.
For example, what if Mozilla had leverage over device manufacturers to say "no locked bootloaders" and device manufacturers complied? I'm not sure Mozilla has that leverage today, but what other ways could Mozilla affect the industry for good once it does?
[0] https://github.com/nickdesaulniers/What-Open-Source-Means-To...
Re: Webkit.js
#34Neat. Getting some good use out of HTML2Canvas as well. But always wondering why there is no way to get a bitmap from screen... something like window.getPixels(x, y, width, height).
Re: Webkit.js
#35Earlier quoted context omitted.
Firefox for Android is very popular and highly rated in the Google play store. The browsers that are in the Apple App store are handicapped by legal limitations, which are not present on other, more open operating systems.
>The browsers that are in the Apple App store are handicapped by legal limitations, which are not present on other, more open operating systems. Is FirefoxOS more or less 'open' than iOS? You can't write a competitive javascript runtime for FirefoxOS either.
You can fork the project on Github and Mercurial and write DOM bindings to whatever JavaScript engine you'd like.
[0] https://github.com/mozilla-b2g/B2G [1] http://hg.mozilla.org/
Re: Webkit.js
#36Neat. Getting some good use out of HTML2Canvas as well. But always wondering why there is no way to get a bitmap from screen... something like window.getPixels(x, y, width, height).
Yes! This would open a huge number of possibilities. Simple things like a colour picker, to transitions based on the content of the window would be made possible. I would love to see this happen.
Re: Webkit.js
#37In Chrome (for me, on 64bit Linux) it consumes 176MB of RAM -- for all of WebKit + Cairo + FreeType/HarfBuzz/etc -- it's most of an OS right there.
GMail, a webapp email reader, is currently taking 368MB of RAM. Insane!
Re: Webkit.js
#38this is pretty cool but network requests and javascript support would make it even more crazier.
I viewed the html source for this page and pasted it. I was quite impressed. It looks like this is supposed to be a browser engine written in Javascript?
So essentially we would have a sandbox browser within a browser? That would be awesome.
Re: Webkit.js
#39Anyway to get this to run in node with the output going to say Cairo? It'd be a fun little project to see if you could build a simple but working browser in nothing but JS.
And then, getting the browser running itself in the in-browser browser.
Reminds me of Gary Bernhardt's talk "The Birth and Death of JavaScript": https://www.destroyallsoftware.com/talks/the-birth-and-death...
Re: Webkit.js
#40Why? Not being dry/evil, simply just interesting in whether this project has practical offshoot or is pure fun (..)?