WebKit.js: Pure JavaScript Port of WebKit • Hacker News Board

Re: WebKit.js: Pure JavaScript Port of WebKit

#11

Post by dikei » Thu, Jan 16, 2014, 6:37 PM UTC

sathishmanohar wrote: post #4

Now firefox can run chrome inside firefox, but chrome can't run firefox inside chrome.

Firefox cannot run chrome until they implement v8.js

Re: WebKit.js: Pure JavaScript Port of WebKit

#12

Post by kej » Thu, Jan 16, 2014, 6:38 PM UTC

sathishmanohar wrote: post #4

Now firefox can run chrome inside firefox, but chrome can't run firefox inside chrome.

You could probably turn Firefox into a NaCl app that would run inside Chrome.

Re: WebKit.js: Pure JavaScript Port of WebKit

#13

Post by undershirt » Thu, Jan 16, 2014, 6:39 PM UTC

TheMakeA wrote: post #10

I may be the only one excited about this, but I think it's awesome. I imagine a future where a "web browser" is just a WebGL + Networking + JS API, and you just load in HTML5.js. The benefit of something like this is that it puts the power back in the hands of the people. You don't have to worry about Microsoft ignoring standards, you just load in the HTML5.js that you know works. Want a new feature? Fork HTML5.js on…

Thank you for sharing that. That is a really interesting vision for the future of browsers.

Re: WebKit.js: Pure JavaScript Port of WebKit

#14

Post by wmf » Thu, Jan 16, 2014, 6:50 PM UTC

TheMakeA wrote: post #10

I may be the only one excited about this, but I think it's awesome. I imagine a future where a "web browser" is just a WebGL + Networking + JS API, and you just load in HTML5.js. The benefit of something like this is that it puts the power back in the hands of the people. You don't have to worry about Microsoft ignoring standards, you just load in the HTML5.js that you know works. Want a new feature? Fork HTML5.js on…

Check out the Embassies project: http://research.microsoft.com/en-us/projects/embassies/

Re: WebKit.js: Pure JavaScript Port of WebKit

#15

Post by elwell » Thu, Jan 16, 2014, 6:52 PM UTC

All in a 50KB js file.

1. Why?

2. How is this humanly possible?

Re: WebKit.js: Pure JavaScript Port of WebKit

#16

Post by elwell » Thu, Jan 16, 2014, 6:53 PM UTC

dikei wrote: post #11

sathishmanohar wrote: post #4

Now firefox can run chrome inside firefox, but chrome can't run firefox inside chrome.

Firefox cannot run chrome until they implement v8.js

Yeah. Maybe Safari?

Re: WebKit.js: Pure JavaScript Port of WebKit

#17

Post by dlubarov » Thu, Jan 16, 2014, 6:53 PM UTC

I wrote a JS port of JavaScriptCore:

  eval

Re: WebKit.js: Pure JavaScript Port of WebKit

#18

Post by julien_c » Thu, Jan 16, 2014, 6:53 PM UTC

TheMakeA wrote: post #10

I may be the only one excited about this, but I think it's awesome. I imagine a future where a "web browser" is just a WebGL + Networking + JS API, and you just load in HTML5.js. The benefit of something like this is that it puts the power back in the hands of the people. You don't have to worry about Microsoft ignoring standards, you just load in the HTML5.js that you know works. Want a new feature? Fork HTML5.js on…

Have you checked out http://breach.cc/ and http://breach.github.io/exo_browser/ ?

> The ExoBrowser is a scriptable platform designed to ease the experimentation with new concepts for the Web Browser.

> The ExoBrowser exposes its API (parts of the Chromium Content API + a Simple View Model) in Javascript and enables the implementation of a fully functional browser entirely out of it (as a Javascript/HTML/CSS app)

Re: WebKit.js: Pure JavaScript Port of WebKit

#19

Post by elwell » Thu, Jan 16, 2014, 6:55 PM UTC

dlubarov wrote: post #17

I wrote a JS port of JavaScriptCore: eval

Doesn't pass JSLint, moving on...

Re: WebKit.js: Pure JavaScript Port of WebKit

#20

Post by eseehausen » Thu, Jan 16, 2014, 6:56 PM UTC

elwell wrote: post #15

All in a 50KB js file. 1. Why? 2. How is this humanly possible?

It's 50MB. That probably revises #2. As for #1, isn't this a good thing in itself?