Earlier quoted context omitted.
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. Your fixation of the HTTP protocol was invented by Ti…
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 o…
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.