Hacker News Reader

Comment by philosopher1234 | Hacker News Reader

I think this is an insufficient argument. There are lots of examples where standardization works and is effective, eg HTML, HTTP, SSL, FTP, CSS ...

The argument you posed is against standardization in general, but if the conclusion is “all standardization/regulation is bad” that holds no empirical water. You have to make the case that this specific standardization is bad, since standardization as a concept is not in question.

View on HN

Think of the dead and dying standards that competed against those listed above in the marketplace of ideas (SOAP, Gopher, ECMAScript 1.4[1]).

[1] https://en.wikipedia.org/wiki/ECMAScript#4th_Edition_(abando...

I regret to inform you that SOAP's death has been limited to open source. Enterprise continues to eat it up.

You can even do much more complex things using SOAP, but Rest is much easier to learn and use, so a junior programmer can pick it up in days or hours.

People dislike having to make efforts.

In my experience, SOAP has poor tooling compared to REST and nobody implements it properly. Given that, it's not really more powerful than REST in practice.

Are you talking RPC or true REST?

Don't understand what I ask - look here http://greglturnquist.com/2016/05/03/rest-soap-corba-e-got/

Not more powerful. More standarized. Wss for example.

Well none the less, the standard doesn't help if nobody follows it. Since REST is less prescriptive, the tooling is generally more tolerant of all the funny implementations out there. At least, that's what I've found.

> I regret to inform you that SOAP's death has been limited to open source. Enterprise continues to eat it up.

How apropos. A behind-the-times punishment for being so behind-the-times? [1]

[1] https://en.wikipedia.org/wiki/Washing_out_the_mouth_with_soa...

Reply on news.ycombinator.com