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.
This is all common sense, why is this being posted here? Probably enlightening to our moronic moderators though.
Pre-Internet: < 1995, THE WEB, post-Internet: > 1995
"Tubes"
The technology is fine. It's our so-called civilization that's broken, and it's brokenness is what breaks the Internet. Between some nations and their draconic censorship, ISPs mucking about with the flow of information, and criminals using it as a vehicle to attack it and it's users, I'm surprised it works as well as it does. As usual a good thing has been ruined by getting too many PEOPLE involved with it.
"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
The real takeaway here is that AMP, and everything similar to it, need to die in a fire.
Don't use AMP, don't let your clients use AMP, don't click on any AMP links. AMP is cancer.
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)
That link to a goat sea. You know the link.
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.
walled gardgens cannot be part of the beb by this definition.
It's a good definition precisely for that reason. These unlinkable pages break the web
Some drink at the fountain of knowledge. Others just gargle.
1) Define "linkable".
2) Define "client".
Do so in a way that is unambiguous, but also is unlikely to change over time. Good luck.
Now that HTML5 is finally finished, what the web is is defined very clearly by the W3C standards. Sure, you can replace those with your own proprietary tech, but then don't call it 'web'.
My friend Ghostery tells me this page has 31 different trackers loaded on it. 31 pieces of useless information to be sold by one group of con/ad men to another. And it is the dependence on selling demographic information and the insta-bidding of ad space that keeps clogging the tubes and prompts well meaning but deluded engineers to create solutions like AMP.
Give me back Web 1.0 and HTML 1.1 where content where you were judged on your content, not how well your page looks on a phone.
Average Intelligence is a Scary Thing
(3) And must include 300k of Javascript libraries.
Google Apps are being discontinued except for Chrome OS.
https://www.theverge.com/2016/...
Not only that, they're slated for second-half of 2017... so like in a couple of months. Goodbye Netflix app. I hope they've resolved the "no 1080p/4K in Chrome except in the app" issue.
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.
I knew I wasn't wasting my life writing the ultimate Gopher client over the past 20 years! CHECKMATE, Web!
I'm given to understand that there are even ports other than 80 and 443. Gasp! You could even write a client that does something crazy, like use port 110 for a dedicated email client. Heresy!
For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
Online hypertext. That is all.