First of all capitalism doesn't apply to home grown diy stuff, so even if your argument was validity it would still be irrelevant here.
Secondly, even though I am very much in favour of a social state, so I am not arguing for capitalism in general here,
capitalism is pretty much a unregulated market economy.
How would you describe most societies of the last few hundred thousand years?
Socialism and everything related to it is a very modern concept. That was only made possible through the abundance of modern industrialisation.
If anything, the communist states that claimed to be defenders of socialism (I wouldn't call them socialist in any way but, meh), have shown that they were the biggest proponents of monoculture.
How do you feed a billion people through state organised agriculture? Through fields that are hundreds of miles long, so that they can be harvested easily and efficiently by a single machine.
You can still see the industrial agriculture wastelands of this philosophy in east germany today. Wind that would normally be broken by vegetation and the borders of smaller fields can erode the top soil and leaves nothing but unusable desert.
Way to project, not sure how you extrapolated all that from my comment. My point is that when a bottom line is involved, you will see only a few options come to dominance once the dust settles. And while home grown efforts do bear fruit, they very very seldom become mainstream.
I hate to break it to HN, but we are not the norm. We're here because we long for more, and have the skills to make that yearning reality. So while every anecdote in the comments is true I'm sure for that person, for the vast majority of people, this article is pretty accurate.
It's easier to write, test, debug, and maintain. I have apps now that a few dozen files, all <= 100loc replacing systems where the number of files is many more and the file sizes were 2000loc per file.
There's a difference between bowing to practicality / trusting someone, and trusting everyone in the chain that gets the packets from the server to your device.
Attackers might target the link between you and ISP, which isn't secured to an adequate degree. Servers ought to be harder to reach, but lack of hygiene displayed by offering only unauthenticated http downloads in 2015 means that even if people running those servers switched to https we know they are probably incapable of securing them. In a way it is better http stays as a red flag.
This has nothing to do with being vocal about security. Yea, they're helping the technical cause, but if you don't want backdoors in everything, the CEO's need to talk to the public so they're aware, and sending letters and phone calls.
I'm an American, and I think most Americans would recognize it as meaning "bullshit"; I certainly did. it's not commonly used but it is commonly understood.
I'm an American; it strikes me as an overloaded expression, used to imply both "bullshit" and "testicles", plus whatever the Sex Pistols were on about in their album title...
... yet in C. S. Forester naval stories, it clearly refers to steers or bulls.
So, I can only conclude that it is a random operator used to confuse colonials.
It was very divided 4-5 years ago, predominantly when underscore and jQuery were both champing at the bit to be the top utility library. It's shifted towards not monkey patching, but it's not not absolutely decided for many developers.
It was very undivided 8 years ago - it was common knowledge to never, ever override the prototypes of built-in objects. In fact, a major reason that JQuery won out over Prototype & Mootools was because the latter two monkey-patched built-in prototypes, and as a result were incompatible with each other or with any other library that overrode built-in methods.
IIRC, this was an interview question at Google when I applied in 2008, and I think one of the reasons I got the job was because I was aware of all of the pitfalls of it.
I managed to skip using underscore, but from a quick glance through the library, isn't the reason it's called underscore because it provides '_' as a namespace for all the utility functions, rather than altering Array.prototype the way Prototype did?
I would recommend the iTunesU - Stanford iOS 8 Tutorial series as well. Been a while since I wrote an iOS app, just watched it this weekend to see what was new, and found it to be great.
