3 ms·
I was expecting some RFC's like https://www.rfc-editor.org/rfc/rfc2068 https://www.rfc-editor.org/rfc/rfc2068 or talk about RESTful concepts but they go on name
by javier_e06 3y ago
I was expecting some RFC's like https://www.rfc-editor.org/rfc/rfc2068 https://www.rfc-editor.org/rfc/rfc2068 or talk about RESTful concepts but they go on name-dropping to ...make it more interesting? In my book of knowledge web is a protocol described in an RFC. The rest of the stuff rides on top so I was expecting to see the a description of the evolution of such protocol. Netscape (danm you cookies!), PhP, Adobe Flash (Oh boy) is not the history of the bar but the history of the celebrities who frequent the joint.
- askonomm 3y agoI'm only a few articles in at the moment, but I really like it so far. Yes, it's not as technical as RFC's would be, but it's still quite enjoyable as leisurely reading.
- ptx 3y agoYeah, that's what I thought as well. It pulls together screenshots, photos, code snippets, quotes and links to historical documents. The RFCs don't have this stuff. (Maybe I shouldn't have included the "for the technically curious" part in the title when I submitted it, since it isn't focused on the most technical parts?)
- askonomm 3y agoI mean, my mom would not understand most of the stuff there, so I'd say it's technical enough, and saying "technically curious" seems an apt description to me, especially since RFC's would be for people who are much further along the rabbit hole than just "curious", imo. I may be a technical person, but I'm much more of a fan of this story-telling form of content than the hardcore manual stuff.