Видео

Eh... I have been building APIs for over a decade now. And while I agree with the general point that almost nobody ever designs full HATEOAS APIs and maybe OpenAPI style APIs most people do have are not "really" REST, I think the border between the two is a lot more blurred. The argument in the video seems to be that "if there is no hypermedia it is not REST. Well, a lot of APIs employ hypermedia. I made a few of them myself. Consider pagination of list APIs. You get a list of bajillion results. You don't want to send them all to UI. You don't even want to generate them in the first place, since that is likely to bog things down on the backend too. You could, like a lot of people just add a URL parameter like ?page=2 or ?offset=50 or whatever to request the next page. But in a lot of cases your UI needs to know how many results are in the total. At the very least to be able to tell the user how many pages they can page through. So you add some meta data to your results. Main body is the list and meta data contains the total number of results available. This way you can also process HEAD requests that will only serve the total count without the list data. But since you already add metadata you might as well include links to the next and previous page. Why? Because it is more intuitive for the API user and you have an option of making your pagination URLs unpredictable to dissuade scrapers and crawlers from abusing it. A similar example is with embedded objects. You have an ad for some product. Your product has reviews. For obvious reasons you are not going to include review data in the same result as the product request. So your API users need to construct your review URL based on the product data. You have a special review by product endpoint. You could have a hierarchical /product/<id>/reviews/ endpoint. Both are fine approaches, but both have downsides. The easiest approach is to include a URL for the review list endpoint in the product data. And again this gives you a lot of freedom on what you want that URL to look like. There are other examples, of course, but as I said, hypermedia in APIs is far from being dead. It just doesn't look as neat and idealistic as the original HATEOS idea.

Something I started playing around with in my project was using the schema to define dynamic structure. Say I have a bunch of different item types and the documents contain different aspects that aren't static, I used the schema to define the dynamic web content. Over time, that schema can change, new item types can be added. When handling these documents, a simple read of the document structure is used rather then applying the schema to it.

For some reason I feel like starting a fire.

I detect a reference to KOHUEPT.

Seems like lots of topics aren't working anymore in 2024. Wonder how all the big brains didn't foresee this.

Amen to this. I was involved in a system where the management decided it had to be REST. It was a real-time control system. What a bad fit.

Many "simple" protocols of the earlier days were actually really simple, like SMTP. Only later, the word "simple" was misused, as you say in the case of SOAP.

Great video, Dylan!

In my 25 years of experience I've yet to meet a REST purist who was good at anything but making ppt slides.

This is magnificent. I had multiple “penny drop” moments - understanding the context of the “why?” really helps me understand.

Oh this channel is for me.

Love these trips back in time. Nice t-shirt.

I'm old enough to remember when Z39.50 was most of the Internet traffic.

"no hypermedia - no rest"? ok then, but then also if you have a stateful login, ie. the same request which gives different results based on some state on the server (eg. a login state) then you don't have REST. See paragraph 5.1.3 Stateless in Roy's paper

idea for javaScript update: !Nan = "number"; !"number" = String; String*String = "crossword"...

Wow, I had no idea this was a thing that's sick, going to try and integrate this into my workflow

you're mixing up things. authentication has nothing to do with it, but it's nice when authentication works seamlessly with REST and applications. applications and what REST API provides to them are different things. there's no need for hypermedia to be part of an API unless it's a need/nice to have for the application. REST is stateless. applications use whatever technologies to maintain authentication and state if they need it. REST separates the concerns of server and client, and typically give the client a structured way to do CRUD (create/read/update/delete) like things with objects on server, that application pulls together into a coherent application to do something. web REST APIs is another level or number of levels that people implement, which is more a reflection of their business needs rather than a reflection on core REST APIs.

this guy explains things so well im going to be hacking governments🤣

We've also essentially moved from dumb terminals in the '70s to smart terminals now, with everything essentially running as a web app or something cloud-based. The idea of actually running software on that massively powerful machine in front of you has become antiquated.

NaNNaNNaNNaNNaNNaNNaNNaNNaNNaNNaNNaNNaNNaNNaNNaN

Why do you seem to imply that REST services only provide frontend content. We have hundreds of REST APIs in our organization that are purely for communication between backend services. Hyperlinks in the response message are not needed for this. Indeed, backend services communicating via REST send JSON message bodies, not HTML.

These videod are just sooo good Please don't stop making them 🙏

What did I just watch? I looked like a pile of loose sand shifting ...

The "cat" could be a squeaky door hinge.

Great video might revive applets just to make people mad

Madness 😂

I'm sorry, but JavaScript is in no sense elegant. Elegance of a system is a measure of how well it suits the problem it's trying to solve. Elegant languages have low impedance for use. JavaScript is for sure a simple language, but it was designed in a few weeks by essentially one person. You cannot expect elegance from that.

Hahaha! Excellent! 👌

🙂

Wet Ass Tokens?

Just as Brendan Eich saw it

you can take this to an extreme and obfuscate *any javascript program* into only using the characters []()!+ i love javascript, masochistically

I hate that empty arrays are truthy in JS. They are falsey in Python and that seems reasonable.

Oh, I thought this would be about WASM-WAT (WAsm Text format).

Could it be that this notion of truthiness was pioneered in Perl? Perl 5 came in 1994, Javascript appeared in 1995 (according to Wikipedia). But, I see that Javascript could have it's own industrial-grade obfuscated programming contests 😀

Looking back I find it a bit amusing how "write once, run/debug anywhere" was the motto for Java, and Oracle used to make a big stink about how Java wasn't JavaScript, and yet it was JavaScript where that promise actually won out in the long run

Aww, my prediction was wrong. I _almost_ correctly interpreted ({}+"")[!""+!""] as indexing 2 from the string "Object Object" (forgetting the square brackets), which would've been 'j', and predicted the entire expression would evaluate to "javascript"

JavaScript is not a good language, it's a necessary and at this point pretty much irreplaceable language. The idea of just running code without needing to compile, in a way that can just be interpreted by all browsers is obviously grand. Just the design of the language itself is unfortunately pretty mediocre.

🤣 That's brilliantly ridiculous! And what I'm hearing is that this process could generate working Rockstar code?

Dunno when, but from the WAT talk, things have changed.. {}+[] and []+{} now both return '[object Object]' in NodeJS

classic jsfuck

I was like, wat? Wat is awesome? Yes.

Just a note of appreciation for "The Consolidated Cheese and Diesel Corporation" at 03:56 🤣

The late Joe Armstrong is still my #1 computer science hero because of the way he thought about problems, and his great mind for critiques, positive and otherwise.

In my personal experience, it sure helps.

the web was a mistake

This is where the "What3Words" App can come in handy. 🤔

Nice and Clear. I was part of introducing REST in an embedded product, and I must admit that we never caught the Hypermedia thing. So - I guess we got it right ;-)

Too bad certain Big Tech companies conspired to completely neuter WASM.

wat