| Good point. I hadn't thought of it that way actually but that has got to be part of it. For me, I sort of skipped over Ruby. I was too busy with other things to really get into it. So since I had more experience (not a lot, but more) with Python than with Ruby, that is what CoffeeScript seems like to me, instead of Ruby. I always liked Python syntax, its just that I was busy with projects that involved a lot of HTML/CSS/JavaScript/PHP etc. I have spent years and years writing C#/C/C++/JavaScript/PHP code with curly braces etc. To me, the curly braces and some other stuff are noise. Especially when you get into callbacks and have to remember to keep all of your curly braces and parenthesis straight. Its basically stuff that, as demonstrated by CoffeeScript, the compiler can take care of for you, but in JavaScript it just wasn't taken care of. In a similar vein, JavaScript (and any other dynamic language or language with static type inference) demonstrates that type declarations aren't necessary, and that a language/compiler can usually take care of that stuff for you. In a similar vein, C demonstrated (among other things) that managing the stack manually isn't necessary. Ruby syntax to me is significantly more complicated than CoffeeScript and not really as clean (begin end blocks etc). I think that Rails has some important advantages in terms of software engineering, but the performance and syntax of Ruby turns me off a bit. Still, there is probably more good than bad so I might still end up doing some Rails stuff. I don't think its advantageous to write an if statement backwards and I think people who wear black wire-rim glasses when they can easily afford contacts or don't even need lenses are ridiculous. I also have never owned a Mac in my life. I dual boot to Ubuntu/Windows 7. |