4 ms·
> It is not hard to imagine your Web-enabled microwave oven consulting the frozen-food manufacturer's Web site for optimal cooking parameters. This is Berners-
by patrec 7y ago
> It is not hard to imagine your Web-enabled microwave oven consulting the frozen-food manufacturer's Web site for optimal cooking parameters.
This is Berners-Lee being visionary about the potential of a world-wide network of computers. The problem is not just the terrible technical implementation, it's also that the vision behind all this semantic web stuff was one of soulless dorks who saw the world's population spend their days semantically marking up All The Things to get the most of their web-enabled microwaves.
Everything I have seen Berners-Lee prominently involved in sucks at every level from micro to macro. Take urls: url query strings separators conflict with html escaping, the port syntax conflicts with the IPv6 syntax (which came first) and finally urls are not even self delimiting, so Tim hatched the aesthetically compelling workaround to write them as <URL:http://example.com> http://example.com>.
- mehh 7y ago>It is not hard to imagine your Web-enabled microwave oven consulting the frozen-food manufacturer's Web site for optimal cooking parameters. >This is Berners-Lee being visionary about the potential of a world-wide network of computers. That sounds very much like the sort of stuff that gets spouted by the IoT crowd too though isn't it? >The problem is not just the terrible technical implementation, it's also that the vision behind all this semantic web stuff was one of soulless dorks who saw the world's population spend their days semantically marking up All The Things to get the most of their web-enabled microwaves. Well, aren't there a huge mass of developers spending their lives writing custom code for every damn API, and then integrating with more custom code. And each time eventing new poor ways of describing the things and relationships?