An contrived example: let's say an unfixed Bootstrap 3 bug is that there is a formatting error when rendering "div.jumbotron > h1 > span.label > small". You could replace the last small with you own css class and be done.
Contrast that to a bug in Angular, for example, that enabled a XSS bug. You'd want to upgrade Angular, instead of manually patching or adding a workaround to all your forms.
I'm not disagreeing, but one thing that makes this different is you can easily fix most Bootstrap bugs by overriding it with some custom CSS, or just not use that class. It's different than some deeply integrated code that you have to patch and maintain.
This reminds me, a few years back I was reading the code of a few different obscure libraries. One of them had a primary process that would spawn different worker processes and kill them off if certain conditions were met. No joke, the primary process was named "Hitler".
I may not have been clear, but I understand and fully support their right to charge for software and services. I just haven't worked on any projects for which their prices fit in to the calculation.
I have a love-hate relationship with nginx. I love that it's fast and rock solid. But recently I keep on getting tripped up when the directive I'm trying to configure is only available in the paid plan, the pricing of which puts it out of (my) reach.
Also, there really should be separate docs for the open source vs paid plan.
That said, I do plan on kicking the tires on the HTTP/2 support.
Sure if you want a full set of native tools I won't suggest otherwise. But a full cygwin install is way more invasive than node, and if you just want some specific tools, vorpal might be for you. Or maybe cygwin is. Whatever works for you.
But a benefit might be cross-platform compatibility seeing as some OSes don't come with, say, grep out of the box. While you could use the native tools, there could be some benefit to writing your own to do exactly what you want consistently.
I don't really disagree with you, but just pointing out there is some benefit to writing one's own CLI.
Having grown up near Portland, I too was surprised about the historic levels of racism. Though in retrospect it is believable, considering the percentages of minorities is (or at least seems) so much lower than anywhere I've lived since.
My recollection growing up was that seeing a minority was a noteworthy occurrence, because of it's rareness. That changed when I moved into Portland proper, but I never really noticed racism there.
I have no numbers to back me, but my impression is the vast majority of OS X users can't be bothered with doing backups even with a built-in Backup solution, much less a 3rd party one.
Time Machine isn't going to stop someone who places value on doing proper backups from doing them, and if it makes it easy enough for my mom do back up her files, then that's a net win — not marketing.
And hey, it only took me reminding her 5 times before she got the external drive and set up Time Machine — no family tech support involved.
> Important to note: because JavaScript itself is always backwards-compatible (1JS), any code that runs on Node will run on iojs, but not necessarily vice versa.
Though I'd imagine this will not hold true with addons, seeing as there are vastly different versions of the V8 engine.
An contrived example: let's say an unfixed Bootstrap 3 bug is that there is a formatting error when rendering "div.jumbotron > h1 > span.label > small". You could replace the last small with you own css class and be done.
Contrast that to a bug in Angular, for example, that enabled a XSS bug. You'd want to upgrade Angular, instead of manually patching or adding a workaround to all your forms.
That's what I was thinking, at least.