I like Divvy because it supports more than just halves and quarters — I use a 7×6 grid so my browser can be wider than my editor and terminal: https://mizage.com/divvy/
Pairs well with Stay to make windows automatically return to their assigned layout when plugging/unplugging my external display: https://cordlessdog.com/stay/
PICS was very complicated and attenpted to cover all possible "categories" of adult content. It was confusing, incomplete and only a handful of sites voluntarily labelled their sites with it. RTA is one simple static header that any site operator could add in seconds unless they get more complicated with it by dynamically adding it to individual videos say, on Youtube which means in that case the server application would need to send that header for any video tagged as adult.
I added PICS to my forums but it was missing many categories of adult content. I ended up just selecting everything as I could not predict what people may upload which made for a very long header.
Agreed though in my example the point would be to set the header in the case the child is logged in but for whatever reason the site does not know their age. Instead of a third party site, a header is sent with the video tagged as adult that triggers parental controls if they are enabled by the device owner.
“Organizations” didn't exist until GitHub was already popular and entrenched, and it got popular and entrenched by centering the person developing the code instead of the code that was being developed: https://github.blog/news-insights/introducing-organizations/
2010 is pretty early as far as GitHub history goes. Organizations were free, what wasn’t free was private repositories (but that applied to personal accounts too).
> But maybe the most underappreciated thing GitHub did was archival work: GitHub became a library. It became an index of a huge part of the software commons because even abandoned projects remained findable.
I think this is a bad thing actually. Having something that's centralized but helpful-99%-of-the-time atrophies our collective archival skills. If everything had to be seeded by someone to keep it alive, everyone would be better at holding on to their copies of the things they really cared about instead of being able to assume they can just check it out again when they want to.
There should be no single place that something can be taken down. When a project on GitHub gets DMCAed it takes everyones' forks with it too. Just look at what happened when Nintendo took down the popular Switch emulators in 2024, where archival/continuation efforts consisted of people figuring out who had the latest revision checked out and sharing it. That was only possible because they were very popular project: https://news.ycombinator.com/item?id=40254602
Aside: I really love the Splatoon-ish header/footer animation on this site! Very unintrusive, adds a lot to the vibe, and also quickly gets out of your way as soon as you scroll down. I'm totally going to rip this off lol
> Having something that's centralized but helpful-99%-of-the-time atrophies our collective archival skills.
Also it feels like "if it's not on GitHub, it doesn't exist", which is a bad thing. Feels like too many developers don't know that code can be stored somewhere else.
Archival is easy but copyright and IP law gets in the way. If we removed obstacles to making information accessible, it would lead to less concentration of power.
I don't agree with this. Github has existed for years and one of the reasons developers trust it is that they never monetized their "archival" work yet (TBD with all the new Copilot features).
The alternative would be many sites, each one of them with their own DMCA rules.
Torrent doesn't magically find peers, even with DHT the torrent files have seed nodes baked in. A middelman required for both the centralized trackers and trackerless torrents.
DHT seed nodes are optional. A torrent node that's already connected to the DHT doesn't need them. Most torrent software has some default nodes baked in, from which it can discover the whole DHT.
> In the past few years, GitHub has absorbed both a fundamental paradigm shift (agentic coding) AND several different hockey sticks of growth. It's messy. I'm not always proud of the results or the product choices we are forced into.
Excellent example of why centralization is a bad thing. A Git “hub” is not a thing that should have ever existed for a self-described “distributed” version control system.
Decentralized networks benefit from hubs if they benefit a subset of the network, which GitHub has for a long time. A hub is a focal point and there can (and should be) many of them in the git "network."
Nothing prevents usage of GH in a decentralized fashion. There's nothing magical about git remotes. Just add some more, figure out a process that works for you, have fun!
In reality: when I want to send a letter I don't want to figure out a process from scratch. I want to go to the local post office, buy a stamp, and post a letter.
Convenience is a spectrum and different people land in different spots. What irks me is when I lack the choice. And that's not the case here.
And there's nothing wrong with it! I take detours on road trips all the time following “Historic <thing> →” signs or just because I see something interesting in the distance and want to go check it out. On a train journey I'd just have to watch them pass by.
> Not all diners look like train cars, but many do because they were fabricated to look that way, […] features a corrugated metal surface
Article would do well to mention that this particular style comes from cars manufactured by Budd Company, who developed the necessary process of welding the stainless steel, first seen on Burlington's “Zephyr”:
Pairs well with Stay to make windows automatically return to their assigned layout when plugging/unplugging my external display: https://cordlessdog.com/stay/
reply