676 karma · joined August 5, 2020
From the transcript:
> (Model, thinking): Could also be Lake Zug, considering the architecture. The user mentioned they were in Switzerland for postgrad, so it could be a familiar place.
> (Model, thinking): (Goes onto analyse the EXIF data)
To me, this reads as a genuine, vision-based guess, augmented with memory of your other chats, that was then confirmed with the EXIF data. Seems to me that the model then confirms it did so, not that it skipped straight to checking the metadata and lying about it as you accuse.
Before posting this I feel it’s worth clarifying I didn’t take you to say you do hate them as people, please excuse the ramble.
Standards are already emerging, including MCP, and to say that simply because they’ll evolve and be replaced over time means they’re not ‘real’ now is ridiculous. Look at the early internet and web as examples.
Local models, even accounting for reasonable progress and device performance improvements, will always, inherently, be behind the eight ball compared to SOTA models. While they may be sufficient for the low hanging fruit, I’d not bet against the frontier models being every bit as compelling relatively speaking.
Using weasel words like ‘real’ and ‘x is the future’ is astoundingly arrogant, and anyone claiming with confidence that they’ve got any idea where we’re heading is almost assuredly wrong.
If we take the premise at face value, then this is a time management question, and that’s a part of pretty much every performance evaluation everywhere. You’re not rewarded for writing some throwaway internal tooling that’s needed ASAP in assembly or with a handcrafted native UI, even if it’s strictly better once done. Instead you bash it out in a day’s worth of Electron shitfuckery and keep the wheels moving, even if it makes you sick.
Hyperbole aside, hopefully the point is clear: better is a business decision as much as a technical one, and if an LLM can (one day) do the 80% of the Pareto distribution, then you’d better be working on the other 20% when management come knocking. If I run a cafe, I need my baristas making coffee when the orders are stacking up, not polishing the machine.
Caveats for critical code, maintenance, technical debt, etc. of course. Good engineers know when to push back, but also, crucially, when it doesn’t serve a purpose to do so.
*I don’t know to what extent it’s worthwhile discussing whether you could call these the same model vs. entirely different, for any two products in the same family. Outside of simply quantising the same model and nothing else. Maybe you could include distillations of a base model too?
It’s forwards compatibility if we’re discussing the idea of the program being compatible with future versions of Windows, but that’s neither the point of what was suggested, nor is it realistic — breaking changes, or compatibility, are going to be at Microsoft’s hands and largely an intentional decision at a platform level, not something an individual developer can shore up against.