8 ms·
As cool as Brave is, I still think it has big issues running Chromium. Chromium still allows Google to dictate a lot of the internet. We should have more compet
by godelski 4y ago
As cool as Brave is, I still think it has big issues running Chromium. Chromium still allows Google to dictate a lot of the internet. We should have more competition in the space and that will help us all. I honestly even wish there was more than Chromium (and the various colors), Safari, and Firefox. It really seems a lot of these decentralized services have become highly centralized and thus a lack or competition and growth.
- endisneigh 4y agoI respect your opinion but honestly fragmentation sucks. I wish there was even more consolidation - ever use a power drill? 7 different battery types non compatible with each other. On a related note I’m happy usb seems to be the general connector winner (though it’s certainly not without fault). What would the average consumer gain if there were say, 10 different browser engines equally popular? Chromium is open source and you can easily disable features you disagree with. Don’t see the downside. Fork it and add functionality you’d like, like Brave.
- marricks 4y agoA lot of if there was an independent web consortium which agreed on standards. Which, hey, we do have and the more power chromium gets the more Google can just ignore that.
- mike_hock 4y agoThe same the average user gains from having 10 manufacturers to choose from when buying standardized USB connectors.
- endisneigh 4y agoMore browser engines does not imply standardization. Would you prefer the 2000s when you had your choice of dozens of power connectors for cell phones? There’s a reason the EU is mandating USB-C. Corporations have no reason and historically will not standardize amongst themselves for most things unless there’s a single winner.
- cowtools 4y agoCompletely backwards reasoning here. The protocols (standards) and implementations are to be considered separate.
- deleted 4y ago[deleted]
- fsckboy 4y agoMore browser engines does not imply standardization. There’s a reason the EU is mandating USB-C when you can plug your USB-C internet into either chrome or firefox without thinking about it, you have standardized.
- xypage 4y agoI'm finding it hard to give you the benefit of the doubt because it really sounds like you're advocating for a Google monopoly, which doesn't help anyone. Sure having a bunch of different battery types is annoying but in that case either you should find a brand you trust and stick with them, or brands have fragmentation within themselves which is a different issue altogether. The "fragmentation" you're talking about here is competition though, there isn't really any downside to having a bunch of different popular browsers and the upside is that none of them get to do anything crazy knowing there's no serious alternative so you can't leave. Google is already invasive of privacy, I can only imagine it'd be even worse if they didn't feel like there was significant risk of people switching browsers because nothing else was popular.
- endisneigh 4y agoGoogle is not really the point. The point is that there’s a single standard. Doesn’t matter who’s it is to me. > The "fragmentation" you're talking about here is competition though, there isn't really any downside to having a bunch of different popular browsers and the upside is that none of them get to do anything crazy knowing there's no serious alternative so you can't leave. If this is your opinion then what difference does it make if there’s a monopoly? You can use Firefox or Safari no? Not to mention chromium is open source. Anyone can fork it, like Brave in FTA. I don’t see any downsides, given that you can disable and features you object to.
- garblegarble 4y ago>The point is that there’s a single standard An implementation isn't a standard, though... and the concern is that Google are using their dominance here to push more half-baked ideas (some of which they then discard, see HTTP2 Push)
- untitaker_ 4y agoAn implementation isn't a standard, yet reference implementations exist, and yet the WHATWG standards are written in pseudocode.
- bombcar 4y agoI'm glad there are multiple different power-tool manufacturers, and I'm not entirely sure there'd be as much competition if they were all forced to use one battery connector. (You can buy adapters if you want, but it's generally not worth it).
- endisneigh 4y agoWhy are you glad that there are multiple battery connectors? Makes no sense to me. It’s like disagreeing with AA batteries. It’s like electric cars having different chargers and no standard.
- bombcar 4y agoBecause the companies can develop different toolsets that do different things (the weight/power tradeoff for one, some battery connectors allow more than just voltage to cross, but also information and the tool can work with the charger/battery to produce better power), and for me the actual downsides have been minor or none. Even construction guys often have a huge mix of various tool brand and battery types and it's sometimes a minor annoyance. And you'll notice that AA batteries are almost universally ... gone; replaced with built-in batteries or custom-wrapped lithium batteries. Standards are great when things are calmed down, but when there's rapid advance they can cause their own issues (we saw this in the wireless world). Even the electric charger for cars thing runs into the limits of the standard (the fastest charging is almost always non-standardized). Having a "baseline" standard for those could be nice, something like we have with USB, but even that has its annoying problems.
- smegsicle 4y agolong live 18650
- bb88 4y ago> And you'll notice that AA batteries are almost universally ... gone; replaced with built-in batteries or custom-wrapped lithium batteries. Ever open up a Dewalt battery pack? It's a circuit board and a whole bunch of 18650's. All of them are 3.7 V. What's different is the amount of power they supply and the energy they hold, how fast they can recharged, etc. But we have that with the AA/A/C/D standard as well. Some batteries can hold more energy, some can deliver more current for a longer time, etc. NiCad, Alkaline, NiMh... etc.
- pawelk 4y ago> ever use a power drill? 7 different battery types non compatible with each other. Battery is the proprietary part. The engine (battery + motor) makes it spin, but for the purpose of making a hole or driving a screw one can use a wide array of standardized bits from various manufacturers. You may need an SDS adapter (one way or the other) and that's it. Same bits will even work with a hand cranked drill press built 100 years ago.
- michaelmrose 4y agoThere is some consolidation among power tools https://toolguyd.com/tool-brands-corporate-affiliations/ https://toolguyd.com/tool-brands-corporate-affiliations/ They still screw you on batteries and indeed would do so harder if there were fewer companies. Instead of incompatible batteries per brand it would be per year. Sorry sir that's a 2022 tool it can't use 2021 batteries. You can either ask congress to establish a standard, start a power tool company that supports more brands with adapters, or basically suck it up because selling batteries way over cost is extremely profitable and nobody wants actual competition in that space. The one thing you don't want is consolidation. Likewise you think you want consolidation among browser engines but you really don't because it gives the vendor future leverage to fuck you.
- nocman 4y agoThe point you seem to be missing is that Chromium isn't a standard. If you want to reduce fragmentation while avoiding having one entity with too much control, the solution is fair setting of web standards and multiple browser implementations from different entities. Requiring everyone to "just fork Chromium" would leave far too much power in the hands of Google (as if they didn't have far too much power already).
- jrochkind1 4y ago> ever use a power drill? 7 different battery types non compatible with each other. OK, but do you think you would be well-served if this problem were solved by there being only ONE manufacturer of power drills, take what they give you at the price they charge or nothing? It would be one way of solving the problem of lack of standardization of power drill batteries. It is the analogy of what you are speaking in favor of by analogy. The better solution might be multiple drill manufacturers agreeing on a battery standard to all use together, so their batteries can be interchangeable, but you still have your choice of different competing drill and battery manufacturers. What would be the analogy with browsers, do you think?
- eropple 4y ago> What would be the analogy with browsers, do you think? It wouldn't be "use a single browser engine codebase owned by a single company", and that does seem to be the point advocated for here.
- bb88 4y ago> OK, but do you think you would be well-served if this problem were solved by there being only ONE manufacturer of power drills, take what they give you at the price they charge or nothing? Imagine having 20 different gas guzzling cars with 20 different proprietary fuel inlets. If you buy an Audi say, you'd have to go to the Audi refilling station. > What would be the analogy with browsers, do you think? There's no need for analogy -- we've experienced this in the past, e.g., MS ActiveX and other Internet Explorer bugs (or features). There's also the proprietary web, e.g. SilverLight and Flash, before HTML5 Canvas came along. And then HTML5 was a branding effort. Browsers needed to support it to be marketable to the general public. Things just started working again without needing to install plugins or to keep plugins up to date (Flash) -- it was a better web. The W3C could do this if the web gets too fragmented again.
- godelski 4y agoWhat a strange argument. The diversity in cars helped set the universality in the gas port. The same thing is happening with electric vehicles. Yeah, there are some proprietary ones like Tesla, but as more manufacturers have gotten into the space there have become standards as companies realize that a standard charging port helps them beat Tesla (being a united force). Network effects are real.
- brnt 4y agoFragmentation sucks, but code monopoly even more. A healthy ecosystem needs a plurality of implementations, or Chromium needs to come under committee control. (W3C? Something like the C++ standards committee.)
- blowski 4y agoBuilding a general purpose browser must be insanely complicated challenge with very little reward. It would be interesting to see more niche browsers for browsing specific types of site, though.
- bombcar 4y agoThe only way a new browser engine will be written in this day and age is if a massive company throws absolutely billions at it (Microsoft and Apple have both given up on this) or a competing browser on the Chromium engine gets popular enough that they become the main fork and begin to diverge. I don't really see any other way until HTML and the web is replaced by something else entirely.
- chrisseaton 4y agoWhat browser engine did Apple give up on?
- bombcar 4y agoThe sarcastic answer would be "webkit" but technically Chrome forked from that.
- chrisseaton 4y agoYeah I’m not sure Apple has abandoned any previous engine they worked on - it’s all been incremental for them.
- thrdbndndn 4y agoI think this point often isn't mentioned enough to be fair. Chromium is a ridiculously complex project. Most of these "independant" browser teams are simply not capable to create a browser from scratch. I'm not saying people should praise Google or anything since they obviously have interest in it, But Google is still the one who (mostly) build chromium and leave it open source (I understand they have to since it was originally a fork of Webkit, but I feel Google can do it from scratch if they wanted). Without it none of these browsers would exist. If anything, why almost no one uses Gecko/Firefox as a template/start point instead is a more interesting question, TBH.
- gjsman-1000 4y agoBuilding a web browser that is feature-complete, bug-compatible with Chromium, and relatively secure is about as complicated as building a whole operating system from scratch. Plus, as Mozilla has learned, nobody ever made money from selling web browsers. Costs a fortune to develop, makes almost nothing in return except for influence or protecting other businesses. Plus, why the heck would you do that if Chromium is open-source? It's completely pointless.
- jrm4 4y agoDo we have to Stallman this question again? Building from open source mostly controlled by a big-ol company is the opposite of future-proofing, especially when "connectedness" is part of that company's bread and butter. Just having access to source doesn't guarantee much in this day and age.
- jjcon 4y agoChromium isn’t written by just 1 entity, Microsoft intel samsung have all made major contributions - and anyone can hard fork it if they want to. I know most others here disagree but we do need standardization in this modern web world and chromium is just that. Even if we don’t like it, the reality is what it is. Firefox is dead (about the same market share as ‘samsung internet’ these days). It would be best if we worked to make these web standards (chromium) bend to our collective will (like brave or Microsoft) rather than chasing pipe dreams of a Firefox return.
- cowtools 4y agoFirefox market share is dying because of this mentality that is killing it. Self-fuffiling prophecy. The standardization is in the standard, not the implementation. You do not need everyone to use the same implementation in order to have standardization: that just allows the implementer to bend the standard to his will.
- gjsman-1000 4y agoNo. Firefox has been dying for, what, a decade now (losing market share since 2013)? The only people using Firefox are the people who care about Firefox as a product and a competitor, which is (in the grand scheme of things), almost nobody. Everybody else left, often with decent enough reason. Google recommended Chrome, Chrome was faster for a long time, Firefox stagnated and put ads and sponsorships everywhere, and wasn't better in almost any respect for a normal user than Chrome.
- mmastrac 4y agoAlmost everything everyone accuses Mozilla of and uses as their reasons for leaving is far worse in a Chrome ecosystem. It boggles my mind how people can complain about X and then jump to chrome where X is just as bad or worse.
- gjsman-1000 4y agoAh... no? Firefox, before Quantum, was slower than Chrome, had worse battery life than Chrome, and (on a Mac) was way louder than Chrome. And by the time they mostly fixed these problems, there was basically no reason to use Firefox other than it wasn't Chrome - which, other than to a developer, is not a selling point to the masses.
- deleted 4y ago[deleted]
- silisili 4y agoI'm glad it did. They made an amazing browser at light speed that people actually want to use due to that decision. The interesting question to me is...what happens if Brave gets bigger than Chrome. Like how Ubuntu did Debian, on the desktop at least. Does Google nix Chromium? More restrictive licensing? Curious the outcome.
- nicce 4y agoThe speed is caused by filtering many ads by default. Nothing rocket science what you could not do with browser extensions by yourself.
- silisili 4y agoI was referring more to development speed, if that wasn't clear, my apologies. That said, it is also speedy to use for the reasons outlined.
- jacooper 4y agoI used to refuse Chromium for the Same reason. But honestly it already happened, Firefox is already irrelevant. Mozilla is mis-managed organization that is funded to avoid anti-trust investigations, they dont fully push for privacy because they are afraid of google, do out of touch changes, and focus on political advocacy. Compare that to brave, which builds its own independent search engine, ad network, and has privacy by default in its products. There is no hope that Mozilla and Firefox will change the status-quo anytime soon, Firefox is losing users at crazy rate, and Mozilla is absolutely failing to do anything to change Firefox's destiny towards irrelevance. Brave is almost everything Mozilla should've been. Actually do what they sey, no hidden google analytics in their products, no unique ID for each installer downloaded, push for privacy by default and independence from big tech, not being shy from google, because they are their only income. I would argue, that if Mozilla wants to turn its course around with their "limited resources" it should drop gecko, and anything irrelevant to the users experience. Fork Chromium, the best web engine out there by a mile, and remove any anti-privacy / anticompetitive code, while still taking advantage of the huge development resources directed to chromium from many parties, and maybe Mozilla can also influence Chromium's development. Start pushing privacy by default, its the reason brave is gaining users at such a rapid pace, its a browser I recommend to everyone, as just by installing it they already are much more private than with chrome. What matters is the users experience, its why brave is growing.
- ravenstine 4y agoI totally agree that Mozilla is mismanaged, but I'll still take a mismanaged and politicized Mozilla over a tentacle of The Google any day. And that's precisely why I use Firefox. In response to the comment you were responding to, I don't know why anyone should care about how relevant Firefox is. For every browser someone invents, there will be someone claiming how bad it is from a security standpoint because reasons. Whatever. I can't keep changing browsers every time someone on HN says my browser is flawed or that the company behind it sucks. Unless things have changed, there are things about Firefox that I want that Chromium doesn't have. Can I disable history entirely in Chrome? Last time I looked, nope. Can I have multi-account containers? Nope. Can I block autoplaying videos? Nope. Can my ad-blocking not be nerfed? Nope. Can I not have the settings flags get taken away so frequently? Nope. I'm sure there's other things as well. If Brave went the road of completely relying on its own browser engine or a fork of Chromium, I'd be all in. The longer Brave is around, the more likely I might make the switch. Another reason I don't want to leave Firefox is I've seen plenty of new and hip web browsers come and go.
- armchairhacker 4y agoyou can still use Konquerer or any old / niche browser if your site isn’t using the latest HTML/CSS features and Javascript APIs. The issue is that webpages are incredibly complex - they can be full-scale applications - yet they are expected to run the exact same in different browsers, down to subtle implementation details. So in order to make a new browser you would basically be reinventing Chromium. Or you could start fresh with a new language to write websites in complete with a new browser engine. I would actually love this, web design today is a huge mess with HTML / CSS / JS quirks and backwards compatibility. But you still have the literally trillions of existing websites, which you’ll have to support with Chromium or Gecko until the end of time. And more importantly, you have the 99.9% of users who are still using Chromium or Firefox and won’t be able to use your new website, so you’ll have to backwards-generate HTML/CSS/JS from your new script anyways.
- jefftk 4y ago> you can still use Konquerer There are only three actively developed full browser engines (WebKit, Blink, Gecko) [1], and Konqueror runs on WebKit. (It used to use KHTML, which WebKit began as a fork of) [1] https://www.jefftk.com/p/browser-engines https://www.jefftk.com/p/browser-engines
- brnt 4y agoSince Qt doesn't come with WebKit for some time now, I think Konqueror is for all intents and purposes orphaned. Its outdatedness breaks the Oauth2 flow for setting up Gmail calenders/contacts in Kontact.
- jgalt212 4y agoChromium still allows Google to dictate a lot of the internet. IE6 still allows Microsoft to dictate a lot of the internet. the more things change...
- concinds 4y agoThe problem with that argument is that browsers don't compete on engines but on features, UX and integration (and bundling). All an engine is about, is webcompat (and Chrome wins here). It's literally not a differentiating feature. A good engine is an engine that never, ever fails to render a webpage (again, Chrome wins here). Even if Gecko was fully on-par with Blink (I keep hearing from Firefox users that they struggle with some websites, though admittedly very few, but Chrome obviously works fine with them), they'd have just invested millions in man-hours to get to the starting line, and have webpages not fail to render. A lot of companies might switch to Firefox if they switched to Blink and webcompat was never an issue. I've argued before that Firefox would benefit from switching to Blink (and gain better security, webcompat, enterprise support, and on and on), save tons of manpower and money, and compete on privacy, features, integration, and things users actually care about, as well as keeping Manifest v2, and patching out other Chrome-badthings. But that's basically Brave.
- perryizgr8 4y ago> The problem with that argument is that browsers don't compete on engines but on features, UX and integration Not always. Firefox lost much of its userbase not because it had less features or integration or was failing to render pages. In fact it was the preferred browser for most sites, with devs targeting it and testing on it. It lost because the engine was just inferior, which made it slower than the competition.
- concinds 4y agoYeah, you can extend my argument beyond webcompat to speed, security, etc. An engine that is better on these metrics is a better engine. My point (which I somewhat misstated) was that having the best engine is the bare minimum; it just brings you to the starting line. And if you don't have the best engine you'll always lose. (Sidenote: Evernote learned that lesson the hard way. Focus on core product, not marketing. Chrome's dominant, not just because of its marketing, but because it was a fundamentally superior product from the start; you can dominate a market with an inferior product based purely on marketing, as Evernote showed, but never durably). Hence why trying to compete on engines makes little sense to me. Since so many top corporations are contibuting to Chromium (Samsung, Intel, Microsoft, more), it's difficult to call it "Google's browser engine" anymore. The "engine competition" model makes sense if all engines are proprietary. Then, competition is the only way to push for improvements. But with every major browser engine open-source, it's better to concentrate efforts onto one engine. Imagine if every Gecko dev was contributing to Chromium instead of (somewhat) reinventing the wheel? Would Chrome not get faster/safer? It's a bit like if there were "multiple Linuxes", developed independently, that all rigidly had to be compatible with the same APIs/userland (/implement web standards). No, there's just one Linux. Google still wouldn't control the web (actually, they'd control it less if Mozilla's a stakeholder in Blink than with Mozilla doing their own thing and becoming increasingly irrelevant), since each browser dev can patch things into and out of Blink for their own browser (like Brave does); while still sharing all common contributions back with all other Chromium browsers. Win-win.