3 ms·
There's a lot of reasons to not use abstraction languages like CoffeeScript and Haml, but the reasons the author cites are weak. > First, compiler languages re
by rubiquity 13y ago
There's a lot of reasons to not use abstraction languages like CoffeeScript and Haml, but the reasons the author cites are weak.
> First, compiler languages require some learning. HAML is awesome, but the number of people who know how to write it is small. That means every time we need to make a change to Scoutzie, not everyone can get tasked with updates. Same goes for Coffee.
I'm sorry to hear that you don't have a culture of learning and teaching other people at your company new technologies.
> Second, both languages make debugging a harder process. When something breaks and I try to fix it, I can't always tell right away whether it's due to poorly written logic, or simply improperly written code.
Both CoffeeScript and Haml have syntax errors so you can tell whether your error is syntax related or not.
> Lastly, there are just too many dependencies.
If you're using Rails, which it sounds like you are, the coffee-rails gem is in your Gemfile by default. I've never had any issues with the coffee-rails or Haml gems in 3 years of using them. I hardly notice that they are even there.
- winslow 13y agoTo expand on your second point. Debugging coffeescript has become pretty easy with Chrome and Firefox supporting source maps. With livereload and coffee's autocompile (watch & compile flags) I basically skip the build steps. For me, coffeescript was similar in syntax to Python (our main language at work) and it makes everything much cleaner compared to JS for big projects.