This was my first thought when reading the title. I've spent the last month using chawan browser, which has a Gemini layer. And it's generally just a lot of fun to mix old web 1.0 layers with a new one.
There are also the other "small web" protocols (and some other stuff). Either way, it is still the same internet and not a new one, and still uses TCP/IP and DNS (although not HTTP/HTML). (That does not mean that it is not worth anything, though.)
Yes and it is cell phone friendly. I moved my site to gemini a couple of years ago. Maintenance is trivial compared to the WEB.
There is also gopher and USENET, but on cells it can be hard.
But the largest issue is the users attraction to "bright and shiny". I think no matter what comes I fear it will end up on the same path as now. Gemini has the ability to avoid enshitification, but it is still not attracting users like www.
Anyway alternatives exist but they need some TLC and a method to keep out commercial entities.
Gopher and Gemini can both work on many kind of devices; having a monochrome display, or the differences in input (e.g. having numbered lines works OK, especially since both require links to be on a line by itself, unlike HTML), etc, without the author of the document needing to worry about such things like that. In both cases text entry might sometimes be needed so is not ideal but still it is possible.
What is "TLC" meaning here? Furthermore, for the purpose of keeping out commercial entities, it would be necessary to have the details of what is intended to be avoided and in what contexts, as well as how to avoid certain things; I think simply "keeping out commercial entities" won't do (except perhaps for such things like e.g. indexing services, which can choose not to link to them).
There is like 1,713 open PR's on the Bun repo. I'm assuming all are from Claude or robobun?. I guess this gives us an insight on what the claude-code workflow look likes. Crazy times.
> Most are created autonomously by @robobun, checked for duplicates with a GitHub action (powered by Claude), reviewed by @coderabbitai and @claude. Meanwhile the CI is broken and @robobun finally closes a portion of its own PRs because they duplicate other PRs it has written. (Merging into main is still done by a human.)
Not a hoax, saw it in the news. I'm not at Amazon but can confirm massive productivity gains. The issue is reviewing code. With output similar to a firehose of PR's we need to be more careful and mindful with PR's. Don't vibe code a massive PR and slap it on your coworkers and expect a review. The same PR etiquette exist today as it did years ago.
reply