I couldn't agree more. I was thinking the same thing while reading it.

I was thinking the same thing. It has nothing to do with callbacks.

> fully resolving circular dependencies is equivalent to solving the halting problem, IIRC.

I don't think so. Any good dependency injection framework would detect this kind of circular dependency.

Of logger and DB, certainly. The coupling introduced via locks is harder to detect. But most importantly, circular dependency between components might be OK in a path-dependent way - that's what I meant by fully resolving it.

Just analyzing the dependency graph of injected components is indeed just a topological sort.

this article boils down to the comments.

oh god, why ?

I don't like surveys, but I can tell you this. ES6 all the way down. ES7 async stuff looks great. facebook flow looks promising

take a look at 6to5 project

awesome, thx for the pointers!

you can always solve any problem throwing money at it. I guess the main point is running the same thing with 30% less servers, not more.

You can't actually solve a lot of problems by throwing money at them. Ensuring that scaling your core application to arbitrary traffic sizes is in the class of money-solvable problems isn't trivial and should guide your architectural decisions from day 1.

Yes, you'll probably end up doing significant rewrites if you do actually win the lottery and get big, but it's nice to know that you're not going to top out at some arbitrary size and have to start turning customers away while you do those rewrites.

try compiling a super simple sass file multiple times. The time it takes varies so much. Ruby's performance is not predictable.

The point here is why the same algorithm would take 0.3 sec to run and the next time it would take 1 sec. After seen that I never coded Ruby again.

do you know assembly ? and what about raw binary ?

I never wanted to learn the details of how a computer really work as, but I spend a single week learning C, just to learn the basic concepts like pointers. It really helped me understand better other languages. Besides, It would take you many years for you to master it, and the kind of jobs you would get with it would f* damn boring. Don't waste more than a week on it :)

I'm learning Rust at the moment, I feel I can express my ideas better with it versus go. But as a hobby. for fun.

I've being coding exclusively in JS for 3 years. And just now I feel comfortable with it.

There is so much going on with it. I bet you heard about OOP, but what about functional programing. And functional reactive programing ?

There are so many libraries and framework in JS. It just crazy. There is angular vs ember. And what about react or famo.us ? And there is nodejs, and things like npm, gulp, browserify.

To learn javascript, the language is one thing. But all its tools is another.

The reality is this, the more languages you learn, the easier it is to learn a next one. Today I know over 10 languages, but I master only one. And that is what matters, the one you master.

But what I things is super important for a programmer this days is a basic knowledge of shell and git. IMO

This is a great advice if you want to be a generalist. I'm a specialist.

Take a look in this article, it illustrates pretty well the differences. http://www.nczonline.net/blog/2014/07/15/generalists-and-spe...