3 ms·

> Yeah, please don’t; this is an abomination that’s fun for demonstrating and teaching how these things work, but should absolutely never be used in reality. W

> Yeah, please don’t; this is an abomination that’s fun for demonstrating and teaching how these things work, but should absolutely never be used in reality. Would you say the same about taking a browser -- which was designed to be a document viewer for researchers -- and turning it into an entire application execution platform like we have now? Point is: It's silly to say things like this, because this is how innovation happens.

svachalek 6y ago
You know, if we could just go back and make that un-happen, we probably would have built an actual internet application platform. That probably would have been a lot better than the layers of hackery that we deal with now, but ok, that's pure speculation.
- TheKarateKid 6y ago
  Perhaps, but that doesn't mean it would be better. Look at how many over-engineered platforms/frameworks Microsoft made, and it just ended up being over-complicated or reached a point where it was no longer worth continuing.
chrismorgan 6y ago
No, please read my other comments here—the point is that this thing doesn’t solve anything, but introduces various problems. The only tenuous claim it can have is that the document is JSON, so if you want to parse the data, maybe you’ll find it easier? But in practice this is not useful: you can already embed or link to a JSON representation in the HTML, and that JSON representation then won’t be constrained by having to embed the renderer, either. Not all inventions are useful.
- TheKarateKid 6y ago
  It solves the problem of having to use multiple languages across front/back-end by using Javascript/JSON for everything. It may seem as ridiculous as using Javascript to write back-end server-side and desktop software, yet along came Node and industry hype and here we are today doing exactly that.
  - chrismorgan 6y ago
    As I’ve said, I have no objection to using this sort of JSON as an input format, but I do object to deploying in this format.

svachalek 6y ago

You know, if we could just go back and make that un-happen, we probably would have built an actual internet application platform. That probably would have been a lot better than the layers of hackery that we deal with now, but ok, that's pure speculation.

TheKarateKid 6y ago
Perhaps, but that doesn't mean it would be better. Look at how many over-engineered platforms/frameworks Microsoft made, and it just ended up being over-complicated or reached a point where it was no longer worth continuing.

chrismorgan 6y ago

No, please read my other comments here—the point is that this thing doesn’t solve anything, but introduces various problems. The only tenuous claim it can have is that the document is JSON, so if you want to parse the data, maybe you’ll find it easier? But in practice this is not useful: you can already embed or link to a JSON representation in the HTML, and that JSON representation then won’t be constrained by having to embed the renderer, either. Not all inventions are useful.

TheKarateKid 6y ago
It solves the problem of having to use multiple languages across front/back-end by using Javascript/JSON for everything. It may seem as ridiculous as using Javascript to write back-end server-side and desktop software, yet along came Node and industry hype and here we are today doing exactly that.
- chrismorgan 6y ago
  As I’ve said, I have no objection to using this sort of JSON as an input format, but I do object to deploying in this format.