48 karma · joined August 30, 2010
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.
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.
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.
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.
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 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.
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.
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.
Transparent enough?