10 ms·
WTF? Chromium (2016)
- edhelas 9y agoI think that we are getting too dependent on this browser/engine (Chrome/Chromium/Electron and the many others derivatives). This will create serious issues in the future regarding how Google is caring about respecting the market, the standards and their users in general. Hopefully Mozilla has done a quite impressive work on Firefox those past few months and I personally don't see any advantages anymore for Chrome.
- mcny 9y ago> Hopefully Mozilla has done a quite impressive work on Firefox those past few months and I personally don't see any advantages anymore for Chrome. I use nightly and it is pretty good. Quite a few things are broken in nightly in Android but I can use nightly as my main browser (besides for hangouts which Google has yet to implement). Edit, we have pocket on Firefox though so https://getpocket.com/blog/ https://getpocket.com/blog/
- deusum 9y agoFF Quantum is quite nice, highly recommended.
- fenwick67 9y agoIt seems crazy to me how may projects depend on Chromium and V8 directly. Hopefully with Firefox's new improvements some of this will change.
- JustSomeNobody 9y agoMore to come with headless Chrome a thing.
- oatmealsnap 9y agoHeadless Firefox is a thing, too.
- oatmealsnap 9y agoAside from community support, what is preventing Firefox's JS engine from being used to power a JS runtime?
- bzbarsky 9y agoNothing really, and people use it for that. For example, https://github.com/0ad/0ad/tree/master/libraries/source/spidermonkey https://github.com/0ad/0ad/tree/master/libraries/source/spid...
- porfirium 9y agoThe Iridium website and logo look so professional and "enterprisey" that it looks like there's lots of money behind of it and they're going to screw you. A barebones or even text-only website would do them a favour.
- oatmealsnap 9y agoI don't get that sense at all. Looks like a generic "techy" Wordpress theme.
- hathawsh 9y agoI don't think that's a fair assessment. The web site (https://iridiumbrowser.de/ https://iridiumbrowser.de/) is nearly on par with the web sites for other big open source projects like http://python.org http://python.org or http://ruby-lang.org http://ruby-lang.org . I think it just needs minor tweaks. I would replace the marquee with static text and replace the section title "Manifest" with something clearer like "Our Purpose" or "Our Ambition".
- porfirium 9y agoI clicked on the Iridium website and I only see one line of text in uppercase. It has nothing to do with Python's or Ruby's. The Iridium website gives me the impression I'm downloading something akin to Comodo's browser. And it's constructive criticism anyway.
- exikyut 9y agoI was curious what the site looked like, so I opened it. Okay, I've seen worse desig--WHAT?! Wow, a marquee! Nice.
- janus3030 9y agoOpen the door, get on the floor Everybody walk the dinosaur
- tardygrad 9y agoOr just use Firefox, even if it is slightly slower than Chromium it's at least a browser that works for you not one that treats you as a pawn. A Chrome monoculture is harmful, even if Google has the best intentions which I don't think they do - they definitely value their profits over an open web.
- DominoTree 9y agoFWIW, at this point, the Firefox 57 betas are more responsive than Chromium for me. Not planning on looking back any time soon.
- tazjin 9y agoSame for me, I've also enabled all the experimental webrender flags on both private and work machines and have had basically no issues at all for the last weeks. It's actually almost slightly uncanny how well it's working.
- snowpanda 9y ago>It's actually almost slightly uncanny how well it's working. Indeed, I've caught myself thinking "it's not supposed to render this fast" a few times myself. Really am enjoying the nightlies.
- kibwen 9y agoThis might be a placebo effect, because last I heard enabling WebRender would leave the usual renderer enabled as well in order to paper over yet-unimplemented features, which should often result in double the work and, one would assume, worse performance. But if it doesn't feel slower, then, well, that might be some kind of triumph. :P
- merb 9y agoI'm still on chrome, because of pepper flash.. :/ and because debugging angular sucks on firefox. Edit: still checking out if it might be possible. i've just seen that the newer firefox has also some kind of flash player integrated. just the debugging is now strange.
- tzahola 9y agoI’d appreciate a curated list of software vendors who don’t run these kind of field tests/experiment/whatever on their users. Extra points if their products are not filled with bloated “”””analytics”””” crapware either.
- the_common_man 9y agohttps://bugs.chromium.org/p/chromium/issues/detail?id=318572 https://bugs.chromium.org/p/chromium/issues/detail?id=318572 is the issue
- Tyriar 9y agoIridium's stable release is based on Chromium v61 and Chrome is on v62. Sure they can boast about enhanced privacy, but I'm not so sure about security unless their base Chromium version is always up to date.
- agl 9y agoThe fact that Chromium runs multiple processes is unrelated to any field trials. Chromium has always been multi-process; that's why individual tabs and plugins can crash without taking down the whole browser. Additionally, multiple processes are needed in order to implement sandboxing on Linux. Field trials have long been a part of Chromium too: https://blog.chromium.org/2012/05/changes-to-field-trials-infrastructure.html https://blog.chromium.org/2012/05/changes-to-field-trials-in.... They are used to experiment with different solutions or, sometimes, to allow a change to be quickly reverted in the field if it's causing a problem. You can manually enable/disable several of these on chrome://flags/ (although it's not advised).
- xg15 9y agoAnd? All that is written in the article. The question is whether or not forcing users to partake in field trials is a good idea.
- agl 9y agoThe piece seems to suggest that a) multiple processes were the performance problem and b) that a field trial was causing that and "mak[ing] my computer unusable". Multiple processes do take more memory, but there's a good reason for them. While it's possible that it was a field trial that was causing issues here, there's no evidence to support that. Sadly, it was probably just excessive resource usage independent of any trials: Chromium did have a period where memory usage especially was allowed to drift and that was an oversight that Speed team are correcting (https://chromium.googlesource.com/chromium/src/+/lkcr/docs/speed/README.md https://chromium.googlesource.com/chromium/src/+/lkcr/docs/s...). On the other hand, field trials produce important feedback. One example just from today: TLS 1.3 draft 18 had significant issues with middlebox bugs to the point where it wasn't viable to deploy it. Chromium has been using field trails to test variants of TLS 1.3 intended to work around these issues and allow TLS 1.3 to be used for real. This has resulted in concrete changes to help TLS 1.3: https://www.ietf.org/mail-archive/web/tls/current/msg24908.html https://www.ietf.org/mail-archive/web/tls/current/msg24908.h... These sorts of things require large-scale testing. We brought all the middleboxes that we could find for local testing, but that cannot account for the variety of firmware versions and configurations used in the wild.
- millstone 9y agoThe love for Firefox seems misplaced, given that 1% of Firefox downloaders get a version that sends what you type to a third party (Cliqz). HN discussion was https://news.ycombinator.com/item?id=15421708 https://news.ycombinator.com/item?id=15421708
- prophesi 9y agoOnly 1% of German users. Yet, even though it affects only a super small set of users, it's still a ridiculous thing for Firefox to do. From the article: "One of Mozilla’s core privacy principles is No Surprises: we will use and share data in ways that are transparent and benefit our users. That is why we are telling you about this today. " Which doesn't make sense. If one of your core privacy principles is to tell your users what you're using & collecting, why not just tell them before/while downloading? Or better yet, let this be opt-in? This isn't big enough of a mishap for "the love" to be misplaced, but it is enough to always be wary of what even the most privacy-minded companies do with their products.
- deleted 9y ago[deleted]
- yongjik 9y agoWould the author be happier if Chrome/Chromium didn't do these "field trials", and instead just enabled whatever feature they were testing for all users, and the author was hit with the same problem, along with everyone else? When you cut through the rhetorics, the author is basically complaining that Chromium decided to update itself. Well, maybe it warrants complaint, but I fail to see what's such a big deal. (The alternative is millions using browsers ridden with last year's vulnerabilities.)
- CapacitorSet 9y ago>the author is basically complaining that Chromium decided to update itself. Well, maybe it warrants complaint, but I fail to see what's such a big deal. (The alternative is millions using browsers ridden with last year's vulnerabilities.) You're misrepresenting mandatory enrolment in A/B testing with plain software updates. Firefox is an example of a browser that does software updates, but does not force you to use potentially buggy features - and yet they do not have "millions using browsers ridden with last year's vulnerabilities", because their alternative is to give users a choice to enroll in experiments. I do participate in experiments since I wish to improve Firefox, but I could switch to any time to no experiments at all.
- yongjik 9y agoA/B testing is not some nefarious scheme to harm users. When Google or Mozilla wants to add a new feature, there are basically three choices: (1) Opt-in: Add the feature to the new version. Users must choose to upgrade. (2) Opt-out: Roll out the new version automatically, unless the user actively choose not to. (2a) Opt-out with A/B test: Roll out the new version to a small portion of users first, and proceed if nobody catches fire. Once you decided to use opt-out, there aren't that much difference between (2) and (2a). The major difference is that with (2a), a smaller number of users are hit when an unforeseen bug inevitably finds itself into release process. And of course we know what happens when something like a web browser relies on the users to actively click "Upgrade". I'm sure there are some people still using IE6.
- Anderkent 9y ago
- otto_ortega 9y agoFor a developer there is no better browser than Firefox Developer Edition 58+ at the moment, its new Quantum engine is insanely fast and the included developers tools are far superior than the ones on Chrome. I know Firefox had a dark period on which it felt behind Chrome on most fronts, but those days are over, if you haven't used it on a while, give it try! you won regret it.
- peterwwillis 9y agoAs lame as Firefox is, it always works when I need it to (unless I use add-ons). Thanks for sucking the least, Firefox.
- oatmealsnap 9y agoCheck out the Beta, or wait for Firefox Quantum to get released next week. It's FAST!
- peterwwillis 9y agoI don't need fast, I need a secondary browser. It can be slow as long as it works. (Firefox hasn't been fast or unbloated since Phoenix/Firebird 1.5)
- jdlyga 9y agoChrome honestly hasn't improved much in a while. It's kind of like where Firefox was back in 2012. Now that Firefox is faster and more efficient, maybe they'll start putting more effort back into it.
- yuhong 9y agoThis reminds me of this Twitter thread about DiagTrack: https://twitter.com/yuhong2/status/869631096719261696 https://twitter.com/yuhong2/status/869631096719261696
- yuhong 9y agoThe funny thing is that it is not difficult to prove the exact cause with a debugger and symbols in cases like this either. I wonder if doing what Process Explorer does (quickly suspend/resume threads and display call stack) would be easy in Linux though.
- ryuuchin 9y agoIsn't the answer here to just run the latest stable version where the impact of field trials would be minimized? Even the stable version will probably have features/field trials in the command line if you start looking at it for render processes. It was also never established if this A-B testing through field trials was to blame. It is a valid way to roll out new features to users while trying to minimize breakage. Most of the unstable stuff happens with the unstable branches in any case (dev and to a lesser extent beta). I do realize this isn't the best answer but I thought that the closer you get to canary/dev branch the more variation you'll be subject to. You can force field trials on and off at the command line if you know the option name and how to format it correctly. e.g. for some older ones: --force-fieldtrials="EnableWin32kLockDownMimeTypes/Default/*EnableAppContainer/Enabled/"
- arunc 9y agoIs chromium builds available on Windows (not Google's chrome)?
- kodablah 9y agoShameless plug, my browser is: https://cretz.github.io/doogie/ https://cretz.github.io/doogie/. I do no telemetry, surprise feature testing, etc. There are of course others, the best of which is Ungoogled Chromium, but they are a bit behind on their updates.
- finchisko 9y agoWhat happened to "Don't be evil?". Or they changed it to "Do not eval?":D. Bit off topic, but that guy experienced lagginess in UI due some rogue Chrome process. I remember some bug in VLC that slow down my computer to level, it was not even possible to type on keyboard. And I wonder, why is this happening in era of multicore CPUs? Why there is no restriction (by default) for process, how many cores it can utilise? I mean the tooling is already there (cgroups on Linux), but they're not used by default.
- deathanatos 9y ago1. I'm not seeing the causal link between the flag and the symptoms. I often find "Chrome" "causing" the same problems, but typically you can judge from the memory use that an errant tab is allocating the world, and you've started drawing on swap, which of course slows things down. But here we've cropped the memory stats out of the screenshot from top (for the system as a whole; we can see a few processes consuming a few hundred MiB, but Chrome loves processes, and there could be several more below, and summing RAM usage from processes is a deceptively tricky beast), and I can see nothing to prove that the field trial is even to blame. 2. You get the browser for free. If everyone adopted this same attitude, Chrome would not be able to do real-world A/B testing on features; what should they do instead, just release it all or nothing? You might have been unlucky today, but perhaps tomorrow someone else's misery provides the needed data to prevent a bad feature from going out. 3. Vote with your "feet", and switch to Firefox? (or one of the other myriad of browsers out there…)
- FascinatedBox 9y agoWhat other serious alternatives are out there though? I know of Firefox and Edge. But aren't Opera and Safari now reskins of Chromium, to some degree?
- dragonwriter 9y agoBlink (Chromium’s engine) was forked from WebKit (Safari’s Engine) and the two have developed separately. Safari is not a skin of Chromium or vice versa.
- friendzis 9y agoRegarding point 2: what if Tesla pushed silent OTA updates for A/B test that accidentally disabled ABS or traction control, rendering the car unusable? This is what I cannot grasp about modern software project management/ops. <s> The only relevant measure is time to ship. If the unit tests pass it is good to go. </s> So many times have I seen webapps so broken that core functions do not even load or by no means would pass simple "click here and there" usability test. In house QA sometimes seems to be abandoned. Automated testing is a good thing, but in my book shipping comes with implicit assertion that changes perform the task at least on a basic level. Field A/B testing of experimental features is a good thing, which I am ok with even if I happen to get worse alternative. Shipping outright broken features if I am not on beta/testing/nightly release channel is unacceptable.
- lima 9y agoThe author assumes that the field trial command line arguments are somehow related to the issue he had, which is not the case. Chrome is always running multiple processes and they always have a very large number of arguments, including field trials. He's just describing normal behavior.
- vardump 9y agoI once debugged an issue in another process on Windows that would only appear when Chrome was not running. Not sure if Chrome still always does it, but back then it was because Chrome changed timer tick frequency to presumably 1 ms by calling timeBeginPeriod (https://msdn.microsoft.com/en-us/library/windows/desktop/dd757624(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/dd7...). On Windows, this affects whole system timer resolution and caused problematic timing code in the other process to function correctly. Funny enough, earlier workaround was to only run this piece of software with a Chrome window open.
- md_ 9y agoThe article appears to assert two things: 1. Chrome runs field trials. 2. At one point Chrome locked up the author's computer. Does it ever connect the two points, or are they unrelated?