> A company which sells that much software can certainly afford to re-implement an AGPL component; or at least implement a good enough stub implementation to make the software run acceptably.
If you ever work at a software company, you'll understand that you never have enough time to do what you want, and you have to pick and choose the most valuable tasks and go with those. Rewriting perfectly working code is never valuable.
I do, in fact, work at a tech company, and do, in fact, write a lot of code to do my job. However, it is not a software company, as it does not sell proprietary software directly.
> Rewriting perfectly working code is never valuable.
It might be far more valuable than the other option, i.e. releasing the proprietary software under a free software license. An AGPL licensing issue will only ever, in a worst case scenario, force you to choose one of those two options, no more.
Every GPL violation that I've ever heard about remedied was remedied over time often months to years. If you never create derivative works you don't intend to share you will never have an issue. If you do clearly and obviously conspire to break the law you can probably still negotiate yourself enough time to comply with the law and retain the rights to your own software after having tried to get away with breaking the law.
No, your comment just doesn't make sense. Lightbulb manufacturers are not responsible for wars because tanks have lightbulbs in them, and GitHub is not responsible for all the harm in the world either because some bad actors use GitHub.
Sorry, I can't even discuss this with you. I rather disagree - this is what the whole "military-industrial complex" is about - but it's off-topic and forbidden.
This is totally not what the "military-industrial complex" is about. Wow.
The MIC concept is a specific application of the general idea of regulatory capture of policymakers to the vertical of defence contracting. This is nothing like that: the corporation here isn't a defence contractor and they're not bribing the government. It fits 0%.
There are dozens of models that various companies use. When applying for a mortgage, there are different models used when applying for a car or an apartment. Credit Karma gets their scores from the credit bureaus with some particular model, which probably isn't the same one when you go try to get a car. It's not _wrong_ it's just different.
To be clear: credit karma shows VantageScore 3.0 whereas most credit cards, mortgages, and auto loans use a FICO score more often. That being said, there's a bunch of FICO versions in active use. For a rundown of them see here: https://www.investopedia.com/articles/credit-loans-mortgages...
Some esoteric lenders might use VantageScore and, for the most part, if you have a good VantageScore 3.0 you'll most likely have good FICO scores.
There's a good 55 point gap between my FICO and my VantageScore, so if you're getting a mortgage or something, you'll definitely want to check the FICO value to at least know if that's the case for you.
> By squashing the who and the message are lost. But we think that's okay because it's a lesser evil than having a bunch of commits in trunk. Which is bullshit.
Well, don't erase the message when squashing. My policy is that we take the pull request and use the message title and description as the actual message of the squashed commit, which works great.
Having a bunch of commits IS really bad. One idea = one commit is so much better than some bullshit three commits of "refactored" "made mistake" "back to normal" those are just as worthless to keep in the history as recording your typos+backspaces+fixes into the history.
Anyone who is glorifying hunter-gatherers needs to look at the hard evidence, of which we actually have. There are plenty of recorded evidence of hunter gatherers societies and there are still many that exist, such as in Papa New Guinea for example.
Their lives are full of incredible violence and murders happen all the time. There is a reason that the populations do not exceed a certain capacity. Because they kill each other. (Sometimes it's because there is only so much food in a certain area to support them) There are plenty of sources. Guns, Germs, and Steel is a great book that can explain some of this.
If you ever work at a software company, you'll understand that you never have enough time to do what you want, and you have to pick and choose the most valuable tasks and go with those. Rewriting perfectly working code is never valuable.