Tim Berners-Lee: 25 years on, the Web still needs work
cnet.com
cnet.com
It is a very sad couple of years and I don't know the solution.
Also, looks that you have no idea how much work Apple has done to propel the things that we now take for granted: canvas element, CSS transforms and animations, all the initial work on WebKit before Google joined in (yes, I know it is based on KHTML, but it has none of the aforementioned staff before).
There is no wonder you don't know the solution: it is hard do find a solution to nonexistent problems. No matter what you think, technology is not a zero sum game, and the web is not supposed to rule it all.
http://www.theatlantic.com/technology/archive/2012/12/bruce-...
http://www.wired.com/beyond_the_beyond/2013/04/text-of-sxsw2...
Consider as much as people complain about walled gardens DNS is quietly backing the 'open' web because some things really do work better as a walled gardens.
The Web started out being simple, so the barriers to entry were low and people easily got into writing pages to share information with others. Now anyone who wants to build a website gets bombarded with dozens (if not hundreds) of frameworks, libraries, application platform, etc. and it makes them feel like they have to somehow learn and use all of this new stuff, because they're given the impression (mostly from big commercial sites) that they have to do so or their site will "look outdated". I think we should encourage more "just writing webpages", with an emphasis on (mostly static) content, and less on the "app-ification" currently going on.
As much as this is probably not a popular opinion here, I think the days of Geocities and the like, with almost everyone wanting to --- and easily accomplishing --- the task of writing webpages, was when the Web was much closer to its goals. Admittedly, these "amateurs" didn't have the best design for their sites, and browsers were less featureful than they are today, but somehow the "roughness" and "wild" nature of those days felt like far more of a user-empowering Web than it is today.
Yep, I made a similar (but less eloquently stated) observation a while ago: https://news.ycombinator.com/item?id=3876834
It now seems clear to me that the only way to keep the Web/Internet free is to narrow the gap between what programmers and non-progammers can make, at least prima facie. That is the real difference between now and then: kids and novices like me could make something that prima facie resembled what the professionals were doing, whether it was hacking DOS apps or simple web pages; at least I thought I had a chance of getting near the pros.
Can you explain precisely how this will kill the web but the status quo where everyone uses Flash / Silverlight instead of the web stack does not?
Silverlight is already dead,
There was a window to kill DRM, Tim Berners-Lee should have called the MPAA bluff..
The MPAA needs the internet far more than the internet needs the MPAA and their content
EME goes far far far far beyond just allowing netflix to claim HTML5 Compatibility
when EME is in the spec, the Open Web is dead...
Slowly, slowly, we'll be reinventing web. I can't wait for 2020, when these brand new apps that structure every kind of data and make it uniformly accessible, in a form that makes it easy for automated programs to reason about both content and structure, are going to be all the rage.
I'm actually excited about it. What makes me bitter is the fact that I have no idea what the fuck we were doing wrong in the early 2000s or so, because we should have been there already.
It's easy to find scapegoats like Facebook, tightly clutching private data in poorly-designed, ever-changing access schemes that polarize the WWW, but I'm not entirely convinced they're the only ones to blame.
> I can't wait for 2020
You may as well wait till 2200 till someone finds a solution to the problem no one has.
If we are going to do something slowly of quickly it is to finally understand what web is and what it isn't.I don't think "we" were dong anything wrong. A lot of stuff now being used to accelerate web development simply wasn't mature enough, back then. Also, there are critical-mass effects that simply couldn't be done in early 2000s.
Still, a lot of people were already working on these problems on a conceptual level.
I think web development is speedy, and it also was fairly speedy in the 2000s, too. The web, on the other hand, not so much, and much of it is bloated and hampered by abstraction layers to an indecent degree. JS doesn't help, either.
Something took a wrong turn at a point and the immature, but potentially capable technologies we had degenerated into today's clusterfuck.
Sadly, because sites are so bad on mobile, mobile browsers don't do pinch-to-zoom anymore, and that messes my html-only (no css, no js, valid html5) pages utility.
I doubt the web is going anywhere. The future is going to hyperlink driven link data services that can power both native and web clients.
I have started to architect such a solution for my employer and let me tell you, it is the freaking future!