1,299 karma · joined August 12, 2012
On the web, many developers are "forced" to write JavaScript when they don't really understand it (which is a massive pet peeve of mine, but that's a rant for another time). These developers tend to try and shoehorn design patterns from their language of choice into JS, or they just don't use any design patterns at all. Either way, it just doesn't work; the code just ends up being horrible.
At least libraries like this allow people to use design patterns that are more familiar to them, which should (hopefully) result in cleaner code.
When I'm writing a new feature, I always try and code it as if I'm going to release it as a standalone library that could easily work for other people regardless of what framework they're using.
Stuart Herbert wrote a lot about this: http://blog.stuartherbert.com/php/php-components/
The only thing holding me back from getting an Air right now is the low screen resolution.
This works if you're in a position of power, but sadly even some senior and lead developers seem to struggle with it.
The reason I say active is because even if you do have a thousand repos, you're surely not maintaining all of them - that would be insane. You would probably have 950 repos which would be better off archived, backed-up, and removed from GitHub.
If your back-end is slow, just cache it and forget about it. Front-end is almost always the bottleneck (the exceptions to this rule being near-real-time dynamic sites like New Relic or GoSquared).
This probably seems a little weird - why wouldn't I want to give it a go? I guess it's because I've been using AngularJS for several months now and learning something as opinionated and complex as Ember is a pretty hefty investment in terms of time and effort.
seivan mentioned ObjectController and ArrayController, which I think are really cool. Does anybody else know of any other features that might whet my appetite and convince me to jump on the Ember train?
If any DevExpress guys/gals are reading this, please consider making a shorter (2-3 min) video showing some tests being written and run.
It's now 404ing, but there was a pretty well-known argument on one of Twitter Bootstrap's GitHub issues[1]. The Bootstrap guys didn't use semicolons, and it caused problems when minifying the code. It's an edge case, I know, but it was a problem.
I never understood the whole anti-semicolon thing anyway. It just seems really hipster to me. Use CoffeeScript, if you don't want semicolons.
[1] https://github.com/twitter/bootstrap/issues/3057BTW this didn't work in Chrome for me, but it did work in Firefox Nightly.
I think the main problem comes from the fact that much of the code still resembles the spaghetti that was written over 10 years ago. Even recent versions have problems with basic input sanitization, which makes injection attacks really easy. Social engineering is also a massive problem: if you can phish an admin login, you can essentially take over the entire web server because the admin panel is just too powerful.
The thing is, and please forgive me for dismissing your achievement like this, it doesn't make you a good programmer. Programmers solve problems like this on a daily basis. You've definitely proven that you have the right mindset and determination to be a good programmer, but at the same time this sort of egotistical, superior attitude is the trait of a bad programmer. Nobody likes working with people like that.
I never wanted to be "that" guy on HN who puts down other peoples' posts, but I think the whole smugness of this rubbed me up the wrong way. Please, carry on solving real-world problems. Just, show a little modesty and humiliation.
(function( window, undefined ) {
// ...
})( window );This graphic sums up pretty nicely what "HTML5" actually encompasses: http://upload.wikimedia.org/wikipedia/commons/f/f7/HTML5-API...
I probably have a disorder. I should get help.
I guess it depends on the culture within your team, how much you all care about your test suites.