Besides the short names, common blocks and computed gotos were the bane of my existence maintaining primordial Fortran. My first and intern project was translating a punch card era (early 60s was the best bet) code base that had been textified and could compile in f77. Fortunately I didn’t have to really deal with any strings
CoolScan support has improved a lot in the last month or so. I don't have one so I cant comment in practice, but its a very active project and I'd definitely encourage you to submit bugs if you have a coolscan.
You should check out the negpy project. It in my view has the best inversion process. It claims to emulate the whole analog print chain in the inversion process. They have a fold works cited.
It also automates most of the process. It works with SANE, some other legacy scanners, and camera scanning. It can even do trichrome scans automatically.
Funnily sub-zero fridges are considered the samsung of the semi-commercial brands. They prioritize things like customizable doors and easy to break but consumer loved features like ice makers and water dispensers. You will never see sub-zero in actual commercial kitchens.
> say "new semantic information". It should be communicated, and you can't trust an LLM to choose the correct database, you need to specify that yourself.
But I can most of the time, and correct it if it chooses the wrong thing. That's the whole reason LLMs are faster. Its the reason we can give a paragraph prompt and get a kLOC PR back but only need to correct about 5% of it.
The value of writing isn’t always to communicate new information. It’s often to align everyone’s assumptions. For instance, when I say casually to a colleague or an agent “this change will require a db migration” they understand it’s to my teams primary application database. If I submit a design doc to a company wide review which database is changing is critical information. If the 300 bits were truly enough your agent or junior engineer would implement the wrong thing correctly as they often do.
> The actual risk that the author does not even broach upon for investors... the thing that will actually torpedo this massive investment are the open source open weight chinese models that commoditize the entire endeavor.
OpenAI and Anthropic investors yes, however open weight models are good for cloud providers. They can turn the two large customers into direct ai services that can be spread across many customers and reduce the cloud providers overhead on ai services.
You can. Davinci is more powerful for this too because you can copy the parts of the node tree. So you can have a base edit for exposure, white balance etc then apply your look as a copy paste on top of the clean part. In Lightroom and most photocentric workflows you get one prebaked pipeline.
For all the potshots about AI, this update is huge even if you take away the AI features. They basically added lightroom to this release. There's some polish before you'd want to change your subscription, but its really tempting. It may be the best photo management/editor on linux. Yes, I know about darktable and rawtherapee and I stand by what I said. They also added a ton of motion graphics stuff which from the beta seem to be enough to undercut a lot of basic uses of after effects out. The later two features are in the free release as well!
Imo vistas biggest problem was they underspecced the minimum system requirements. Most peoples experience with vista was on sub 1gb of ram machines with a single core, no gpu and 32 bits. Vista was an os for modern architectures first. Windows 7 had the luxury of those features being the default at launch.
Moreover the two lost shuttles included human lives. Better to blow stuff up with demo payloads now before sending up large contracted payloads or worse human beings!
Games will typically un at 4k or less which is about 8mp on the other hand it’s difficult to buy a stills camera with less than 20 mp, and >40mp is common. Most algorithms are n^2 in graphics as well so we wouldn’t expect a linear speed up. I’ve tried dxo, Lightroom, and topaz they all perform about the same so I don’t think it’s particularly unoptimized.
I remain convinced we won’t look at project estimates as time based in software engineering as our primary cost estimate. And this is transition will happen rapidly. We’re going to shift to a capex/token spend model for project estimates where the business will say “ok I do want that feature for $1000 in tokens”.
A lot of enhancements came on the model side which in many ways enabled context engineering.
200k and now 1M contexts. Better context management was enabled by improvements in structured outputs/tool calling at the model level. Also reasoning models really upped the game “plan” mode wouldn’t work well without them.
I generally do this when I arrive at the agent getting stuck at a test loop or whatever after injecting some later requirement in and tweaking. Once I hit a decent place I have the agent summarize, discard the branch (it’s part of the context too!) and start with the new prompt
Its funny you mention excel, I see vibe coding in the business sense right now being a gateway to replace all of the ad hoc uses of excel. We've basically leveled up the quality of the software you can build before buying a SaaS product or a hiring an in house engineer.
I’m more interested in what happens when a language is designed specifically for llms? When doing vibe coding a lot of code is a lot more verbose than I’d do normally. Do we drop down the abstraction level because llms are just so good a churning out boilerplate?
Don't forget shortening copyrights would have a major impact on this issue as well! 25 year copyright would make most of these libraries public domain. Then the price would truly reflect what we would all like to be subsidizing: the new stuff.
Does the rights to Friends being traded around for the Nth time really benefit anyone?
Explanations aren't sufficient either. The industry has burned that bridge. Strong contractual guarantees. Ceasing personal data collection operations, etc. etc. Concrete steps only. Thus far we have one concrete step that is proof of the opposite direction.