> it's basically just a REST API

The opening has 1 paragraph and 5 table entries. One of them is “Not REST”

It’s a little scary that this was considered too dense or complex because the basics were explained in something that could be read in 1 minute. That still wasn’t enough to stop the top HN comment (as I write this) from calling it too dense and giving incorrect information that is immediately refuted by skimming the top part of the article.

▲

sharifhsn 3 hours ago | parent | next [-]

It is not technically REST, but it is basically REST. The alternative to a server endpoint is JSON-RPC over stdin which has the same request/response format as REST. This is exactly the point about over-complicating it by saying "it's not REST, it's not JSON-RPC". It's a JSON request/response protocol with a defined format.

	▲	jazzypants 2 hours ago \| parent \| next [-]
		REST !== JSON-RPC https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert...
	▲	tasuki an hour ago \| parent \| prev [-]
		> It is not technically REST, but it is basically REST. What does that even mean? > the same request/response format as REST What request/response format does REST have? Do you even know what HATEOAS means?

▲

wongarsu 2 hours ago | parent | prev | next [-]

The opening is fine, but when you click "Start the lessons" you get a six-pane interface that imho is pretty overwhelming

Yeah, I can click around and follow what's going on. But I'm with GP: this is not making it easier to understand. It's great at being Hollywood UX: looks pretty, stuff moving everywhere. One click on "step" makes the image animate, and change the text in the left sidebar, top middle, and right sidebar, in addition to stepping the table in the bottom middle. But it's almost the opposite of distilling information

	▲	steve_adams_86 25 minutes ago \| parent [-]
		> you get a six-pane interface that imho is pretty overwhelming Agreed, and it probably doesn't need to be overwhelming but the design choices leave the intent and purpose of the UI fairly unclear. It requires a bit of clicking around to understand what it's all for, and it's quite flat and unappealing, leaving little drive to do that work.

▲

iugtmkbdfil834 3 hours ago | parent | prev | next [-]

Sign of times man. Not that long ago -- on HN mind you -- someone posted an article that landed on main page that used lsblk as some sort of secret hacker linux command.

▲

parineum 3 hours ago | parent | prev | next [-]

That's the purpose of the comment, to make a comparison that's simpler than the article that is missing from the article.

If the article said, "It's basically just REST". There'd be no need to comment as such.

▲

sleepybrett an hour ago | parent | prev | next [-]

This is actually one of the better 'mcp explained' type 'articles' i've read.

▲

taneq 3 hours ago | parent | prev | next [-]

While we’re applauding brevity, three cheers for the first line being “model context protocol”. While yes, this one is common, it’s still nice not having to scroll through 20 screens of blah to still not find out what the thing is.

▲

flanz_10 2 hours ago | parent | prev [-]

> The opening has 1 paragraph and 5 table entries. One of them is “Not REST”

and yet...