3 ms·
Thanks but I don't need a misguided history lesson skewed to support your warped view of events attributing the creation of the Web to your lord and savio
by AdieuToLogic 11y ago
Thanks but I don't need a misguided history
lesson skewed to support your warped view of
events attributing the creation of the Web to
your lord and savior who you wish was sole
entity responsible for the Internet but was
instead created by the geniuses who built the
ARPANET in 1969 which is what formed the
technical foundation and what made the
Internet possible.
I have no idea where your anger, vitriol, and venom originate. I humbly suggest you find someone professionally qualified to help you work through these issues. Perhaps you are experiencing a persecutory delusion[1], though I freely state I am not a clinical psychiatrist and only present this as a possibility from someone who has never met you personally.
Your fixation of the HTTP protocol was
invented by Tim Berners-Lee, on-his-own.
The first version created in 1991 supported
the most important GET Request method
(http://www.w3.org/Protocols/HTTP/AsImplemented.html).
Of course Tim Berners-Lee has been and remains a major force in defining the HTTP protocol and "the Web" as we know it. This is well documented and an indisputable fact. However, as great as his contributions have been and continue to be, he has not operated alone.
What you fail to mention in the statement you quote is:
This is a subset of the full HTTP protocol,
and is known as HTTP 0.9.
(http://www.w3.org/Protocols/HTTP/AsImplemented.html)
The HTTP protocol has not stood still and has had contributors throughout the last 24 years. If you cannot accept this, that is your issue to deal with and not mine.
If you had even read Section 1.1 of RFC-1945, you could have saved yourself the embarrassment of saying "The first version created in 1991", as the RFC reads thusly:
HTTP has been in use by the World-Wide Web
global information initiative since 1990.
Remember that one of the authors of this RFC is Mr. Tim Berners-Lee.
You then go on to spew:
The fact you glorify a simple text
protocol as the magical thing that makes
the web possible is indicative of the
extent of your religious delusion to a
single technology.
Well, if you cannot accept my explanation of the importance of HTTP, perhaps you can fathom what Mr. Berners-Lee wrote instead:
Did you invent the Internet?
No, no, no!
...
I just had to take the hypertext idea and
connect it to the TCP and DNS ideas and
-- ta-da! -- the World Wide Web.[2]
Can you accept/understand that the primary contributor to what you colloquially describe as what "makes the web possible" is, in fact, stating that the web was made by combining hypertext with previously established technologies? See also previous mention of persecutory delusion[1].
Go ahead and try make versions of Gmail,
Facebook, Google Maps, Google Docs / Office,
etc with dumb clients and full page
reloads on every request ...
The fact that you conflate a REST architecture with "full page reloads" only shows your ignorance. There is nothing precluding an XMLHttpRequest sent from a browser client to a REST endpoint. Actually, it is quite common and the REST server wouldn't know/care if it were done anyway.
Any fool can create simple a text protocol,
any fool can create a dumb, server-driven
client, any fool can document a
code-on-demand solution.
No, any fool can trivialize the accomplishments of those before them. Any fool can benefit from infrastructure which allows them to be oblivious to how the bytes sent around the world "just work." Any fool can lament about performance on a resource constrained platform, such as a mobile device, and reject possibilities to address them.
That isn't to say HTTP isn't a well-thought
out and defined work, it is ...
That must have seriously hurt you to type.
1 - http://psychcentral.com/encyclopedia/2008/persecutory-delusion/ http://psychcentral.com/encyclopedia/2008/persecutory-delusi...
2 - http://www.w3.org/People/Berners-Lee/Kids.html#invent http://www.w3.org/People/Berners-Lee/Kids.html#invent
- deleted 11y ago[deleted]
- devtique 11y agoSave your humble condescending suggestions, its a side-effect of having to constantly deal with mindless blinkered zealots who can only think with REST blinkers on and are immediately dismissive of any technology that supersedes it with endless ramblings of what is/isn't REST and anything that isn't is automatically Evil, which is worse than a waste of text since it wastes other peoples times who could otherwise be spent delivering value. So take note your REST crusades aren't victim-less, there are others who just want to deliver the best experience with all tools at their disposal and your mindless preaching is viewed as an obstacle to progress. I have no trouble accepting the truth, I take issue with your thinly veiled attempts to thwart it in your attempts to glorify the author of your precious REST as the founding father of the Internet, which he is far from responsible. Even if he didn't contribute anything we'd still have the Internet and the WWW. It's very well-known he helped create HTTP, but HTTP existed before his contributions and continues to evolve without them. You're trying to downplay decades of accomplishments of brilliant minds that went into creating the Internet and the decades of programmer-effort who created technologies that goes into creating modern browsers whom are responsible for forming the web experiences as we know it today - just so you can glorify the author of your movement to aid in your preaching as a weapon to combat anything that's not REST. The fact is Tim Berners-Lee did create the first version of a text protocol known as HTTP on-his-own (a fact you can't bring yourself to admit), and like all technology he didn't do it in a vacuum, his ideas are shaped from ideas and technologies before him. Which is how all technology should progress, constant improvements by brilliant minds over time, with the best ideas succeeding. What blocks progress is religious technologies like REST, which itself isn't what's bad, it's the side-effect of breeding mindless souls who constantly seek to block anything which falls out its puristic view which they treat as Gospel. Which moves the focus from the end-user experience to how can we accomplish this into the most REST-ful way possible. > The fact that you conflate a REST architecture with "full page reloads" only shows your ignorance. Actually its your biased ignorance that I'm replying to, you think the reason that Native Mobile Apps is eating websites is because of SPA's that have "megabytes of interpreted code" - something you are desperate to believe in but which couldn't be further from the truth, those SPA's are what's keeping the Web competitive with Native Mobile Apps. Where are all the superior HATEOS mobile apps? It's been more than a decade of failed attempts which have yet to produce anything that holds a candle to a quality Native Mobile or Desktop App, who still can't figure out how to shoe-horn offline usage into their server-driven turn-by-turn apps.