Lifetime member. It’s a great community and really great having a network of people to meetup with while travelling. There’s often impromptu meetups organized on there in the popular nomad destinations like Bali or Chiang Mai. I’ve met a bunch of great people on their over the last two years.
Several centuries of linguistic evolution would disagree. Those have always been neutral, though there has been usage of singular "they" dating back to Shakespearean-era.
It is somewhat widely accepted that he/him/his is only gender-neutral in situations where the gender is ambiguous though. For example, in writing documentation.
Personally, I think it sounds weird and prefer they/one.
A signed CLA may seem silly, but there were changes in code comments. That makes code ownership ambiguous, and the law doesn't tend to play nice with ambiguity.
The contributor also had not signed a CLA, and the commit message did not follow the guidelines.
Ben should have been more explicit in his initial post about his reason for denying the commit. Isaac shouldn't have merged the pull, which violated the guidelines. The community shouldn't have raised their pitchforks without first seeking an explanation.
Everyone involved could use a dose of professionalism.
It's difficult to escape that sort of situation, but it doesn't get easier. It gets harder, and faster-paced. And that's a good thing.
Adversity is a force that not only pushes us back when we feel fear, but also pushes us forward when we feel determination. How much you want a thing will determine which way you move.
That's what semantic versioning is for. Node modules should continue to move forward, and reinvent themselves to improve how we write our apps. Otherwise it'll just turn into another PHP.
Have a look at node.native. It's just libuv and c++11, which behaves pretty much the same as node. But much lighter, and with no Javascript engine tacked on. Obviously not nearly as stable and supported, but it's an example of how c++11 can work very similarly.
Node is not really tied to Joyent. Actually, a good amount of the core team is at StrongLoop.
Joyent has basically got it as far as they needed it to get for their own uses. Now they are just sitting on it and keeping it stable while letting userland modules cover future expansion.
It was easier until we discovered even cleaner ways, and most of the Javascript community began to adopt them. But node chose to stick to the "old" ways. (Not really old, but not as shiny and new as the alternatives)
I feel like promises don't need to be part of core though. It's easy enough to wrap the standard library in userland and just have other things depend on the wrappers.
I couldn't even afford to get INTO university. By 18, I had to pay $1000/month rent or get kicked out. My family had NO money saved to help with college. I wasn't eligible for any scholarships I could find. The city I was in paid minimum wage for EVERYTHING, even skilled work. I worked $8/hour doing web development.
I tried saving up enough to even just move away. 3 years later, and not a penny ahead, I just threw caution to the wind and plunged myself deep into debt to get the hell out of there.
A year later, I've made more than I did in those 3 years put together. I'm still in debt, but I'll comfortably be out in 6-8 months. At this point, university would only be of value to me if I felt like immigrating to the US.
The point is, if your situation sucks, change it. If school doesn't seem viable, skip it. Find a workaround. The point is not acquire a piece of paper, the point is to prove your worth.
I'm a Javascript user. The list of things I'd change is enormous. A few of the biggest things though, is making better object looping; it's annoying having to check each property to see if it's on the object itself or it's prototype. It'd also be nice to have a build in extend/include system, rather than having all these different custom ones people use. Put jQuery and Underscore on the same page and you have two different implementations of object extension. Seems like kind of a waste of code.
Yes, but NaCl provides direct access to GPU interface libraries. You can code for OpenGL directly, rather than running your graphics code through several layers of abstraction, slowing it down exponentially along the way.
There is, to some extent; hardware acceleration for canvas. But I don't expect that to be at all comparable to native OpenGL for awhile yet. JS has certainly had some significant advances in speed over the last few years, but there's only so much optimization you can do. It's still running in a VM, so there will always be that overhead.
Another important thing to consider is that the native API will always have to exist before a Javascript abstraction can. Many triple-a titles will use brand new GPU features to sell the newest line of graphics cards. That won't work if they are making a browser game and the required interface to do those things doesn't exist yet. Javascript will always be chasing the tail of native.
The moment a programmer thinks they know the ultimate solution to a problem is the moment they understand the problem the least.
No, templating is not perfect. Nothing a programmer does is perfect. Our job, as programmers, is to make stuff suck less. We break stuff until it works. We squash bugs until we can't find any more. That doesn't mean what we've built is perfect. It means what we've built is the best we could build with our current understanding of the problem.
I don't think of spaghetti code as the presence of logic in presentation code, I think of it as a lack of separation of what SHOULD logically be abstracted. I find the code it labels evolves over time as the common abstraction level of things increases and we move closer and closer to fully isolating concerns.
Emscripten is not a viable alternative. The Javascript it generates is too slow for performance intensive things, which is the whole point of NaCl. Flash is too unstable.
It's no coincidence that most of the companies on that list sell mediocre software for way more than it's worth. They rob us with their high prices, yet they throw a tantrum when we rob them back. Make your software suck less and maybe I'll consider paying for it.