But this is no excuse: In no way should the development environment leak out into a released product this way! - And it would be exceptionally easy to stop this too: Just disable all development flags in the release build.New updates are being added at the bottom of this story……. Note: I fully understand that in Chrome these flags at least partially leak out of their "trunk-driven development". I absolutely despise it when a software product pushes effort downstream this way. Both for the actual developers and the users.
And it would be so much more understandable. In fact, I think maybe about 20 command line options would cover 99.9% of all usecases for chrome. But it is much harder to think about whether a user would actually ever want to change the setting, if it had a good default value. The problem here (at least in part) is that it is extremely easy for devs to just add a configuration option. Well, at least not in the ridiculous way that Chrome or Firefox do it.Ĭommand line options or config files are both fine - when used in moderation. > Well it's either flags, or a config file (And I have never found a Linux Firefox config on any piece of hardware that can reliably play videos on Reddit, which makes me think it's not handling video acceleration properly.)ġ: The one exception: when I was running a low-latency audio app on that Chromebook which grabbed exclusive control of ALSA. That is- as long as you spend non-trivial time in a browser, it's more efficient to do Linux-Inside-Chrome than Chrome-Running-Inside-Linux. Those things being true, it makes more sense from a performance standpoint to use Linux from within Chrome than the other way around. Add to that the fact that I open and close that Chromebook at will with the browser in nearly any state, and it never got hot, crashed, or failed to come back up when I reopened it. That makes me think I've gotten used to a fairly high floor of latency on my Linux machines.Īdd to that the long battery life while browsing in Chrome. It's as if there's some ahead-of-time trick that utilizes the camera to guess my impending trackpad click or keystroke. I speculate without measuring because switching browser tabs on that Chromebook feels uncanny. That includes this Dell XPS laptop running Ubuntu, which is fast and well-supported with firmware. I didn't measure it, but switching tabs in an Asus C201 Chromebook sure seemed to have a much lower latency than tab switching (or clicking on a different app in a menubar) for any Linux distro I've ever used on any piece of hardware.
0 kommentar(er)
