Off topic, How do you clone a project like that big? Git is still trying to receive the objects %1 of 2,200,337
Blink: A rendering engine for the Chromium project
241–250 of 326 posts
Re: Blink: A rendering engine for the Chromium project
#242Earlier quoted context omitted.
>So what happens when someone introduces a new whiz bang css feature that Chrome handles badly? Something you might, as a developer, want to disable in Chrome, but leave in for everything else? Or any other browser since they're all prone to introducing flakey implementations of CSS sometimes. >All this means is we'll have to go back to the old ways of sniffing out browsers, and I fail to see how that's better. The s…
I was being polite. I'm talking about IE specifically. >"Use a modern browser [actually, Chrome] to get the full experience" is not an uncommon sight these days. Yup, and it's sucky. It's no different to "this site is optimised for Internet Explorer".
Hardly. Having a site that has buggy coding which has been tweaked to look good in IE's buggy rendering is a far cry from "our site uses cutting edge web-standard features that your browser does not support, please use a more up to date browser for a better experience". Night and day different.
Re: Blink: A rendering engine for the Chromium project
#243Earlier quoted context omitted.
Assuming that at some point blink will support multiple language VMs, will source maps still be needed (for blink)? Sorry if this is a naive question!
yeah, if you're running directly on a VM for the language (e.g. JS on a JS engine, Dart on a Dart engine) you wouldn't need source maps for debugging, unless you are using some other tool that is doing source->source transforms for you (e.g. https://github.com/dart-lang/web-ui currently does some dart->dart source transforms). You'd still have source maps for the dart2js output.
When you are expecting Blink to be available to chrome standard builds? A ballpark time-frame?
Edit: just found the answer here, if anyone is interested : https://news.ycombinator.com/item?id=5489111
Re: Blink: A rendering engine for the Chromium project
#244Earlier quoted context omitted.
I don't understand this claim. WebKit2 was landed with effectively no notice and no attempts at collaboration. I saw repeated attempts to work on a shared architecture in WebKit2, but none were reciprocated. http://goo.gl/KH1Sr Eventually all non-Apple contributors were cut off entirely from WebKit2 as a matter of policy. http://goo.gl/iTDAR
We talked privately with particular Chrome folks before we started (as described upthread), in the middle, and shortly before landing to mention that we were landing soon. I don't know if the contents of these conversations were ever shared with the whole Chrome team as som Chrome people seemed super surprised at our announcement. It is true that when we announced our effort, it came with a rough working prototype an…
Hi Maciej. Sorry if my comments read as though I was implying that you were wrong or bullheaded to choose WebKit2. That wasn't my intention; there are of course good technical arguments for choosing either architecture, and I'll choose my words more carefully next time the question comes up.
Re: Blink: A rendering engine for the Chromium project
#245I know it might be an unpopular comment, but I really don't like this. I had hoped every browser would eventually use the webkit rendering engine. I have a hard time feeling sorry for those engineers that have to maintain compatibility, when I think of the many frontend engineers that now have to test a different rendering engine :(
>I had hoped every browser would eventually use the webkit rendering engine.
WebKit is not a standard. Writing WebKit code, isn't the same as writing standards-based code. We lived through the ie days, why go back to those?
Re: Blink: A rendering engine for the Chromium project
#246And so begins phase 2 of embrace, extend and extinguish. It's just what large tech companies do now days.
If you're going to badmouth this decision, then please at least read the articles and address the reasons they mentioned. It's pretty stupid and pointless to make irrelevant generalist statements.
Re: Blink: A rendering engine for the Chromium project
#247Will Blink have any direction from non-Google employees, in the same way WebKit has non-Apple reviewers?
Re: Blink: A rendering engine for the Chromium project
#248Earlier quoted context omitted.
I was being polite. I'm talking about IE specifically. >"Use a modern browser [actually, Chrome] to get the full experience" is not an uncommon sight these days. Yup, and it's sucky. It's no different to "this site is optimised for Internet Explorer".
Hardly. Having a site that has buggy coding which has been tweaked to look good in IE's buggy rendering is a far cry from "our site uses cutting edge web-standard features that your browser does not support, please use a more up to date browser for a better experience". Night and day different.
No different. Were you not around when IE was the "cutting edge" and had all the newest features?
Re: Blink: A rendering engine for the Chromium project
#249You can read more about the intended architectural changes at Blink's project page:
http://www.chromium.org/blink#architectural-changes
Re: Blink: A rendering engine for the Chromium project
#250Alex Russell has a good analysis about the move: http://infrequently.org/2013/04/probably-wrong/
The argument is essentially: "It took up lots of engineering time and effort to maintain compatibility with other platforms, so this allows us not to worry about other platforms and only focus on our own and that will allow us to move faster." Hopefully this is easier for everyone. If the chrome multithreading architecture really was the pain point then does that mean that webkit will also be deleting thousands of fi…
*multiprocess