Messaging apps are a lot harder to get right than you might think. I worked for years on messaging using XMPP and the problems were legion. I'd be very interested in seeing how a vibecoded app does at scale, especially with the presence problem.
> One person with an M-16 could take out an entire massive army of people wielding spears
I have to disagree. All it would take is for this army to surround the person with the M-16 and wait for a magazine change, then hurl 50 spears at the hapless pincushion. And that's not counting the probability of the rifle overheating, jamming, etc. after long enough.
I realize I am taking this probably too literally, but my point stands :)
You could learn some mainframe stuff using the Hercules emulator[1], but you'd have to find some z/OS installation media somewhere, and I'm not sure if that might infringe copyright or something. Also, JCL is absolutely horrible IMO.
Elixir is not Ruby, it just has a somewhat Ruby-like syntax. The similarities end there. Elixir does not have the performance issues that Ruby has (although it may have different ones!)
I'm not making these claims. A senior doctor in Western Europe is making these claims[1].
> Fatality is the wrong yardstick. Catching the virus can mess up your life in many, many more ways than just straight-up killing you. "We are all young"—okay. "Even if we get the bug, we will survive"—fantastic. How about needing four months of physical therapy before you even feel human again. Or getting scar tissue in your lungs and having your activity level restricted for the rest of your life.
This is false. Studies done in Wuhan show that people with CVD have well over a 10% mortality rate. In addition, COVID-19 has the potential to cause permanent disability if it does not kill you first.
It’s not only over 80s. It’s anyone with cardiovascular disease, diabetes, hypertension, morbid obesity, and some others, which collectively describes large swaths of the US population.
Death is not the only thing that coronavirus can do to you.
You can spend weeks or months in therapy before you are recovered, or you can get scarring in your lungs - or worse - that leaves you with a permanent disability. Not to mention damage to other organs.
I think many are discounting, or are unaware of, these other nasty possibilities. We don’t know enough yet of the prevalence of these effects, but we do know they happen.
And from the article: "But I know what I don’t want. I don’t want to be stuffed full of tubes with doctors hovering over me, pleased with themselves for keeping my heart beating for another five minutes, eking out every last painful second. That, to me, is dystopia.”
> Immutable data structures are great, but when it's the default, it's a huge win in cognitive-overhead. Maybe that feature isn't unique to Clojure but it's certainly not a prerequisite to being called a lips or a functional language.
Yes, indeed.
TBH, I developed in Erlang for 10 years and, as a result, developed a strong preference for "immutable data structures everywhere".
Unlike LISPs that I've seen (admittedly not that many), with Erlang there simply is no global data so no vars to change - it's all done via function parameters and tail recursion (Erlang has TCO baked in, btw).
> Too many people mumbling and/or talking over each other in meetings, so the remote has trouble following or breaking in. Inadequate videoconference and VPN infrastructure making that worse.
This, in spades. Thanks for taking the time to explain in more detail.