Hacker News new | ask | show | jobs
by zobzu 4596 days ago
TBH JDK has open, 3rd party implementations. I'm running one right now.

Chrome's API don't have this. Chrome == Chromium, and there's nothing else under the sun that either have it or want it.

HOWEVER - Chrome has the largest marketshare by far, thus enforcing whatever it wants. Knowing competitors will not pick up the functionality because "its really made just for Chrome, not for the open web", that's called "extinguishing" competitors. But I'm sure everyone is all too familiar with that concept.

1 comments

jdk is not open source, or wasn't at the time. So 3rd parties open implementations were required. Chrome through chromium is an open implementation by default and it's highly maintained, tested and optimized. Reimplementing it wouldn't make much sense and so would complaining about the lack of implementations.
> Reimplementing it wouldn't make much sense and so would complaining about the lack of implementations.

I do not think that Chromium represents the best possible implementation of the Web stack. Having multiple implementations of HTML and the various related specs is what has pushed them forward so rapidly.

so you say we should ditch all browsers and only use chrome. my issue VERY exactly.