bhldr

It's a pretty great format for rapid prototyping, but very complex and wouldn't deploy it as a public API that needs to be supported for a long time.

Robust as the old protocols? The early TCP protocols are very much underspecified. Maybe you have something else in mind.

Yea this is absolutely what I meant. HTML5's complexity is a symptom of this problem.

I'm a bit worried about the authors taking this overboard and trying to redefine the URL standard with similar complexity.

It's easy to be strict if you are both a producer and a consumer.

This is also widely considered a bad idea now. Making liberal consumers allows for sloppy producers. Over time this requires new consumers to conform to these sloppy producers to maintain compatibility.

Just look at the clusterfuck that HTML5 has become. You need to have extremely deep pockets to enter that market.

Say hypothetically if a got my Drupal site for cheap and now I'm hacked. I pay someone another $100 to install the patch and get rid of the malware, I still come out ahead.

What's my incentive to do things differently?

I also think that's a mischaracterisation. It's statistically unlikely for me to transform the world. I just want to carve out a tiny piece of it and make it better.

I don't disagree with you, but this one in particular seems very far from the definition even if you ignore all the hypermedia stuff.

This is a bit far from what most would consider REST. Just call it a HTTP api?

Looks cool though! I would love a product that behaves like a proxy/CDN for images and does some on-demand resizing/filtering.

Thank you, we'll definitely get some legal advice!

Can we get the word 'american' inserted in the title. It's a very local problem.

Most SPA's don't, because most frameworks have some built-in functionality for this.

A quick search in the dictionary reveals 'yes'.