After a big release changes functionality and design, a lot of people will complain. ‘OMG! Things CHANGED!!!!’ Mostly they’re mad about how their clients are complaining, but … shouldn’t you have warned them in the first place?
Using launchd instead of cron on a Mac is a brain tickler sometimes, especially if you’re used to cron!
You may not like it, you may find it distasteful, but it’s perfectly acceptable, license wise, to use certain products for anything you want. Just don’t break the law.
Risk theater is the art of looking like we’re reducing the risk in our products without actually doing a single thing of value.
“Those who expect to reap the blessings of freedom must, like men, undergo the fatigue of supporting it.” — Thomas Paine
“An avidity to punish is always dangerous to liberty. It leads men to stretch, to misinterpret, and to misapply even the best of laws. He that would make his own liberty secure must guard even his enemy from oppression; for if he violates this duty he establishes a precedent that will reach to himself.” — Thomas Paine
I may not agree with what you do, but if it’s legal, I will defend your right to do it.
It’s an accepted fact that all code will, at some point in time, break. The Open Source community is plagued with this problem, but it’s not endemic just of them. Software aging and rare conditions cause failure in all software.