Yet another talk on the controversy of REST. The creator said: "HATEOAS is a must", almost nobody uses it, and yet call the result "RESTful". The true REST (including HATEOAS) powers the WWW itself, where the client (a browser) has no domain knowledge on the content. This is not true for most of the applications ever built - don't create a generic engine unless absolutely necessary, don't waste your time.
Try to implement this, then you'll change your mind. Too expensive and near-zero benefits. HATEOAS powers the WWW itself, but has very rare use cases when the client has no domain knowledge.
@@user-iv9ki7lv1f Depends on what you consider take off. I've seen it applied in pretty big customer projects. Some AWS APIs even use it. Not seeing much usage in public APIs is a bad indicator of whether something is used or not. Otherwise you'd have to claim that literally nobody would have ever used SOAP in the first place, which - unfortunately - is not true at all, right? 😉
Meh. I don't want to deal with all of that. I just need what I need from the server. I don't want a list of crap that my client now needs to interpret, unless of course a list of crap is specifically what I'm asking for. I don't think it's too much trouble to ask a front end dev to spend 10 minutes to understand the API he wants to program around.
Yet another talk on the controversy of REST. The creator said: "HATEOAS is a must", almost nobody uses it, and yet call the result "RESTful". The true REST (including HATEOAS) powers the WWW itself, where the client (a browser) has no domain knowledge on the content. This is not true for most of the applications ever built - don't create a generic engine unless absolutely necessary, don't waste your time.
I like the capital font used in the presentation - anybody recognize it?
Thats Freight Sans Pro: fonts.adobe.com/fonts/freight-sans
Why do presenter dont understand that without concrete example its all extremely vague for us developer to understand ?
I think that's fantastic. Not soo familiar with REST APIs, so is it actually new or just a good and well known practice?
HATEOAS (en.wikipedia.org/wiki/HATEOAS) has been a thing for a long time but it never took off.
Try to implement this, then you'll change your mind. Too expensive and near-zero benefits. HATEOAS powers the WWW itself, but has very rare use cases when the client has no domain knowledge.
@@user-iv9ki7lv1f Depends on what you consider take off. I've seen it applied in pretty big customer projects. Some AWS APIs even use it. Not seeing much usage in public APIs is a bad indicator of whether something is used or not. Otherwise you'd have to claim that literally nobody would have ever used SOAP in the first place, which - unfortunately - is not true at all, right? 😉
Meh. I don't want to deal with all of that. I just need what I need from the server. I don't want a list of crap that my client now needs to interpret, unless of course a list of crap is specifically what I'm asking for. I don't think it's too much trouble to ask a front end dev to spend 10 minutes to understand the API he wants to program around.
Yep, and you spend less time overall (including fixing bugs) than adding support for HATEOAS.
...kinda looks like e-sports star Northern there..
Watched 23 min. of this, wasted 23 min. of my time ... everything is very meta ...
You saved me time! lost interest in the first 10 minutes and then saw your comment.