sadly we aren't all as smart and worthy as you are, and don't have a decade old react-like hanging around. some of us even prefer the idea of using an open source library for the various benefits of doing so.
i wish there was something like `jbuilder new`, but alas. my current impression is that everything in ocaml-land wants you to spend time writing cryptic configuration files and inventing bespoke project structures.
I mean stability in what they are offering. LTS versions are essentially being done through the concepts of Editions, where every other year or so, a new edition is released and the changes and new features from the previous edition up to that point are summarized.
It's not that rust code is breaking, that's not it. It's that with new things happening every six weeks, if I wanted to write something that 100 developers will work on, how would I do that? Where I would begin? What version should I choose to ensure everybody is on the same page?
Once 2018 edition is polished up, this will be mostly a solved issue, so kudos to rust team.
Note that official Rust team position is that Edition is explicitly not LTS and should not be considered as such.
Actually there was a long thread on Rust internals forum where they worried people may mistake Edition as LTS, but conclusion was that confusion can be prevented by explicit messaging. Looking at your post, I think worry was justified.
imho, a get() from cache when you already have the value seems like an unnecessary waste of cycles and network traffic.
plus this arrangement would seem vulnerable to a pathological case where you found the V from the db, but have a full/failed/partitioned cache and end up faulting or otherwise not returning the V.
> That is a funny question. It is like asking: what is the evolutionary advantage of a broken leg?
i'm unconvinced... a broken leg isn't a normal biological function, while (afaik) pain is an entirely internal process that is a 'response' mechanism.
> Sometimes things go wrong and the result is pain. There is no purpose to it; it just happened. Not everything has an evolutionary purpose.
the ostensible purpose of 'some' pain is to cause you to stop or avoid doing something damaging, or being aware of a need to seek remedy. for those few people who don't feel any physical pain (congenital analgesia)... life is actually more dangerous.
when it comes to incapacitating levels of pain, things seem to get murky. there is some arguable benefit to adopting a protective posture (covering a wound, adopting a fetal position, etc) to mitigate further harm... but it seems these same behaviors can also increase risk of harm as well, especially when it comes to pain causing reduced situational awareness and other reasoning impairments.
isn't this a bit reductive?