@jneira@hmemcpy@Savlambda idk seems like neither term is correct in todays landscape.
Almost everythig is declarative because compilers do a lot of runtime magic for low level stuff.
Almost every "declarative abstraction" is imperative cuz compilers/runtimes rarely if ever take the theorethical advange
@tibo
Hope it isnt too late, I have one:
When im typing something (using the text input or voice input) and i get codex's input request, it breaks my input.
i think the asks from codex should either be above the input box in those cases or queued after i stop using the input box
while im typing if i hit enter or use the mouse I end up accepting thigs that pop up in that particulary moment, very annoying ux.
Discovered the 2nd hand servers world and bought a server to use as homelab
I can’t believe it took me this long, having a homelab is AMAZING.
Feels so enabling!
Yesterday I told codex to write some stuff and use a decryption library i wrote by hand a while ago
The end result failed at decryption every now and then
Turns out it wrote its own implementation, I corrected it by using my library
It worked 100% of the time, what a feeling.
“me” is ok, it isn’t a “2 letter variable”
“c” is gone by either piping (fp) or fluent syntax, even “_” is better because it is the “main variable” of the function.
no name over useless single letter wins everytime, otherwise if “c” must be declared then it doesn’t help at all being that short.
funny how this feels incredibly irrelevant in AI era. it used to feel as such a fun conversation to have 🤣
when i’m driving (i know what to do) i rather it being concise & direct, but when im planning or unsure of the best outcome I doo need it to be more explanatory and collaborative
so far so good it changes gears correctly, although the collaborative part is not quite right, is like codex becomes the driver instead of actuality collaborating