Hacker News Reader

Comment by anaganisk | Hacker News Reader

This is such a bad faith argument whenever I see it, when an end-user is commenting on a project, at least that is funded and has a dedicated team working on it. Asking for something to be fixed, doesn't have to warrant such a reply. I can see if it was some obscure project or some solo dev project, but it's run by Google for gods sake. People don't like it, but even if you are a solo dev open sourcing your stuff a product that expects non tech people/even Js developers, expecting them to open a PR for your coded in some low level language instead of letting you know how much priority it might take is wrong IMHO.

View on HN

What we also forget is that Chromium (+ HTML, Javascript, SVG, ect) is starting to be in a market dominance position where Windows was in past decades: We're at the mercy of a market winner who improves it at their pace.

At times, it appears that web standards have evolved from their open nature to primarily supporting Google's agenda. If Google wants a certain product to run the browser, they will bend the standards to do that.

I bet as soon as a Google product needs this feature, the bug will be fixed.

Oh, probably. That's a pretty standard pattern; I know of a feature that was lacking from Apple's window manager until they found a need for QuickTime to use it and added it in.

This is called "the paranoid style", political scientists talk about it as a unique feature of American politics.

It's hard to interact with because falsifying it requires invoking it yourself.

ex. here, we'd have to say "I bet you'd be right here complaining if it was fixed that Google was allowing arbitrary remote loads in not provably secure context." It requires a whole lot of supposition and negativity.

But Chromium is open source. Opera and Microsoft, among others, contribute frequently. Igalia is a consulting firm that takes commissions for Chromium browser work. So the correct statement would be that anyone with enough time and/or money could make this work, not just Google.

I agree with what you are saying.

But this guy from Russia came in, threw a fit and was never heard again in this bug.

And still, the reply was polite.

I am sure there are tons of more bugs in the chromium project that are 10 years or older. Some things are just more critical than other.

Posting this link to HN (and then describing some unrelated events of the last decade) is asking for it to be fixed? No, it's just griping loudly about one's pet bug, which is one of a zillion in a project as large as Chromium, hoping that somehow this shames Google into reprioritizing it.

>but it's run by Google for gods sake

So? Google still has a team assigned to the project, and that team has limited people, and it also has preferences and priorities.

Reply on news.ycombinator.com