It doesn't have to do with hardware, it's just client-side implementation. I had to write code for multiple key presses before. The browser will normally trigger a keydown and keyup event whenever something is pressed and released. The trick is to keep an array of keyCodes representing current keydowns; during keydowns add to array and during keyups, remove from array.
I'm glad people are toying around with client-side color algorithms and coming up with ways for people to dynamically choose aesthetically nice colors. I worked on this project http://dph.am/projects/ImageEyeDropper/ about a year ago to let people grab colors off an image, find the color range with the highest frequency, and perform some of these color theory functions.
I agree with you here; I usually have underscored included in both the server and browser for my projects. Events seem like it could be useful. Sure Backbone gives you events on models and collections, but I don't always include Backbone models in my node apps.
I feel like this is no different than passwordchart.com but is a bit less configurable. I use 1password myself after using passwordchart for a while. Ever thought about how to handle services that require you to change your password every few months?
I work at Webs and we also recently abandoned scrum for a more kanban approach. While all points in the article resonated with our company, the biggest problem we had was not delivering projects on time.
We focused too much on fitting as much work into a sprint as possible for maximized throughput. The problem with that, especially when you have alot of projects going on at the same time, is that alot of work was being burned across the board, but the needle for each individual projects didn't move forward fast enough and we ended up missing deadlines.
Another problem with scrum is that it turns creative developers into code monkeys, and this in turn lowers code quality. Developers are constantly worried about trying to meet deadlines for the next two weeks rather than taking the time to do things correctly. This ultimately creates technical debts and hurts the team in the end.
(also, if you're a manager and you use the developer points burned in order to rate performance and distribute bonus, then fuck you)
Context absolutely matters! Techcrunch sold the article as Facebook betting too much on HTML5, period. His quote was that at the time 2 years ago, it was a mistake betting too much on HTML5 over native for their mobile application. And it's true, 2 years ago and even now, most phones have a hard time handling Facebook's intensive need in HTML5. It's true, Facebook could have spent more engineering resources improving the HTML5 spec and push it forward, but anyone saying context doesn't matter is just being ignorant.
Regarding his whole point of using css, that upvote image should really be a background in the css file and the innerHTML should be text with a negative indent.
The company I work for was recently acquired. A part of the agreement for the founders, aside from having to stay with the company for 2 years, is they can't have more than 1% ownership of a competing company for that duration and up to a year after employment termination.
sorry if I sound like a markup nazi, but... the pricing table contains tabular with headers and should be treated as such. The columns should be table cells and not divs (all a sudden you no longer have to provide a width on the entire container and it could stretch to fit and used in any location). The header-class container should either be a th, or if you opt for a non-table element, then an actual header tag would be appropriate. Maybe an h6? The bold tag was a poor choice; either <strong> or <em> would be a better option.
As far as reusability goes, the id="pricing-table" should really have been a class.
i'm sure other people have mentioned but it doesn't work in IE9 or below. You should at the very lease support IE9. If you wanna throw away IE8 or below, it would make sense to just use canvas rather than a base64-encoded image.