Are you evaluating the points made by James from your context and limiting your understanding? If you work for a company where software is not a differentiator, but a cost to doing business, then using frameworks, DI or not, is probably the right thing to do. But if your code is a core part of the business, you probably don't want to give control to some third party that may screw you.
All successful companies that I have worked for where the code is core to the business, rolled most of their own software (NPM for the web aside). Long term you need that control, understanding and speed of change if required.
What major upheaval examples should we fear? DI frameworks seem quite reloable, trustworthy, & consistent. I cant think of any examples of a community being burned by trusting their framework. I cant think of any cases or blogs where someone has been left up a creek, has ended up hard clashing with their framework
I dont see what justifies this fear, uncertainty, and doubt.
Yes, I evaluate it from the perspective of developing enterprise software where I need to designate extension points for a fluid number of team members. Only using CI can I balance the flexibility of offering the interfaces people need with the oversight needed.
Also just develop your own DI if you consider it business critical but not yet commodity (you don't do your own logging/crypto/math libs, right?).
It seems to me that your statement has some assumptions that may not be true, that a MCAS failure caused runaway trim would be recognized as such by the pilots. The ultimate issue may be a runaway trim, but a MCAS failure may not produce the normal indicators that would lead the pilots to diagnose the failure correctly within the time available. Assuming that a MCAS failure is the same thing as a runaway trim failure and should have been handled by the pilots, while technically correct, might not be an appropriate conclusion.
I have a corporate Amex card, and even though its a "Corporate" card, given to me by my employer, it is in my name and I am legally responsible for it. My company will reimburse me for my expenses if approved by my manager. I have always thought this was a liability and weird, but everybody else at the company (a 500 company) thinks it's normal. So any expenses not approved at the end of the month are my responsibility. Anybody else have similar experiences?
Because awareness of the gap between measurement and conclusion might just be the most important thing in the world, and people and governments fail spectacularly at it all the time with significant lasting effects on society.
For anyone reading this who doubts what BugsJustFindMe said here, as an example I invite you to examine how the government measures the loudness of broadcast commercials compared to the programs that surround them. We had seventy years of blasting people with commercials, all because the way of measuring the loudness does not match the actual "loudness".
Trying to get to the factually right conclusion is an expression of humility, because it allows admitting that our initial expectations were wrong.
Using the right conclusion to properly guide our actions is necessary for compassion and love -- if you truly with to benefit others, then your actions must be correct and guided by the right answers.
The challenge is updating other people's beliefs without being seen as an attack.
Take that anti-cynical perspective back to Reddit thank you, here in Hacker News we have no time for such leniency.
===
On a serious note, I enjoyed reading it. I think it's clear(ish?) that the approach taken by the author leaves a little to be desired, he seems to be modest and quite aware of this.
It's no different to Myth Busters really. They use the scientific process and rarely express them selves past a sample size of one. But for the purpose of advocating science and it's methods, I think it's good. If it's not well... I'll leave you all to stick to reading Journals?
