News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Latty on Friday April 13, 2018 @09:38AM (#16829836)
I can make a self-driving train far more easily than I can make a self-driving car.

You are comparing two things that aren't equivalent. The living standard provides a lot more value than the old specs, and that's why they won.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Friday April 13, 2018 @09:41AM (#16829862)
The living standards winning is something we should see as tragedy, not as something good.

We’ve made parsing the web something that only massive corporations can do. We’ve made building a browser so complicated that even Opera gave up after the complexity of HTML5, and we’re now left with only 4 major browser engines, of which 2 share a significant amount of code.

Do you see an innovative ecosystem there?

We’re left with a web that can’t be parsed, we’re left with a web where, to run Selenium tests, we have to run Chrome headless, because nothing else can even attempt to render websites anymore.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by chrisseaton on Friday April 13, 2018 @09:45AM (#16829892)
> Do you see an innovative ecosystem there?

Yes! Everyone says that the specification approach is what was severely limiting innovation, and when they took the living specification approach instead that's when web innovation took off again.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Friday April 13, 2018 @09:48AM (#16829918)
Oh? How many tools do you know that can parse a current HTML5 react app without importing any existing browser?

Every tool we have to use on the web relies on 4 existing tools that only major companies can build.

I’ll pay you $100 if you manage to write, in 4 weeks, a browser, from scratch, that renders a real life React app accurately, including all content, without importing a single bit of code or libraries from existing browsers or web tools.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by sangnoir on Friday April 13, 2018 @10:49AM (#16830463)
> Oh? How many tools do you know that can parse a current HTML5 react app without importing any existing browser?

I don't recall XHTML deprecating JavaScript- pray tell, how would you render the XHTML version of a react app without a browser, or a JS engine as a bare minimum? (X)HTML is orthogonal to Js/react.

I could develop a self-driving car for $50 000 (instead of millions) if human drivers and pedestrians started behaving in well-defined patterns, following strict rules and stopped doing stupid, unexpected things. I'd really love that, but it's not going to happen even though there already are "standards" in the law books.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by chrisseaton on Friday April 13, 2018 @09:56AM (#16829992)
You asked about innovation, not how easy it is for new people to enter the market. Innovation in browsers has definitely gone up and as a user I feel like I'm winning from this with better websites and more powerful web apps.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Friday April 13, 2018 @09:59AM (#16830019)
How many new browsers do you see? Is that innovation in browsers? Browser competition and innovation is at its lowest ever. Chrome holds 2/3rds usage globally.

I don’t want more powerful ways to display ads, I want to get more content, better connected, without any of the fluff around it.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by chrisseaton on Friday April 13, 2018 @10:08AM (#16830097)
> Browser competition and innovation is at its lowest ever.

I don't care directly about competition, because that's just a means to an end, and the end I care about is innovation, and I don't agree that innovation is low - I think it's high. New HTML features are coming out in a fast continuous stream, unlike how it used to be.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by tptacek on Friday April 13, 2018 @10:38AM (#16830367)
What does it even mean to parse a React app? Crawlers can't resolve the halting problem, either.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Friday April 13, 2018 @10:43AM (#16830406)
> Crawlers can't resolve the halting problem, either.

And yet, that’s where we’re at today. Blogspot posts require JS. So many other pieces of content are similarily built.

And with phatomjs gone, we’re now running entire headless browsers just to test if websites are rendered correctly. It’s insanity.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Latty on Friday April 13, 2018 @09:47AM (#16829911)
Yes, and before that there were maybe 1.5 viable ways to render flash content.

Then you need to take that `.exe` and try and pull out it's content. Game, app, whatever.

We have a web that can be parsed, with difficulty, instead of a web without half of the content we want to parse.

The web was being replaced - this is what saved it, like it or not.