What, JSON shouldn't have schemas because they exist for other formats? Or JSON shouldn't be used because XML is good enough?

While I agree that tech should reevaluate its sisyphean upgrade treadmill, I'm not sure how that relates here.

> Or JSON shouldn't be used because XML is good enough?

Mu. Neither JSON nor XML should be used, because S-expressions are good enough, and more attractive to boot.

It's Groundhog Day all over, and the cycles are getting shorter and shorter.

You'll love this talk by Robert C. Martin ("The Future Of Programming"): https://www.youtube.com/watch?v=ecIWPzGEbFc

I was looking for a comment that explained how json schemas are similar or not to xsd but your rant was the closest I could find amongst all the hype that this is great.

Did you have other technologies in mind or were you also thinking of xsd?

This is really the vapid comment you chose and not any of the comments that didn't immediately write off the technology but actually had a business problem to solve?

Please comment civilly and substantively or not at all.

https://news.ycombinator.com/newsguidelines.html

Alright. Just got frustrated. I've been programming since 5, but ever since I did 'proper' computer tech, it's been this back and forth game of: * thin client vs fat client * clientside / serverside * all the same document formats * layers upon layers upon layers of abstraction * static vs dynamic languages etc etc etc

my 286 was more responsive and would compile my games faster than most other things on my i7. It is plain insanity.