yes, he has. as has substack. basically everything.
but part of the reason they are so prolific is that they focus on very small, single use modules that do one thing well. So they have hundreds of repos, but many of them are 10 - 15 lines of code.
That may be one reason, but the guy's responsible for Express, Jade, Mocha, Commander, and many others. I honestly thought visionmedia was a company until a few months ago.
The node-inspired `http-browserify` is my favorite; really nice, sane syntax for doing ajax requests that you can mix with client-side streams and transforms to do really advanced things with code that is clear and readable. Of course you have to use browserify to use it, but it's worth looking into.
Everyone who says using tables is wrong, is wrong. The only issue as far as I'm concerned is it is tedious to style tables, and you have to have <table><tr><td> all the time which is tedious to work with. All the other arguments are perfectionism. Even the accessibility argument is nonsense nowadays, it amazes me people are claiming screen-readers haven't advanced in 10 years. TEN YEARS AGO screen readers sucked with tables.
The US is way more into dance music now than they were 10 or 20 years ago when Europe etc. were quite into it. Daft Punk are predominantly known for dance music, so this album got more interest from US music publications etc. Of course, this album is the least “dancey” they’ve made, and heh, no doubt that helped!
I'd consider Windows more readily, but you are a bit screwed if you do decide you want to dip in the Open Source pool. You can dip there, but it's harder and less well supported, and some things simply don't work. So you are tying yourself to Windows, and often, Microsoft tools. Fine if you're sure it'll work, but I would feel like I was gambling.
We're building a web-based saas on a Microsoft stack. We use coffeescript, sass, compass in our development environment and it works really well. There are open source libraries for doing REST, unit testing, performance testing and they work pretty well. Node.js and npm run on Windows. Mercurial always has and git now works as well.
It does sound a bit as if you were using a node.js stack on top of a Windows operating system, which I wouldn't exactly call a Microsoft stack. In which case there is really just the question of what you know better, linux ecosystem or Microsoft...
No, we're are using a Microsoft stack - ASP.NET MVC and Sql Server.
We're not actually using Node.js in that sense. I was just pointing out that it works well (we use Node and npm to run the coffeescript compiler - that's it)
Sorry to be blunt, but it's clear you have never had to design or support a user-facing product. Anyone who has done either of these things will disagree with your base assumptions, ie. that users care about understanding their software, that they read warning texts, and that they don't mindlessly flip switches when trying to achieve unrelated goals.
And it's fabulous, I switched from Sublime Text 2 last week and have no interest in Sublime Text 3 anymore. I was disturbed that Sublime Text 2 had several irritating bugs that I encountered most days and yet all dev was going into the next version that would require a new license. Also I am a sucker for OS X native feel and ST2 clearly had effort put in there, but still fell short.
I use TM2 regularly and really like it for these reasons. My only real gripe, and why I might switch to ST3 at some point, is auto complete. TM technically has code completion[1], but I've never found it particularly useful compared to the popup style that ST and XCode use.
Indeed, never offer features that you don't intend to fully support. People hate change, but they hate you more if you take away something they use, especially if they feel they paid for it.
Recently I wrote a less overwhelming pre-compiler that allows you type HTML inline with your Javascript, may be worth a look: http://mxcl.github.io/bs BullScript’s goal is just to make writing JS a little nicer, but not to be some whole new language.
Somewhat silly question... why not write BSC in JS? I mean, this seems like something that would be a natural fit in a NodeJS environment, and tying into NPM similar to CoffeeScript, Less etc.
I don't mean to come across as an ass, just curious. Though, I do think what you are doing could be a natural extension to CoffeeScript itself.
Also, I would suggest having an htmlEncode(variable) by default, I know that htmlEncode isn't a built-in JS method, but you should want to escape html entities.
Yes with hindsight I wish I had written it in JS, but writing the BS compiler was something I wanted to get done fast, and I'm more proficient with Ruby.
BS has the #x{foo} syntax for htmlEncoding, or did you mean that should just be the default?
