Live data from Hacker News

Helium Browser

helium.computer

191–200 of 561 posts

Re: Helium Browser

#191

Earlier quoted context omitted.

Gecko is too big to die. Even with Firefox’s market share being a shadow of its former self, it’s still used by millions. The real problems with Gecko is just that it’s harder to fork and has less compatibility with the web (that last part is largely just due to Chromium being the de facto standard so fewer people test their sites against Firefox).

> The real problems with Gecko is just that it’s harder to fork That goes contrary to my experience. I'm a maintainer of a Firefox fork (with rather extensive changes to a lot of the internals), and it is pretty manageable to maintain. We manage to keep it roughly up to date and add new features without financial backing or folks working full-time on it. If all you do is change the branding and apply some superficial…

Thats interesting. Thanks for sharing.

Why do you think that very few projects adopt Gecko then?

Re: Helium Browser

#192

> Helium is based on Chromium > Best privacy by default Sorry, pass... Even with un-googled Chromium I do not think these statements are self-consistent. We need browsers that do not allow Google to control the ecosystem. We need legitimate competition. So what, our choices are Firefox (Gecko), Safari (WebKit), and Ladybird? Personally I go with Firefox on most devices and Orion (WebKit) on my iPhone and iPad. > Heli…

Literally the first thing I looked for...(if it is based on chromium). When can we get a new kind of browser that doesn't use html/css/js...? Build one from scratch with a common design language (but modifiable by the user)

That would be a monumental task probably requiring tens of millions to be honest

Re: Helium Browser

#193

> Helium is based on Chromium > Best privacy by default Sorry, pass... Even with un-googled Chromium I do not think these statements are self-consistent. We need browsers that do not allow Google to control the ecosystem. We need legitimate competition. So what, our choices are Firefox (Gecko), Safari (WebKit), and Ladybird? Personally I go with Firefox on most devices and Orion (WebKit) on my iPhone and iPad. > Heli…

Literally the first thing I looked for...(if it is based on chromium). When can we get a new kind of browser that doesn't use html/css/js...? Build one from scratch with a common design language (but modifiable by the user)

This is a gargantuan task, I can’t even articulate how much work this would be.

Re: Helium Browser

#194
post #184

I was excited for a new Helium browser release and it just turns out that people these days don’t even do a single google search before using a name that is already taken. https://slashlos.github.io/Helium/

Wow, that's a real fuckup.

Re: Helium Browser

#195
post #189

Earlier quoted context omitted.

Hopefully the Ladybird browser will become a viable choice soon

I think we're many years off it even being viable for most people

They haven’t solved security yet. They are doomed to repeat Firefox/Chrome issues until they start using that Swift.

Re: Helium Browser

#196
post #189

Earlier quoted context omitted.

> So what, our choices are Firefox (Gecko), Don't forget Servo. People are actively working on it, and it could use more help.

Hopefully the Ladybird browser will become a viable choice soon

I hope that not. Or at least, get out of the control of the controversial person behind it.

If I would put all the eggs on a basket, I will prefer Servo.

Re: Helium Browser

#197

Earlier quoted context omitted.

Allow me to rephrase my earlier choice Chromium: Entirely dependent on Google, a $3T company who's entire business model relies upon invading your privacy and currently has a >70% global share of browsers WebKit: A closed source browser with ~18% of browser share and run by a nearly $4T company who forces all browsers on their mobile devices to be reskinned versions of their browser and probably wants to do the same…

> WebKit: A closed source browser You seem to be confusing Safari (a closed source Apple product), and WebKit (an open source browser engine used by multiple browsers).

You beat me to this comment. Webkit is not an apple only thing

Re: Helium Browser

#198
post #135

> Helium is based on Chromium > Best privacy by default Sorry, pass... Even with un-googled Chromium I do not think these statements are self-consistent. We need browsers that do not allow Google to control the ecosystem. We need legitimate competition. So what, our choices are Firefox (Gecko), Safari (WebKit), and Ladybird? Personally I go with Firefox on most devices and Orion (WebKit) on my iPhone and iPad. > Heli…

Security isn't just about your data. It's about the security of an open web. Having one rendering engine that controls everything is not secure.

It's actually the beauty of open source that we can align on a few primitives that are reusable in several different contexts to build radically different product experiences and world views. If you think of the phylogenetic tree of software this is exactly what you want to happen.

Re: Helium Browser

#199

> Helium is based on Chromium > Best privacy by default Sorry, pass... Even with un-googled Chromium I do not think these statements are self-consistent. We need browsers that do not allow Google to control the ecosystem. We need legitimate competition. So what, our choices are Firefox (Gecko), Safari (WebKit), and Ladybird? Personally I go with Firefox on most devices and Orion (WebKit) on my iPhone and iPad. > Heli…

Safari should be on Windows. I don't care what CSS standards it has, it needs to give Chrome and Firefox some competition

Re: Helium Browser

#200
post #186

Earlier quoted context omitted.

> Maybe because it(Apple) is slow to adopt standards I think this is an interesting bit of propaganda - they are historically not all that slow to adopt actual standards. What they often are is unwilling to adopt Google's pre-standardisation extensions (things like WebUSB, which have never been adopted as standards).

WebGPL, WebRTC, Gamepad API, WebASM etc Years behind Gecko and Chromium. Don't get me started on codec support with Safari. Webkit is the new IE.

WebGPU not yet a W3C standard (it's at the previous step, as a "candidate recommendation"). Apple's WebGPU implementation went live before Firefox's implementation.

WebRTC went live in Safari the same year that the non-draft version went live in Chrome (Chrome supported the pre-standard webkit-prefixed version for some years before).

Similarly, Safari added support for WASM the same year that WASM was standardised (once again, Chrome supported a pre-standard version ahead of standardisation).

Post reply on HN