Webkit.js • Hacker News Board

Re: Webkit.js

#21

Post by tlinton » Fri, Jun 20, 2014, 6:36 PM UTC

PLenz wrote: post #3

Anyway 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.

Yes, there's a software rendering version, it actually uses Cairo. Software rendering just bitblts up (out of a webworker or as a SDL_UpdateRect) callback in javascript as a RGBA array.

Re: Webkit.js

#22

Post by agildehaus » Fri, Jun 20, 2014, 6:36 PM UTC

nnnnni wrote: post #17

atonse wrote: post #4

Earlier 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.

Chrome forked Webkit over a year ago, creating Blink. They're two independent layout engines now.

Re: Webkit.js

#23

Post by tlinton » Fri, Jun 20, 2014, 6:36 PM UTC

LukeB_UK wrote: post #5

Getting errors on chrome 35.0.1916.153 on Linux Mint. 56 on line 34 in webkit.api.js Uncaught # on line 15633 in webkit.bin.js

If you put in any HTML that requires webkit to go out to hte network it crashes since network requests are disabled in the demo.

Re: Webkit.js

#24

Post by anon1385 » Fri, Jun 20, 2014, 6:37 PM UTC

ozten wrote: post #15

atonse wrote: post #4

Earlier 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…

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.

Re: Webkit.js

#25

Post by freehunter » Fri, Jun 20, 2014, 6:38 PM UTC

atonse wrote: post #4

ozten wrote: post #2

FirefoxOS will host Safari / Chrome apps, before iOS will allow a Firefox. Open FTW.

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 best thing about Android Firefox is the add-ons. Having adblock running on my phone is a pretty nice-to-have feature.

Re: Webkit.js

#26

Post by copremesis » Fri, Jun 20, 2014, 6:41 PM UTC

straight up broken

Re: Webkit.js

#27

Post by thefreeman » Fri, Jun 20, 2014, 6:42 PM UTC

nnnnni wrote: post #17

atonse wrote: post #4

Earlier 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.

I'm pretty sure iOS Chrome is only WebKit at the core because of iOS restrictions. All other version of Chrome on all platforms use Blink.

Re: Webkit.js

#28

Post by [deleted] » Fri, Jun 20, 2014, 6:42 PM UTC

nnnnni wrote: post #17

atonse wrote: post #4

Earlier 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.

[deleted]

Re: Webkit.js

#29

Post by thefreeman » Fri, Jun 20, 2014, 6:44 PM UTC

agildehaus wrote: post #22

nnnnni wrote: post #17

Earlier quoted context omitted.

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.

Chrome forked Webkit over a year ago, creating Blink. They're two independent layout engines now.

I believe he is referring to the fact that iOS Chrome is the only version still using WebKit

Re: Webkit.js

#30

Post by tlinton » Fri, Jun 20, 2014, 6:55 PM UTC

agildehaus wrote: post #22

nnnnni wrote: post #17

Earlier quoted context omitted.

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.

Chrome forked Webkit over a year ago, creating Blink. They're two independent layout engines now.

Sort of, they're very similar still. In actually the layout is almost exactly the same, its the rendering and compositing that has significantly changed between the two.