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.
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.
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.
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?
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.
I have for about a year now done all my work out of Dropbox (via a symlink from ~/src) it works great for multiple machines and has added advantages, eg. I never worry about deleting files that aren't staged anymore, as I can undo the delete from Dropbox’s website.
Git is for long-term version control, working out of Dropbox is like having a script running that stashes and unstashes every change you make so that its in the git-reflog.