A website for debloated open source alternatives
debloat.dev
debloat.dev
All the /p/ URLs are in the sitemap, all the site's pages can be retrieved over a single TCP connection
https://debloat.dev/sitemap.xml
This, i.e., retrieving all 200 /p/ URLs over a single TCP connection (using HTTP/1.1 pipelining), results in a 1.9MB HTML file comprising all the /p/ pages, including response headers. NB. This isn't "crawling". All URLs (cf. a set of "seed" URLs) are known before the connection is made
No cookies, no Javascript
Other than CSS, no bloat
NB. A 1.9MB sitemap would not be large. For example, here is a 2.9MB sitemap from AP
Would a "1990's style" website offer a sitemap.xml file
Also, this site, like most today, uses "slugs" for its URLs. In the 1990's this was less common; URLs were often "uncool":
https://www.w3.org/Provider/Style/URI.html
NB. I'm not commenting on the website's content or how it was generated/sourced
Wrapping modules to expose additional functionality for a niche in a problem domain is tricky. You will end up with some code duplication and some predictability issues with your timelines, but the end result will be better for it.
Long ago someone convinced me that 'Strangling a Service' could also be applied to APIs. The base module should be as simple as possible but no simpler, and more esoteric features should be shunted off to another module. And then in the case when features are antagonistic to each other, they can live in parallel in separate wrappers.
The tricky part there is writing unit tests in the base to defend the negative space that these features fit into. This feature depends on an invariant in the base API that will break everything if merged.
This is the inherent problem with tech start-ups. Once they solve the problem they were founded to solve, then what? It's feature complete, but investors insist that the line must go up. Can you imagine if `sed` or `vim` was brought to market by a venture-backed company?
IMHO, capitalism and FOSS are fundamentally incompatible.
A bold statement to make given the world we live in today contains plenty of both, working together, in harmony.
Really lightweight and nice!
You can see some collection, and I'm building some advanced research capabilities to it.
For now, you can see if you can fully replace an app with a sub, with oss alternatives, or free alternatives.
Heavily vibe coded but all the apps out there didn't have what I needed, a list of features, what exactly is missing, if there is an sso tax or not, licenses, cheaper alternatives, if there are some tjat genuinely can't be replaced and why.
Lemme know what you think about it and what I should add to it
That would be a good feature here.
There's also an implicit judgment in your question. Is well-designed, well-tested AI-generated code worse than poorly written, but hand-typed code?
You're asking an extremely reasonable question, IMHO, especially given these are projects with limited resources going up against generally larger, better-resourced projects. AI is an obvious point of leverage in such a situation, and so there is a lot of potential to reverse engineer using AI and get good results.
What all of these requests fundamentally come down to is "How are you filtering for quality?", which is an extremely difficult question given the state of, for example, the app stores.
Heh. I was essentially run out of lobsters for repeatedly asking that question. Not even kidding. At some point I became the second most flagged user in the entire forum. The site itself invited me to delete my account.
After a while I simply asked Claude to define "slop" and posted the answer. To this day it's still the only coherent definition of "slop" in the entire site.
AI involvement is a possible heuristic but I seriously doubt it's all that useful for software (probably works a lot better for books)