The advanced version also has a locally hosted chatbot per primitive.
We’ve figured out annoying casts with next gen type coercion: type hallucination - the LLM will try to figure out how to do any necessary conversions at runtime and just kind of guess any missing details.
The best thing is it doesn’t ever do the same thing twice. So if it causes a bug the first time, it might not the second time.
This already happens in enterprise code bases with dummies running the show and juniors coding. Every primitive is actually a god object that can work at any level of the software stack.
Soon we will see the revelation of app driven development where the fundamental primitive type is an app.
Thread -> app
Class -> app
Object -> app
Struct -> app
Union -> app
String -> app
Integer -> app
Boolean -> app
Don’t worry ram is cheap, right?
Each primitive has at least one Electron instance dedicated to it. The advanced version also has a locally hosted chatbot per primitive.
We’ve figured out annoying casts with next gen type coercion: type hallucination - the LLM will try to figure out how to do any necessary conversions at runtime and just kind of guess any missing details.
The best thing is it doesn’t ever do the same thing twice. So if it causes a bug the first time, it might not the second time.
Or even better, a different bug!
It’s a dynamic developer experience
Software As A Surprise
This already happens in enterprise code bases with dummies running the show and juniors coding. Every primitive is actually a god object that can work at any level of the software stack.
At least we still got float right… right?
That’s three apps for each the sign, mantissa and exponent.