There’s no real world brokers or workers supported (at least built in), but still centralising around a standard interface might make things nicer than the celery tentacle monsters Django apps eventually tend to mutate into.
I'll walk myself out.
The question is whether you actually need such a camera for anything. With a new smartphone that has multiple lenses, out-of-the-box photos will turn out MUCH NICER than from a camera, because initial processing is built into the software. Digital cameras don't have this. You need to take RAW and work pretty hard on it to make the photo look as good as what a smartphone delivers right away.
In tourist destinations, you can often find middle-aged guys running around with huge cameras when in reality most of their photos are quite poor. Because they don't realize that with a regular phone, their pictures would be much nicer.
Fuji then has the whole film simulation system with all their colour science from the last century. It’s a ton of fun, and the jpgs it produces are distinct and beautiful, and I believe better than 99% of people could achieve from post processing the raws, myself included.
The middle-age guy part is accurate though, I got it as a thirtieth present.
Much of the technology was there, but Docker was able to achieve a critical mass, with streamlined workflows. Perhaps as much a social phenomenon as a technical one?
The effort to introduce the concepts to the mainstream can’t be understated. It seems mundane now but it took a lot of grassroots effort and marketing to hit that critical mass.
Oxlint is a alternative to eslint built on Oxc. It has suffered from not supporting the additional level of type-based linting that typescript-eslint can provide. They’ve now addressed that by patching and wrapping Microsoft’s new go-based typescript compiler.
Hopefully they are up to the task of continually keeping up to date with the go compiler’s internals, and/or Microsoft exposes a programmatic interface for the new compiler’s parser and type-checking.
I also wonder if or how plugins will be possible for this go+rust combination linter – they’re a pretty important part of the eslint ecosystem they’re trying to upend.
That said I wonder if it could ever go mainstream – JS is not a trivial language anymore. Matching all of its quirks to the point of being stable seems like a monstrous task. And then Node and all of its APIs are the gorilla in the room too. Even Deno had to acquiesce and replicate those with bugs and all, and it’s just based on V8 too.
Also fwiw there’s no such thing as an M4 Ultra chip. That detail was either a mistake or hallucinated.