Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WTF? Chromium (2016)

raeknowler.com

Post reply on HN
Print view View original

31–40 of 112 posts

Re: WTF? Chromium (2016)

#31

Post by porfirium »

hathawsh wrote: post #25
porfirium wrote: post #3

The 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.

I don't think that's a fair assessment. The web site ( https://iridiumbrowser.de/ ) is nearly on par with the web sites for other big open source projects like http://python.org or 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".

I 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.

Re: WTF? Chromium (2016)

#32

Post by usernam »

tardygrad wrote: post #4

Or 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.

Firefox is not immune to this behavior. Please look up the preference "experiments.enabled" before recommending blindly.

In fact, Firefox has increased in the amount of unwarranted telemetry and "experiments" a lot in the last years, a direction I'm really not happy with.

The main difference is that Firefox still gives you pretty liberal access to most internal settings, while Chromium is abysmal, if not ridiculous.

Re: WTF? Chromium (2016)

#33

Post by otto_ortega »

For 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.

Re: WTF? Chromium (2016)

#34

Post by O1111OOO »

laurent123456 wrote: post #20
tardygrad wrote: post #4

Or 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.

Firefox is not slower, it's just that most websites are optimised and tested only or mainly under Chrome. We are slowly getting back to the way things were with IE, but I hope that Mozilla won't give up and switch to blink or webkit like everybody else.

> Firefox is not slower, it's just that most websites are optimised and tested only or mainly under Chrome.

Anecdotally.. Firefox was always slower rendering pages compared to other browsers. On some sites that I visited regularly, using FF was depressing. Later on, it started to suffer from caching issues on my machine. This caused a massive system slowdown.

Tried Palemoon (non-blink\webkit, etc). It blazed through pages- even the heavy ones FF had problems with historically. The rendered results were spot on too. It was like getting a new machine.

What I'm saying is that we can't blame everything on pages being optimized for Browser X or Browser Y. Sometimes we need to call out our favorite browsing application and let them know this is an issue. Otherwise, they keep losing users based solely on performance.

Having said that, looking forward to Quantum.

Re: WTF? Chromium (2016)

#35

Post by kibwen »

snowpanda wrote: post #28
tazjin wrote: post #23

Earlier quoted context omitted.

Same 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.

>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.

This 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

Re: WTF? Chromium (2016)

#37

Post by oatmealsnap »

JustSomeNobody wrote: post #22
fenwick67 wrote: post #16

Earlier quoted context omitted.

It seems crazy to me how may projects depend on Chromium and V8 directly. Hopefully with Firefox's new improvements some of this will change.

More to come with headless Chrome a thing.

Headless Firefox is a thing, too.

Re: WTF? Chromium (2016)

#39

Post by oatmealsnap »

porfirium wrote: post #3

The 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.

I don't get that sense at all. Looks like a generic "techy" Wordpress theme.

Re: WTF? Chromium (2016)

#40

Post by oatmealsnap »

fenwick67 wrote: post #16
edhelas wrote: post #2

I 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.

It seems crazy to me how may projects depend on Chromium and V8 directly. Hopefully with Firefox's new improvements some of this will change.

Aside from community support, what is preventing Firefox's JS engine from being used to power a JS runtime?
Post reply on HN