Slashdot Mirror
And Now, a Brief Definition of the Web (theverge.com)
Dieter Bohn, writing for The Verge: Traditionally, we think of the web as a combination of a set of specific technologies paired with some core philosophical principles. The problem -- the reason this question even matters -- is that there are a lot of potential replacements for the parts of the web that fix what's broken with technology, while undermining the principles that ought to go with it. [...] A lot of tech companies are flailing around looking for ways to fix this problem. There are web apps that work in Chrome but not really all that well elsewhere. There are Instant Articles in Facebook and AMP pages on Google. There are Instant Android apps that stream to your phone over the internet instead of being installed, which go away when you're done with them just like a browser tab. Google claims to be trying to bring some of the open ethos of the web to smart speakers. Hell, go back to 2014 and you'll find Apple pundit John Gruber arguing we should consider apps and "anything transmitted using HTTP and HTTPS" as part of the web. [...] And now, a brief definition of the web: To count as being part of the web, your app or page must: 1. Be linkable, and 2. Allow any client to access it. That's it.
"Tubes"
"There are web apps that work in Chrome but not really all that well elsewhere."
10-15 years ago, there were "web apps" that worked in Internet Explorer but not really at all well elsewhere.
Google decided, a couple years ago, to basically go that same route... and probably for the same reasons. It's all about lock-in.
#DeleteChrome
I found less and less stuff to be truly linkable. Some of it is almost linkable, but more often than not I try to bookmark that shit only to click it later and get to some generic page which asks me to manually go through some hoops to get to the specific item I bookmarked in the first place.
Direct downloads of software installation kits is a prime example.
...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
To be part of the web, your app or page must:
1. Collect as much of the user's data as possible. Bonus if you can get their entire social contact graph, page visits from outside your domain, and all their search history.
2. Work as poorly as possible if the user attempts to push back against your data harvesting by disabling javascript. Bonus points if you can disable the clipboard and "save as".
3. Load 10X slower than it should due to making connections to two dozen advertising domains.
4. Attempt to hijack and/or completely break the back button.
5. Scrunch all the text up in a 5cm wide band in the middle of an 80cm wide monitor, no matter how the user might attempt to resize the window.
6. Smear content that would easily fit in a single page over 20 pages separated by "next" buttons so you can harvest as many ad impressions as possible.
7. Attempt to get the user to store all of their data remotely in "the cloud", because you can't easily run big data analytics on it if the user gets to store it on their computer. See also, Gmail.
8. Partner with national intelligence agencies.
9. Enforce political based censorship on everyone. Saying $THING is illegal in country $C? Take it down for the whole world.
10. Load 500KB of random scripts merely to display what could be done with 5KB of plain old HTML.
11. Make sure standard HTML hyperlinks don't work unless the user enables scripting.
12. Attempt to use the hardest to read color combinations.
THAT is how you become part of the modern web.
>> HTTP and HTTPS" as part of the web
That's awfully protocol-ist. (Good thing I'm not an ITJW.) Aside from the original web (which included things like FTP), Apple might be interested to learn that there are content-optimized protocols like QUIC out there.
1) Define "linkable".
2) Define "client".
Do so in a way that is unambiguous, but also is unlikely to change over time. Good luck.
No it isn't -- HTML is crap
No, it isn't. It's a fine markup language. When it becomes crap is when page designers think it is a publishing language and think that their view of how their HTML should be rendered is the only way their HTML should be rendered.
and is the THIRD time the web has been re-invented.
I'm pretty sure that HTML was there at the beginning. I remember writing web pages for the CERN server in HTML. HTML5 is perhaps the fifth redesign, trying to turn a good markup language into something it wasn't meant to be.
Here's a demonstration of how HTML is not understood at all: the CBS television program "Scorpion" uses the string "</scorpion>", which everyone who knows better understands is the END of a section of type "Scorpion". But they use it at the beginning of the show, and at every commercial break. Is the show over before it starts? It seems not; the comedy continues for the full hour.
To be more precise, the web is just another application, and your web browser transmits and receives data from the web server over the internet, using the internet protocol suite. The word "web" refers to content linking to other content, an allegory to a spiderweb. The word "internet" is short for "internetwork" and literally means multiple networks communicating with one another (as opposed to two devices communicating on one network.)
The web works without the internet, and the internet works without the web.