While purely speculation, I believe the same thing would have happened, albeit even sooner, under a Harris administration. Government intervention was inevitable and it will have to be worked out through the law.
The centrality of GitHub was part of its appeal. It’s where you went to see where nearly every (obviously not all) open source project was being developed. Based on his post, the network effect was a large part of the draw and the reason he stayed despite reliability issues. A more federated set of git UIs will never capture the same feeling.
Lately I’ve found myself taking the “if you can’t beat em, join em” attitude: if I’m not going to have a job in 5 years, I might as well help get there. It’s a strange feeling where it feels like the only way to exert free will is to accelerate my fate. The feeling of inevitable acceleration is difficult to ignore if you’re a software engineer in 2026.
I’m convinced that he meant rumination, not introspection. There’s simply no way to be “high agency” without some level of introspection. Rumination is essentially a kind of excessive introspection that leads to paralysis.
I remember there was a service that would do this by mail in the 90s. You had to fill out a card with each block letter and then it cost a few hundred dollars. I wasn't even a teenager then so I couldn't afford it, but I always wanted to do it.
When you sign up for an Apple account, you aren't "buying" anything. In fact there is a set of terms & conditions you agree to when signing up which most likely includes language stating that your account can be closed with the discretion of the platform owner. What we need isn't a shift from "buying" to "renting", but instead something akin to a Consumer Bill of Rights that states that you are entitled to appeal account closure if you are in good standing and can prove as much.
Ok fair enough, was a bit hostile there. No involvement with the project, and it’s practically vaporware at this point. But I don’t think it’s unreasonable to dig through people’s post histories, though. I also found the reference to 1599 buried in the FAQ.
Having said all that, film labs and rich enthusiasts do seem to be the target market for this product, if it ever launches.
> I had never even heard of an uncut developed roll of film before
That's how film is developed. Someone at a lab has to cut it.
> who is honestly shooting that much 135 film
How about a film lab? A place where "uncut developed film" is extremely common.
>it's worth 1600 Euros to buy a faster scanner for it
Price is 999 euro.
> pros who still shoot film would use a larger format
Some do, some don't. It depends on the project. I'm a little surprised by your comment looking at your history. You say you're a retired professional photographer and you've never heard of "uncut developed film" before? If you're retired in 2025, you must have been working when all photography was on film. You never developed a roll of film before?
The workflow for this scanner would allow you to thread an uncut roll of 35mm film through it. You'd have to spend more than $0 to get that kind of speed on a DSLR rig.
> Yes. We’re collaborating with several film labs in Berlin to benchmark Knokke against Fuji Frontier and Noritsu scanners.
> Sample results will be published before the Kickstarter campaign, so you can make a fully informed decision.
I don't care how cool your scanner looks or how "modern" the workflow is - it's samples or nothing. Additionally, if they were really smart, they'd collaborate with a well known film photographer instead of using someone's walk-around point-and-shoot photos.
I've noticed a big problem with AirPods Pro 3 on the NYC subway. Maybe my fit isn't right, but Adaptive/Transparent mode is a lot less "transparent" with really loud background noise - I can tell I'm listening to a processed signal rather than the natural muted sound of the AirPods Pro 2.
This is cool. I noticed that, after testing a few URLs, hitting the back button in my browser popped some state to load the previous iframe URL, but the URL of the whole page itself didn't change. It would be nice if the URL had a query param to reflect the currently shown iframe URL.
The ability to express joins in terms of SQL with Estuary is pretty cool. Flink can do a lot of what is described in this post, but you have to set up a lot of intermediate structures, write a lot of Java/Scala, and store your state as protos to support backwards compatibility. Abstracting all of that away would be a huge time saver, but I imagine not having fine grained control over the results and join methods could be frustrating.