So many people neglect the lack of TCO in Python, it’s like a beginner mistake you make when you try to make your Python read like the Haskell you just learned. Not sure why you’re getting downvoted though.
I agree with you there. We did email-based stand-ups for a while and ditched it. It devolved into a mechanical habit of "everything is going great" type answers that nobody payed attention to..
The async aspect of it is convenient, but for me as a team lead, often times the standup is also an opportunity to ask follow up questions, to see if stories are on track, or to determine if somebody would benefit from pairing for the day. These things become increasingly important if you have an uneven balance of dev experience or domain knowledge within the team.
> All the evidence (at least for the pre Omicron variants) suggests that the reality, as viewed by death rate, is orders of magnitude more bleak.
Dr. Rochelle Walensky, Director of CDC was actually in an interview recently where she said 75% of Covid deaths occurred in people with 4 co-morbidities.
This statement begs the question of what percentile of deaths occurred with no co-morbidities at all. In my mind at least, I don't know enough about the death rate to inform if its bleak or not judging as a healthy 41 year old without complicating medical factors.
I was looking at the CDC data for that claim, it looks to me like many of those "co-morbidities" referenced appear to be sepsis, respiratory failure, heart failure, and co-infections:
Most of those sound like they would have been caused by COVID. So, were they probably a fairly normal 41 year old, until they were in the hospitalized for COVID, developed complications, and died. Or is there more to the model here?
Even more confusingly, about half of the US population is obese, but it is only mentioned in a small percentage of death reports (up to about of quarter in the younger populations). Taken naively, this would seem to imply that being obese actually strongly protects from death. But I suspect that it is instead simply not being listed in the causes of death in most cases.
To answer my own question two weeks later, it turns out that number quoted on GMA was specifically the percentage of vaccinated people (https://www.snopes.com/fact-check/covid-deaths-4-comorbiditi...). Her statement had no relevance to an unvaccinated person, as the grand-parent's comment was asking about.
I’ll bite. I have been frustrated with the lack of stable apis in JS in general over the last few years.
It may be an ecosystem problem but I think the big projects have an obligation to set the tone for what is acceptable elsewhere and not just jump on the next wizbang thing that’s marginally better or more correct.
Pros and cons but I see the cost of maintenance being very high in client side js compared to backend.
The frontend ecosystem is definitely less mature than backend. Gmail and Google Maps, two of the first "real" client-side applications, were launched in 2004 and 2005 – so the entire ecosystem is really about a dozen years old. Before that people didn’t really “realize” that JS and web was a real programming environment. That means there's a lot to catch up on and a lot to experiment with as people figure out the best ways to build things. Compare this to backend or infrastructure development which have had decades to develop.
That said – I completely recognize that this can be painful. You don't always need to use the latest stuff though. If a "less fashionable" technology does the job for you, you can definitely use it. And trying to mitigate some of this complexity is why my team works on projects like Create React App which (whether or not you're using React) can insulate you from some of the "churn" that people often feel in the ecosystem.
In React itself, we try to have as few breaking changes as possible. (And our team needs to keep 50,000 components at Facebook working through our changes, which is a major incentive to not break things unnecessarily.) Our last major release, React 16, was released in Sep 2017. But it actually included almost no breakages (we mostly bumped the version number out of caution because it included a huge number of internal refactors). So I'd say our last "actually breaking" release was React 15, in Apr 2016, about 2.5 years ago. React 17 will probably be released sometime next year, so we're talking 3-ish years between releases. I think it's hard to do much better than that without stopping forward progress. Note that if we don't improve React quickly enough people will abandon it for another (incompatible) library, which doesn't really solve your problem either. So we try our best to make sure we're working on (what we think are) the right things and do our best to get it right the first time.
