yeah tbqh I think the biggest challenge with tooling on that front is that this really is a problem mostly limited to community projects. The problems jazzband need to solve don't exist nearly as much in a universe where everyone is in a company on some payroll

In most corporate environments while it might make sense to do N of M in the high security case it's not really a thing that people will jump for for the first... uhhh 10k employees of a company's lifetime.

That requires a lot of infra that isn’t built into _any_ of our tooling.

It’s not so much about decision making as it is about the practical reality that people at that level basically need at least read access to a lot of secrets.

You could say “maybe jazzband can infra its way out of those problems” but that’s a looooot of work! “N out of M consensus on making a GitHub API request to set who is a maintainer” * every single action roadies need to do

It’s not just about bad actors either. Imagine a jazzband roadie getting credentials stolen via some npm-y attack. Obviously this problem exists in the project in the current form but _that problem gets worse just onboarding people_

The level of trust required is immense. We’re talking about a position where you get the keys to the kingdom to a very large number of projects

I would say that having roadie level access is equivalent to having access to Django core. I have never seen a recent Django project that isn’t pulling something from jazzband

Despite this I think it’s important to highlight that even in that world jazzband had a lot of infra so that projects could do things like releases cleanly and safely (we aren’t doing direct project releases to pypi but going through jazzband infra to do the release). So release maintainers have a lot less access despite releases “coming from” Jazzband

This stuff stands on the foundations it's built off of. It's very hard to argue against the stoic determinism of an `ls` call.

And all the success stories I've seen in people using these tools have had a similar theme: top level might be LLM-y but you rush to get to deterministic straightforward building blocks so that you can have reliability.

That, to me, looks like writing up a bunch of small programs to help establish vocabularies and workflows to avoid just churning and getting lost in the weeds.

I'd be interested in seeing some future form of process orientation, but in the meantime.... shells in general have proven they are decently good at tying stuff together quite well.

`ls dir | grep thingy | process` gonna involve less possibility of annoying drift and churn than "run process on all the files with thingy in their name in directory"

Well the Macbook Air pricing in USD was always around $1000 right?

2013 MBA pricing in USD was $1100

2013 MBA pricing in JPY was 110k JPY

2026 Macbook Neo pricing in JPY is ~100k JPY

2026 Macbook Neo pricing in USD is $600

2026 Macbook Air pricing in JPY is ~140k JPY

2026 Macbook Air pricing in USD is ..~$1100

So depending on the currency either the Neo is a massively cheaper thing or filling a gap in a product line that inflation created.

I wonder how much of Apple's costs are USD-denominated. The fact that the MBA hasn't changed pricing at all makes me guess that not that much, but I don't know how manufacturing contracts work

I dunno, I find it interesting, but JPY inflation is a recent phenomenon