Gemini to not be evolved:
* HTTP is now for interactivity, complex clients, WebGL, Webassembly, ...
* Gemini is for a segregated simpler web: links and text.
I've read Drew's stuff for a while and even wanted to test out Gemini out of interest, but it is really annoying/frustrating to use in my experience. And that is even before you get to the fact that there is nearly nothing there and/or it is nearly impossible. to find.
I understand the designer's reasons to dislike online advertising but the train of logic here seems to be "internet businesses like to make things that are convenient, so let's make something which is intentionally not convenient at all" which in my opinion is a really convoluted and nonsensical way to reach the intended goal. This one is a swing and a miss for me. I hope the designer keeps trying and comes up with something that is actually useful eventually.
I love it.
Honestly, just the lacking of inline links makes this stuff more annoying than anything.
Advertising did a really similar job.
It completely destroyed most web businesses trying to get their customers to "actually pay" in some form or another, and ... basically the only survivors have been a few giant media conglomerates (with their own ad divisions), and the FAANG companies (actually selling the ads). Everybody else is sharecropping on google/facebook's proverbial plantation, and like all similar historical situations of rentiership, the vast, vast majority of them have gone out of business and been acquired by the proverbial landlord (this is why, you know, something like 2/3 of the newspapers in the USA have gone out of business in the last few decades). What's even worse with the newspapers is that in many cases they weren't even acquired; they were just shuttered completely.
(The only other major survivor has been people selling actual physical products over the web.)
--
There are thousands of articles about why local journalism going out of business (and not getting replaced by anything, typically) is bad, and I'll leave googling those as an exercise for the reader.
People here won't like this, but the only realistic alternative to the advertising model where the vendor subsidizes the content, is a DRM model where the user pays to unlock the content.
I expect the designers foresaw this.
I don't think wide popularity was a goal.
This is the only reason it has any attention. People who understand it like it because others are excluded
It's trivial to serve your site as .txt files if you want. This is the digital equivalent of sticking a "no girls allowed" sign on your treehouse
It's exactly how the web evolved. It did not have activex/java applets/flash/javascript at the beginning.
Nope. And he has links to his blogs about what he doesn't like.
--- start quote ---
I used wget to download all 1,217 of the W3C specifications which have been published at the time of writing, of which web browsers need to implement a substantial subset in order to provide a modern web experience. I ran a word count on all of these specifications. How complex would you guess the web is?
The total word count of the W3C specification catalogue is 114 million words at the time of writing. If you added the combined word counts of the C11, C++17, UEFI, USB 3.2, and POSIX specifications, all 8,754 published RFCs, and the combined word counts of everything on Wikipedia’s list of longest novels, you would be 12 million words short of the W3C specifications.
I conclude that it is impossible to build a new web browser. The complexity of the web is obscene. The creation of a new web browser would be comparable in effort to the Apollo program or the Manhattan project.
It is impossible to:
- Implement the web correctly
- Implement the web securely
- Implement the web at all
Starting a bespoke browser engine with the intention of competing with Google or Mozilla is a fool’s errand.
--- end quote ---
https://drewdevault.com/2020/03/18/Reckless-limitless-scope....
You could fairly easily make your own web browser that uses HTTP and only reads (gem)text files and ignore the rest of the web.
Or just use Lynx.
Pushing your own standard seems to only add to the complexity of it all. Now if you want to make browser that can read all the text pages, you have implement HTTPS and Gemini.
Ah yes. Just the content. Including things like WebUSB, WebHID, and a bunch of others.
> You could fairly easily make your own web browser that uses HTTP and only reads (gem)text files and ignore the rest of the web.
Yes, you probably could. And it wouldn't work with most of the web.
I'm not. It's you, who keep saying that the author's gripe is with HTML, content, HTTP and what not. It's not.
Text over HTTP:
- Easy to write browsers
- Viewable by those browsers
- Can use other browsers
- Viewable by everyone else
- Can only see some other websites
Text over Gemini: - Easy to write browsers
- Viewable by those browsers
- Cannot use other browsers
- Not viewable by everyone else
- Cannot see any other websites
What's the advantage of Gemini again?