Real answers: gitlab has awesome integrated CI, and you can always go for a remote integration if you prefer (e.g. self-hosted Jenkins, or a managed solution like circleci).

Yeah, I was initially pretty interested because a player like Apple can really push the envelope and drive innovation. I am still wistfully hoping for a portable office AR setup one day.

Live events (like sports) would be cool, but I’m not sure Apple wants to play licensing/marketing matchmaker at the scale required for that to be profitable. From what I’ve heard, it’s the worst part of being in the streaming industry.

Causing annoyance is one of the more polite ways of expressing your dissatisfaction with the status quo.

No true leftist would post this

Space exploration is weight lifting for science.

Does it support unit dependencies? That’s pretty much the only reason I use systemd outside of work. Edit: ah yeah it sure does. I know what I’m playing with next weekend.

Where is “nothing is real, but good luck making use of that information”?

Yep, you and I are operating in orthogonal spaces. I genuinely envy you.

Haha, yeah I use it as well, and like I said it makes drafting the code a lot faster, but it dramatically slows down review and validation of fit for the business purpose.

If I could, I’d put the genie back in the bottle because having ICs dump thousand line MRs on each other and then finding out in gamma that it didn’t actually solve the problem is a ton worse than making a person actually think about what they’re gonna commit for a couple hours. But alas, if we don’t take a first draft with Claude or Gemini agentic tools for every ticket we’ll get PIP’d, so I guess the AI enthusiasts and their sponsors are happy.

I think that newer models of Claude are a lot better, but they are still just chatbots and they still just generate words. As anyone in the industry will tell you: typing out the code was never the slow part.

This might seem like a very indirect response, and that’s because it is largely a notion I have after a couple years of observing the fediverse. My background is in infrastructure for micro services, which is a powerful source of bias, so take this with a grain of salt.

The fediverse is suffering from major problems caused by homogeneity, data duplication, and lack of meaningful coordination. It is completely unsurprising that it struggles to provide the level of service that most users expect. I’m not saying this to be mean, but because I’ve experienced these same growing pains in commercial settings.

The solution has always been to restructure product services in a way that separates concerns. Most of the big guys will, at a very high level, use an API gateway which handles security + authn, then forward requests to high level product services which in turn reach down to the data layer services (which are often ORMs with huge caches sitting on top of databases). Works great, usually.

The fediverse, from what I’ve seen, does not do this. Everyone sets up largely identical monolithic applications which share messages through the Pubsub protocol. Information is duplicated everywhere, and inter-instance communications are a liability not only in content but even in compute and persistence (you can absolutely get DDOS’d by a noisy neighbor). Individual instances are responsible for their own edge security, compute, and data. It’s just a lot to ask of a single person that wants to host a federated instance.

I think that a healthy federated internet will eventually require highly specialized instances at several layers, and for certain maintainers to thanklessly support the public facing services. One of the most obvious classes of these specialized instances, to me, would be the data layer and catching instances, which exist to ensure that content posted on one instance is backed up and served for other instances. It reduces the strain on public facing instances because they no longer have to host all the content they’ve ever seen, and it also ensures that if a public instance goes down, the content does not disappear with it.

This same principle could be used on “gateway” or “bastion” instances which enforce strict security on behalf of public instances. Public instances would block direct connections while treating requests from the gateway nodes as highly privileged. Each public instance would either find a gateway instance to protect it or handle its own security and inter-instance communications.

This obviously isn’t a complete solution, and it’s a hell of a long way from a technical specification, but my hope is that others who are looking at the weird and wonderful landscape of our new internet are having similar concerns and reaching similar conclusions.