> For complex enough and long-running application your run-of-the-mill Rust (so probably what AI would generate) will likely be slower than your run-of-the-mill Java.
That phrase "complex enough" seems to be quite load bearing.
At which point does complexity reach the tipping point where a Java implementation becomes faster? From my experience, the more complex the application, the more enerprisey the Java code becomes, relying heavily on dynamic capabilities that make it slow even by Java standards.
It seems to me that the phrase "non-deterministic", which has mathematical definition, is used as a fancy word for unreliable - same way that "misinformation" is used as a fancy word for lies.
But for the point I was making, it is in fact not an alternative. In my version each SQLite connection is confined to a sandbox, and a C memory bug cannot corrupt the Go runtime, call stack or heap. In their version, a C pointer becomes an unsafe.Pointer that can address all Go memory.
Immediate reclamation, yes. There do exist a number of reference-allocation algorithms that performs deferred reclamation similar to how tracing GC does.
There do exist algorithms for resolving them, and that process can too be deferred, but also restricted to subgraphs and only when cycles are possible.
This is one thing I actually do with a chatbot, instead of an agent. Voice mode even.
I start talking to it while doing menial tasks like cleaning or doing the laundry, and I discuss the architectual decisions and options until I come to some resemblance of a plan.
Good side of this approach is that I can't just "skim over" or "copy paste" things - either I understood them and can repeat them myself, or I can't. It takes more time than /grill-me and similar approaches, but it's the only approach that doesn't make me want to claw my brain out.
I do the same, but without AI in the loop. Just me and my thoughts while cleaning or doing laundry or going for a run. The best designs and architectural choices and algorithms I've come up with in my carreer were developed and/or refined that way.
It's very enlightening, though it requires being comfortable with being alone with ones thoughts. It seems to me many people are not and need constant distractions and/or dopamine kicks.
Thinking alone about fundamentally deep problems can be poweful, but most software problems are not that deep, they follow a pattern, and it's only a question of discovering them. Doing that alone is inherently slower and less efficient than discussing it with a colleague.
AI just serves as a substitute - an artificial conversational partner.
I feel like you consider yourself more virtuous for not using AI for discussion. Would you consider people who don't talk to colleagues at all, but do all the work themselves more virtuous in an analogous manner?
For what it's worth, Prometheus was a Titan, and Titan was immortal, so his liver regrowing the next day wasn't really that special. If eagle fed on his heart, or lungs, they would've regrown too.
The Greeks chose liver because it symbolized the defiance Prometheus had against gods.
I don't know about the Greeks but I know a lot of ancient cultures thought the liver was the most important organ (probably because it's full of blood).
For example in Persian poetry the word liver is found pretty much everywhere you would expect to see the word heart.
"You are my liver" is a nice/romantic thing to say to this day.
There's really no knowing why the Greeks chose liver, or some specific Greek chose liver.
It could have been because the liver was regenerative and they were using the titan with the regenerating liver as another reference to humanity, or it could have been as someone pointed out because predators like to eat the liver first, or it could have been that you can take damage to the liver and live for hours afterwards in agony whereas the same amount of damage to the heart or lungs is apt to cause death to come much quicker.
Perhaps there are undiscovered variants out there were the eagle or a serpent or some other animal attacks his genitals, or his eyes.
But at any rate the Eagle ate his liver, it means nothing in particular, and at the same time it means every particular interpretation we can place on it.
Whatever the actual reason for choosing the liver was, we can be certain it wasn't its regenerative property, since such proprerty was unknown to the Greeks at the time.
Probably not, I don't think I ever read Galen mentioning it, but then again people would get injured in the liver and recuperate better than other injuries I suppose, which makes me think it is surprising if he didn't.
Just went and checked, evidently he never said anything about it.
old American translation of Galen and Hippocrates for anyone interested, as it can be
difficult to find otherwise
I'm thinking the Greeks chose liver because it is the first thing that many predators will eat from a kill - large, more nutrient-dense than almost any other tissue, and relatively quick to access.
But why were those accompaniments chosen for the liver? Because all three foods are high in tyramine, which is toxic if you're on an MAO Inhibitor. Why would Hannibal be on an MAOI? I have no idea, tbqh. They're for depression and Parkinson's, not antipsychotics.
There are a bunch of Japanese words (including a several loanwords from Chinese) that use the liver / gallbladder metaphorically for courage. Both derive from associations between the humours and personality / behavior. I have no idea, however, why both Eastern and Western naive psychology associate gall with, well, gall.
You left out the important part, that Greek influence made it all the way to Japan, in some cases identifiably intact: "[The Greek wind god] Boreas became the Japanese wind god Fujin through the Greco-Buddhist Wardo/Oado and Chinese Feng Bo/Feng Po ("Uncle Wind"; among various other names). The mother deity Hariti [Kishimojin in Japan] was inspired by Tyche."
I am losing more of what little focus I've had every day.
reply