Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blink: A rendering engine for the Chromium project

blog.chromium.org

Post reply on HN
Print view View original

231–240 of 326 posts

Re: Blink: A rendering engine for the Chromium project

#231

Post by smrtinsert »

slacka wrote: post #215

> "For example, we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines" On my 2GB netbook, chrome has gone from my preferred browser to unusable due to the high memory footprint of recent builds. I wonder if this cleanup will help get the memory down to something reasonable like where it was up until Chrome 10 or so.

Recently it's been crashing for me left and right. This seems to happen with chrome over the years, ebb and flow of functional non-functional. I just switch back to Firefox during that time.

Re: Blink: A rendering engine for the Chromium project

#233

Post by dragonwriter »

deadc0de wrote: post #201
hiker wrote: post #47

Earlier quoted context omitted.

Quite the opposite, see http://www.chromium.org/blink#vendor-prefixes

I mean use the monopoly to take the tech, clone, tweak, and then don't contribute back. Thankfully google will keep it open source since they're making money from it quite indirectly. But still.. A "fork you" to apple that would make the web suffer. Douchy.

> I mean use the monopoly

In what market relevant to this issue does Google have a monopoly?

> to take the tech, clone, tweak, and then don't contribute back.

Its all open source, so it is contributed back. Google just isn't constrained to not change things that WebKit users rely on in future Blink work.

> A "fork you" to apple that would make the web suffer.

WebKit and Chromium both being more free to try different solutions isn't going to make the web suffer, its going to make the web better.

Re: Blink: A rendering engine for the Chromium project

#234

Post by dragonwriter »

nnethercote wrote: post #193
yanw wrote: post #20

Earlier quoted context omitted.

Chromium uses a different multi-process architecture ... and supporting multiple architectures over the years has led to increasing complexity ... we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines How is that not engineering based?

Last time I measured (late 2012) the entire mozilla-central repository was 4.488 million lines of code. So I don't believe that by simply streamlining things they'll be able to remove anything like 4.5 million lines. Perhaps an extra zero got inserted somewhere.

> Last time I measured (late 2012) the entire mozilla-central repository was 4.488 million lines of code.

Mozilla isn't WebKit.

> I don't believe that by simply streamlining things they'll be able to remove anything like 4.5 million lines.

I suppose you could compare WebKit repos against Blink repos once the latter is live to see exactly what is cut, but I'm going to say the people working on the code that are the source of the count know how many LOC are involved, and that there direct count is more reliable than a third-party estimate based on a different browser's repo.

Re: Blink: A rendering engine for the Chromium project

#235

Post by levifig »

malandrew wrote: post #167
tolmasky wrote: post #139

Earlier quoted context omitted.

Like most things, habit probably. Also, I used to work a lot on Safari/WebKit, so I guess sentimental value? That being said, I do like the way Safari "feels" a lot more than Chrome. I think Chrome is actually quite ugly, and bad from a UI perspective. For example, Safari's overflow tab menu is a much nicer solution than Chrome's insistence on shrinking tabs ever smaller until you can't tell them apart at all. Additi…

The tab behavior in chrome is what does it for me too. In fact, you can have so many tabs that you can no longer open the last tabs (the tabs extend past the little full screen or switch user icon). I also think Safari has a much better solution for handling bookmarking when you have multiple tabs. Solve these two issues and I'd switch to Chrome in a second.

I actually prefer Firefox's approach to multiple tabs: the tab bar scrolls (you can use the scroll wheel). That's about the only thing I like in Firefox anymore though… Been using Chrome because of its multi-user support (tied in with Google accounts) but Safari is soooo much better than Chrome in terms of UI and UX… Latest Chrome betas, with the full integration of the address bar as a full-blown "Google box" (e.g. you start typing, it loads Google Instant Search without the page's classic search box)…

I digress… :)

Re: Blink: A rendering engine for the Chromium project

#236

Post by vxNsr »

smith7018 wrote: post #217
Achshar wrote: post #207

Earlier quoted context omitted.

Chrome has a very quick release cycle, so I don't see why not?

Webkit is used by Safari (desktop and iOS) which is still a huge portion of internet users.

right but since those "new" things won't work in chrome the hope is that devs won't implement them anywhere else.

Re: Blink: A rendering engine for the Chromium project

#237

Post by cromwellian »

coldtea wrote: post #146
drivebyacct2 wrote: post #4

Interesting timing, given the Samsung+Mozilla+Servo news today.

Yes. Announcing this especially today seems like a "fuck you" at Samsung. Downvotes? Anybody thinks that two companies that are in some heat over Android/Tizen et all, just coincided to release information about new rendering engines on the same day? As if rendering engines are announced every other day, right?

Did you ever consider that the launch date had been scheduled a long time ago?

Re: Blink: A rendering engine for the Chromium project

#238

Post by othermaciej »

tolmasky wrote: post #124
macrael wrote: post #112

So, I'm pretty sure this is a correct history: 1. Google builds a new process architecture into Chrome as a product differentiator. (It was a major part of Chrome's initial marketing) 2. WebKit 2 is built (mostly by Apple?) to bake the same type of architecture straight into the core framework -- anyone using WebKit can use it and get the same security/stability benefits.[1] 3. Google says that the pain in maintainin…

Maybe because anyone who has used Safari knows that WebKit2's multiprocess architecture is worse in practice. As a full-time Safari user I can tell you that things have gotten markedly worse since it went multiprocess. Pages go white momentarily (not crash) all the time, and on top of that they also crash all the time. Additionally, I believe that unlike Chrome, Safari has ONE separate process for all the tabs, and t…

You're right that Chrome's multiprocess architecture is more mature than the WebKit2 design. I wish we hadn't ended up in a position where we felt we had to make our own. But stay tuned - we have some great stuff coming up.

Re: Blink: A rendering engine for the Chromium project

#240

Post by sanxiyn »

coldtea wrote: post #146
drivebyacct2 wrote: post #4

Interesting timing, given the Samsung+Mozilla+Servo news today.

Yes. Announcing this especially today seems like a "fuck you" at Samsung. Downvotes? Anybody thinks that two companies that are in some heat over Android/Tizen et all, just coincided to release information about new rendering engines on the same day? As if rendering engines are announced every other day, right?

This is a conspiracy theory. PR moves take time, so both Servo and Blink announcement probably baked for many weeks. The best explanation is both PR teams thought today is a good timing, probably because it is right after Easter holidays.
Post reply on HN