> Imagine having to constantly fight similar urges all the time
I don't have to imagine, I have a child who survived a TBI that included damage to the hypothalamus. He's never satiated, always wants food. Even with strict diet controls and a locked pantry and a refrigerator with a lock and chain around it... he still manages to get food.
I disagree: code should be correct before it is clear. And because it's so easy to mess up a for loop (for me at least), I choose list comprehensions where reasonable.
> you're just being a jerk to the next dev that has to read your code
That's not very charitable to either party. You're assuming that the motive of the author is to be a jerk, and you're assuming that the reader won't understand. If I had a dev on my team who couldn't read a list comprehension, I'd (a) wonder how they were hired, and then (b) teach them.
Yes, I understand that. I guess my original question would have been better put: can the notion of "current state" be avoided with persistent data structures, and if so, how?
> Once you scratch a little bit the surface, you will see the extraordinary power of its persistent data structures.
I've heard this repeatedly, yet in the examples I've read (for web servers and for web ui work with cljs), they're using atoms with `swap!` to provide "current state".
Could you provide an example of using persistent data structures in a web app? Or am I mis-understanding?
> So the solution is to provide drugs that somehow deaden random neurons in somewhat random parts of the brain, and hope they don't cause massive side effects down the line?
The author didn't share a diagnosis, nor did he or she share the specific medication(s) that helped. Given that, how can you conclude that the drugs "deadened neurons"?
I share your skepticism of modern psychiatric medicine, and yet I think you might be missing some understanding and/or empathy for the patient. He or she is describing schizophrenia and major depressive disorder [1], and while often found together, either one can be utterly debilitating. It would not surprise me if the patient had the same concerns as you and I, but was so desperate, so hopeless that they were willing to take the risk.
[1] not a doctor, therapist, counselor or anything close
`In response to “Please describe the first time you witnessed misconduct by another employee but took no action,” 46 percent (532) advised they had witnessed misconduct by another employee, but concealed what they knew.`
If we can trust the survey results, methodology, etc, the minority of which you speak is 46%.
> I'm pretty sure the side effects would be utterly intolerable even at half of that dose.
I'm absolutely sure. My son takes methylphenidate for traumatic narcolepsy and hyperphagia. At ~60 kg with a 30mg dose, he's got tremors, sweats, chattering teeth, etc.
I can only assume that the researchers have reason to study using these higher doses in mice, but 1mg/kg and 10mg/kg was the first thing that caught my eye. Neurological degeneration seems entirely plausible when you're frying a brain with speed (so to speak).
I haven't found a satisfactory solution to having communicating containers across multiple hosts. There seems to be quite a few solutions in the making (libswarm, geard, etc). How are other people solving this (in production, beyond two or three hosts)?
(3a) No, because your data model never allows physical deletes.
(3b) And because you modeled up to 6NF with temporal keys, you've got the record from (1) and (2) and you know at what times they were related.
> Making an action undoable often more than doubles the development cost of that feature.
Every time I've added the feature, it's bordered on trivial (start a timer to execute the actual delete request, show a link to cancel the request, hide the DOM element).
I suppose if you were doing all the work server-side, then yah, it would be difficult. But the way GOOG does it (IIRC) it's not that hard at all.
I avoided routing with Angular as long as I could because my initial attempts were.. shall we say, painful (and I blame me, not Angular).
When I returned to the routing bits in my app, I picked up ui-router. It's such a nice library, I can't say enough good about it other than this: it should be in Angular core.
I most appreciate nested routes and the state handling; the integration with ng-animate is just butter. Thank you!
I don't have to imagine, I have a child who survived a TBI that included damage to the hypothalamus. He's never satiated, always wants food. Even with strict diet controls and a locked pantry and a refrigerator with a lock and chain around it... he still manages to get food.
It's a living nightmare.