_greim_

45 ms·

451.
by _greim_ 12y ago
I'm trying to boil this down to an easily-digestable list of benefits for server-side development, since I'm completely unfamiliar with webpack. So far I have this: * Transpiles code that runs in node, not just code that run
452.
by _greim_ 12y ago
A common way to get riled up about your favorite cause is to point to the state of the world and say "See? Look how bad things are." Pinker's argument will thus fall into the cross-hairs of almost anyone with a political agen
453.
by _greim_ 12y ago
> ...it was not worth writing down though. I disagree. Nature versus nurture is a difficult but interesting topic. Is our preference for high ceilings caused by culture and experience, or is it something we're genetically predispose
454.
by _greim_ 12y ago
So is the default use case this? process.on('unhandledRejection', function(ex){ throw ex; }); ...the idea being that it's analogous to an uncaught exception bubbling up to the top and causing the process to
455.
by _greim_ 12y ago
> By homogenizing service offerings... Not quite homogenous. Providers could still compete on speed.
456.
by _greim_ 12y ago
Just dive in. The best way to find issues is to be using modules in your own projects. And of course, be easy to work with, know when to/when not to back down, conform your code to the project's conventions at all times, yadda yad
457.
by _greim_ 12y ago
There's a progression from ignore mobile => make it work on mobile => responsive design => adaptive design => mobile first . But that's not far enough. Native mobile apps are mobile only , so in order for web
458.
by _greim_ 12y ago
If I understand, they do remove sound using physical absorption panels. But since absorption by itself feels dead or unnatural, they mike the remaining sound, model it in a virtual space and play that back into the restaurant (or whatever)
459.
by _greim_ 12y ago
I should clarify, there are lots of smart people using and occasionally contributing to node outside the inner circle of core contributors, many of whom will be using node (i.e. not io.js) for a long time. I was wrong to suggest otherwise.
460.
by _greim_ 12y ago
Depends on what you mean by "still developing for Node.js" which is subjective. Going strictly off activity, the graphs on github[1][2] show node trending ever downward from a high back in early 2012, and iojs significantly spikin
461.
by _greim_ 12y ago
It baffles me how little they acknowledge io.js in their public communication. Node is a weirdly paradoxical community composed of a small, really smart core surrounded by a vast but shallow sea of lip service and hype. With this fork io.js
462.
by _greim_ 12y ago
Agreed; "enjoy building stuff" paints a more complete picture than "enjoy coding."
463.
by _greim_ 12y ago
This seems like a symptom of learning to code for the sake of being able to code , versus learning to code because you enjoy coding . It's just as much work in an absolute sense, but the process in the latter case seems more effortle
464.
by _greim_ 12y ago
I'm not an economic expert but all these points seem plausible except I was wondering about this one: > $31M less in spending, economic growth, job creation... Wouldn't there also be a corresponding $31M increase in spending fr
465.
by _greim_ 12y ago
> CenturyLink and Cox were perfectly fine dabbling in 50mbps service for the rest of eternity without true competition. Why isn't there competition between those two?
466.
by _greim_ 12y ago
It should start being called "the jQuery effect" since it's one of those libraries that comes to be considered by the community as a standard way to patch the environment. Not only that, but some people begin to develop very
467.
by _greim_ 12y ago
I had a strongly religious upbringing, but later in life I transitioned and acclimated to the secular world. When I began working at a startup, the fervency and intensity of the meetings—especially when the CEO or board addressed the group—
468.
by _greim_ 12y ago
> doesn't remember the difference between .call and .apply Simply getting the names mixed up and needing to look them up is one thing, but if the unfamiliarity stems from a general unfamiliarity with those methods and their respecti
469.
by _greim_ 12y ago
> Deep down he just doesn't give a crap about starving children in Africa. This is a pretty uncharitable reading of the article. But I agree with the assessment that scientists' main motivation doesn't tend to be altruism
470.
by _greim_ 12y ago
What's the main use case for this? (e.g. Android or iOS apps, or desktop apps, all of the above, or something else?)
471.
by _greim_ 12y ago
People who can build amazing technologies, and people who can explain amazing technologies and make them accessible to a wider audience, are not always the same people. I think you're doing the right thing by creating PRs and helping t
472.
by _greim_ 12y ago
Ben Noordhuis's primary language isn't English, and he was following established PR protocol, so I think he should be given a little bit of leeway.
473.
by _greim_ 12y ago
> We're liberated on the server. I'm liberated on the server in my own app, but not necessarily if I'm publishing something for everyone to use. In that case I'm either forced to feature-detect my way along, or target
474.
by _greim_ 12y ago
I felt like he got thrown under the bus with that whole uproar, and was glad to see him in there.
475.
by _greim_ 12y ago
I suspect there will be a split in the npm ecosystem now, not so much along node/iojs lines but along es5/es6 lines. There's already been lots of discussion about whether module builders should publish es6 code, or should eve
476.
by _greim_ 12y ago
Let's assume that we did in fact solve every aspect of aging except somehow for neural plasticity, and that this did in fact cause social progress to freeze. Would you be okay with killing fifty million people per year, perpetually ,
477.
by _greim_ 12y ago
Lots of innovation in the early days of the internet came from porn. Whatever you may think of porn, I think those innovations have arguably had wider benefits than just the porn industry. Similarly, AI originally built to maximize ad click
478.
by _greim_ 12y ago
> requests coming from JS "need to get a 200" I'm not sure what this is, but it could be some sort of expectation where all responses are expected to get a 200 along with wrappers like this: {"status":&quot
479.
by _greim_ 12y ago
> Async actions as a language-level construct, as opposed to a syntactic abstraction has always been A Bad Idea. Are you saying that the upcoming async/await features of JS are a bad idea? Or maybe I'm not following; can you gi
480.
by _greim_ 12y ago
Inexperienced programmers sometimes can have a dysfunctional, almost worshipful, relationship with complexity. They're entering an industry riddled with complexity, most of it way over their heads, and they're in awe. So when they

More ›