Actually no, TCP/IP/DNS is the backbone
of the Internet and what made the Internet
possible, HTTP was invented before Roy
dropped his thesis. People like to give Roy
kudos for inventing the Internet ...
Hi strawman[1], nice to see you again. I specifically stated that Fielding, Berners-Lee, and Frystyk were responsible for defining
HTTP. A fact well documented by the aforementioned RFC-1945 reference. Since your reply was submitted by some form of
HTTP client (a.k.a. "web browser"), by definition it used said protocol or the derivative "HTTPS" protocol to do so.
This is further supported by you acknowledging the same:
... the thing that makes the web platform
powerful is modern web browsers ...
You see, these "modern web browsers" support a thing called "HTTP." And this "HTTP" thingie was defined by a handful of people (this sounds familiar).
Regarding web client performance verses native apps, you state:
Which Despite its primary focus and
decade-long head-start it's still getting
eaten by Native Mobile Apps ...
This largely can be explained by bloated JavaScript-based SPA's[2] downloading
megabytes of interpreted code. Want faster performing interaction? Don't stuff dozens of script references into a page which mandates the system to download them before being useful.
How could this be done? One is called Code-on-Demand[3]. But for this to be viable, the system must recognize the server as being a first-class concern which collaborates with its clients instead of being a glorified data base connection pool. But if a person is myopically focused on what executes solely in the browser, this might elude them.
> you'd prefer whatever Facebook tells
you is better?
No people should learn to think for
themselves and use their experience to
pick the best tool for the job ...
Here's a point we agree upon. Nice to end it on a high note.
1 - http://www.asa3.org/ASA/education/think/strawman.htm
2 - https://en.wikipedia.org/wiki/Single-page_application
3 - http://restcookbook.com/Basics/codeondemand/