Hacker News new | ask | show | jobs
by interesthrow2 2741 days ago
It sucks because it's not a spec, that's all. HTTP is, GraphQL is. When implementing GraphQL either you follow the spec or it is not GraphQL. Same for HTTP. An vague idea shouldn't be the basis for architectural choices and I'm glad REST and its legacy are now criticized and contested.
2 comments

I've found it's best to let other organizations be the guinea pigs and get the kinks out, or disprove it, before our own org adopts it. Too many get carried away with "new ideas" and dive in the deep-end blindfolded. Let it run "five years in a similar organization" is my time-proven rule of thumb. Unfortunately, I lack rank to enforce this rule.
I assume your criticism applies to OO? Or functional programming? Or event sourcing? Or any number of programming concepts without a "standard"?
> I assume your criticism applies to OO? Or functional programming? Or event sourcing? Or any number of programming concepts without a "standard"?

Don't assume anything, I never talked about OO, or functional programming, or event sourcing or any number of programming concepts without a "standard". Don't make up things in an attempt to further whatever point you are trying to make here. I never talked about those things and don't care about them.