Connectivity to databases was one of Delphi's main selling points.
I think one dude spread the myth of no DLLs in the Twitter thread, lots of people repeated it, and since Delphi 6/7 is not around anymore and it's hard to check, they got away with a slight historical innacuracy.
You want to restrict applications as much as possible without hindering their function. An assistant is only annoying if it can't actually do anything. If the hardware doesn't follow some cosy deal the user can swap out the API when they like, you would have to compete for real and forever.
Because there is simply no need to.
If there was one significantly better overall than Google (and not just a little better or better in just certain niches) people would switch.
Even if the products are better people don’t switch. Google organic has been a spam cesspool for a while with a few layers on top of ads and people don’t switch. I know some people that use Bing because it is the default of windows and they don’t switch.
> What this really signals is the intention (which might be sincere or not) of getting some sort of OEM deal with some device manufacturer.
I assumed they were talking about their partnership with Jony Ive/IO and an internal hardware product, not partnering (not that they won't do that as well).
If you truly believe you have a revolutionary device, you don't need to advertise before its time. You wait in secret, and launch it in a big surprise.
I smell bullshit, and some kind of partnership in which OpenAI provides model access and some third party hardware manufacturing. I could be wrong though.
This news only came out after The Information leaked that OpenAI is working with Luxshare to begin manufacturing a consumer product [0] a couple months ago.
Not officially. It was implied, but it wasn't hard data about their seriousness in comparison to subsequent hiring as well as their enlisting of Luxshare as a vendor.
Just as people once hated being told that Earth isn't the center of the universe, so goes the ego when it comes down to discovering the origin of our thoughts.
Prompt engineering: just basic articulation skills.
Context engineering: just basic organization skills.
Verification engineering: just basic quality assurance skills.
And so on...
---
"Eric" will never be able to fully use AI for development because he lacks knowledge about even the most basic aspects of the developer's job. He's a PM after all.
I understand that the idea of turning everyone into instant developers is super attractive. However, you can't cheat learning. If you give an edge to non-developers for development tasks, it means you will give an even sharper edge to actual developers.
This is true. I've been anti-ai but I started using it recently as an alternative to stack overflow (because google is shoving it down my mouth via search results). It's pretty effective. It does get things wrong from time to time, but then I just fix it up manually. I can't claim it's making me 100x more productive or anything like that. It's just a nice alternative to scrolling through SO answers and looking for the one with the green checkmark.
I still find it sad when people use it for prose though.
If an agent gets things wrong you should stop it and correct it instead.
Sometimes the correction will cost more than starting from scratch. In those cases, you start from scratch.
You do things manually only when novel work is required (the model is unlikely to be trained with the knowledge). The more novel the thing you're doing, the more manual things you have to do.
Identifying "cost of refactoring", and "is this novel?" are also developer skills, so, no formula here. You have to know.
Not native GUI, but as fast and useful as one.
It's more limited nowadays, but you can still do a lot.
reply