Author here. It goes without saying, doesn't it? It's literally called "junk food."
You can get information about why it's bad for you from a million sources (the Center for Science in the Public Interest, which I briefly mention in the piece, is a good starting point), but information about how it came to be? Now that requires a little digging.
You need to be told that deep-fried (or even baked) carbohydrates covered in trans-fats && heavily salted artificially-flavored mock-cheese powder are unhealthy?
As a general rule, avoid eating anything that is Trump-colored.
They might simply be afraid. SoundCloud has all the small artists and all the remixes and DJ sets that are missing in spotify and are already on good terms with labels and artists. SC are planning their own streaming service and once they additionally have the same label based library spotify has they would be a direct competitor.
Isn't some of the draw of SC that the artists know they'll reach an audience? I am not a Spotify subscriber, but I wouldn't think to go to them or Pandora for any unsigned artist - I immediately go to SC.
Microsoft has a document (KB257757) strongly recommending you not try to use Office server-side. They have some recommendations on what other things you could do instead.
Putting the TLDR here because it's really good, and the minimum that one should take from your great article:
The takeaway here is that not all third party code will jive with your app’s intentions. Not all developers take security precautions. Not all libraries on NPM are worthy of being a part of your application. The moment your own code becomes the minority shareholder in the repo and you’re depending more other developers around the world to keep your company afloat than you are yourself, you better make sure you have vetted the code upon which you’re depending. If the head of dev-ops tells you you can’t use a library, trust her judgement before resorting to Millennial cynicism.
On our own projects and experimental R&D efforts, let’s have at it and make bleeding edge code that changes every day. In a professional environment on code that will be used in production in E-Commerce scenarios, though, for the sake of all that is sane in the world, let it bake. Let the community vet it for us! We need to build sites on stacks that don’t implement breaking-changes every week simply because the primary contributor had a stylistic change of heart. We need to use libraries and frameworks that recognize exploits and take extra security measures. Customers trust us with their personal information, credit card numbers, photos and media. We owe it to them to give a shit.
