Comment by tsimionescu
7 months ago
The most likely answer is that it will take the Linux model, with a foundation put together to fund Chrome's development. Then all of the parties interested in people having access to the Web, including Google, will have an incentive to fund this without requiring it to push their specific products.
Chrome currently has far more paid full time engineers than the linux kernel does. I struggle to see how they get paid - except again, by charging search engines to be the default browser or something.
Chrome does a lot of things. I know there are downsides and many people don't agree, but I think overall the browser/internet experience would benefit from simpler browsers that don't move so fast.
> I think overall the browser/internet experience would benefit from simpler browsers that don't move so fast.
I wish browsers moved faster so that I don't have to download so many native apps. Native mobile apps are monitoring me continuously, and way more opaquely than web apps. More importantly, they can't be thwarted by plugins. As a mobile Firefox and Desktop Chrome user, I wish browsers (especially FF) moved faster.
So, no - for privacy reasons I don't agree with your view.
2 replies →
IMO, Chrome does not move fast enough.
The fact of the matter is that the web has been dying because people have moved to mobile devices, where they prefer native apps.
If you're advocating for slower development of browsers, you're also advocating for the death of the open web.
9 replies →
Simpler browsers sound not good to me. It's a bit of a rallying cry on HN it feels like, often in sharper terms.
But computing is so intermediated. There's so many checks to do anything on an iPhone that isn't in the dead code your phone already runs. An Oculus has cool experiences, but we can't shape and share our own easily. There's always someone else's data center between you and your device today.
The web is largely still an experience of data centers too. But it's a neutral platform. Where we can go to any data-center we please. Where anyone can tap the amazing web platform & it's amazing APIs to build all kinds of cool experiences.
In a world where tech defines what the user wants for them, I feel so much like the web & every web platform API is stealing just a little more fire from the gods. It's promethean, giving to humanity prowess & capabilities we wouldn't otherwise have.
The pace is confusing. Sometimes things happen fast. Often they are left sort of unfinished. Fast & slow, fast & slow. I'd love if there was a huge source of funding the societies of the world were putting up to help make this critical human capability, to to fund long careful slow healing and helping as well as fancy new features (es2015/esm modules in the browser tool sooo long & still has so much to fix for example). These things are hard, complicated, and we try so hard to keep going forward without causing too much unfixable undislodgesble bad. But this spirit of bravery is necessary, to keep going. Simpler isn't good. The versatility of the web is too important. There's no other viable substitutes for the capabilities being available on the web, no other paths we have to stealing fire from the gods, no other Promethean dreams. This platform is it, and we need the persistence & drive as a society to keep ourselves improving our shared interactive media form, to keep from being swallowed by the darkness that most computing brings in.
I agree. They jam everything but the kitchen sink into the damn browser these days. Chrome being so well staffed and fast moving means everyone else gets to play catch up and it's bullshit.
Google can keep engineers working on Chrome employed without having control over Chrome.
But why would they if they're forbidden from getting any benefit from Chrome?
6 replies →
I am not sure that is a good thing. Do we really need so many people working on it, or adding more and more features?
IMO more engineers = more bloat, rather than more engineers = a better product.
> Chrome currently has far more paid full time engineers than the linux kernel does.
Are you sure? Do you know how many people work on Chrome? 2,000 people contributed to Linux 6.12. only a small portion of those will be full time but it's still likely many hundred full-time-equivalent engineers.
I think so. About a decade ago I remember hearing that the chrome team had about 1000 full time engineers. I suspect the number has grown over time.
Looking at the number of lines of code, the linux kernel is just barely ahead of chromium now (39m loc vs 36m). But that doesn't include all the proprietary parts of chrome that aren't in chromium - like their binary updating system, h264 decoder, built in google account support, and so on.
https://openhub.net/p/linux/analyses/latest/languages_summar...
https://openhub.net/p/chrome/analyses/latest/languages_summa...
That may be, but Firefox certainly doesn't, and it's not that far from Chrome in terms of feature set, particularly in terms of supported web standards, or security. So I don't feel that a smaller Chrome team would be a catastrophe for Chrome.
At the same time, if every company that actively make money from the web where to pitch in, we would have the most funded foundation in the world.
One minor nit, it will be all parties interested in influence over future web standards and their eventual implementation.
Right, those would have the biggest incentive. But I'm sure good fundraisers will be bale to even get some large companies that aren't engaging in the standards at any level to throw some money to support a standard web browser, if they can convince everyone that without this there won't be a good way for people to access their web sites.
I suspect that the leading reason browsers require so much investment and development effort is the ongoing effort to engineer them into heavily surveilled application delivery platforms.
Most of the browsers in this list were developed by the open source community without major funding: https://en.wikipedia.org/wiki/List_of_web_browsers
Though the same browsers tend not to support many of the newer standards.
I kind of miss SGML, myself, and wonder if a slower pace of browser development and associated code churn might actually be more benefit than harm.