It's easy to fall into a trap where your Banana class becomes a GorillaHoldingTheBananaAndTheEntireJungle class(to borrow a phrase from Joe Armstrong), and nothing ever gets freed because everything is always referenced by something else.
Not to mention the dark arts of avoiding long GC pauses etc.
It's possible to do this in rust too, I suppose. The clearest difference is that in rust these things are explicit rather than implicit. To do this in rust you'd have to use 'static, etc. The other distinction is compile-time versus runtime, of course.
Can you elaborate on this? I'm struggling to picture a situation in which I have a gorilla I'm currently using, but keeping the banana it's holding and the jungle it's in alive is a bad thing.
Data centers don't just heat up the water and return it - they evaporate the water into the atmosphere (yes, I know, the H2O still exists, but it's in a far less usable form when it's gaseous atmospheric H2O)
Do you have a source?
> "AWS now defines two types of Kiro AI request. Spec requests are those started from tasks, while vibe requests are general chat responses. Executing a sub-task consumes at least one spec request plus a vibe request for "coordination"".
I still don't understand why pricing can't be as simple as it was initially and presented in a clear and understandable way: token cost this much, you used this many tokens, and that is it. Probably because if people would see how much they actually consume for real tasks, they would realize that the "vibes" cost more than an actual developer.
Deleted Comment
That being said in C and C++ the single file libraries typically have no dependencies, which is one of the major benefits.
Dependencies are always something that a programmer should be completely clear about, introducing even one new dependency matters and needs to be thought through.
If someone is blasting in new dependencies that themselves have new dependencies and some of these overlap or are circular, and nothing is being baked down to standing alone it's going to end in heart break and disaster no matter what. That basically the opposite of modularity, a web of dependencies that can't be untangled. This applies to libraries and it applies on a smaller scale to things like classes.
For the communists isn’t this exactly what you want? State ownership of the means of production? Shouldn’t you be cheering Trump on for nationalizing corporations and/or industries or at least heading in that direction? Or is the primary criticism he isn’t nationalizing industries fast enough?
What we're seeing here is a situation in which favored firms are subsidized by the government in exchange for personal loyalty to the leader, but profits are still privatized. This is called the "fascist mode of production"