For JavaScript or CSS single-file projects it's actually quite simpler to wget the one file from the Raw URL (or copy-paste the contents into a new buffer in your editor), than to clone/download the archive and then move the file from the downloaded directory and then clean up the other downloaded files.
Co-located teams are better off with sticky notes and whiteboards as long as the client is also in the same room :)
Either way, I work from South America for clients in the US, so I like having these tools around. Specially when they innovate in any way. That means better tooling for communicating with my clients, which is the #1 problem of distributed teams :)
Chat hooks! I want hipchat (or campfire, w/e) to say "Joe commented on…" etc. Specially new items, comments and status changes.
Then I could configure github to notify sprintly and sprintly to notify the chat, instead of getting all the pushes in the chat, which is too noisy IMO.
In this regard I love what Chile is doing with Startup Chile. You guys seriously need something like that, where you just grant visas to smart founders.
I still wouldn't like to live in the US, but I totally support that you become more open :)
When was it that you used it? I haven't used it lately, and when I did I felt the same as you, but for what I've seen Dojo is no longer the "kitchen sink" it used to be. It's small, VERY modular, and has a lot of utilities and interesting things.
Not that jQuery doesn't have any of these. But jQuery was thought out as a DOM manipulation library and then people started sticking a ton of things on top of it.
Dojo is thought out as a modular toolkit, where DOM manipulation is just one of the libraries it includes.
The specific point is that the evented model is not designed as a "one size fits all" solution. It's great for certain scenarios, not very good for certain others.
Basically, the original blog post tries to get to this, remarking on node.js is sold as if it was the silver bullet of web servers, that will scale to anything for anything you .
Of course, you can try to adapt most problems into something that would work in an evented model, but you have to know VERY WELL what you're doing.
IMO the solution is simple: polyglotism. Have parts of your app in node. Other parts in python. Others in ruby. Whatever works best for each specific small part :)
Node is not useless, but it's definitely not my choice to program everything and anything. Same thing with, for example, Rails :)