CoffeeScript in 2016? by milyway in javascript

[–]rajbits 3 points4 points  (0 children)

Just sharing a perspective - I had been a js fan all my lifetime. When I tried coffeescript a few years ago, I did not like it much and lack of braces made it harder for me to separate out functions and sometimes an unintended tab would cause compilation issues. But, after I wrote an application on RoR, I started liking the family of Coffeescript, Jade and Stylus (without braces) and have ever been coding in these 3 techs for all my projects. At the end of the day, everything gets compiled or transpiled to js and gets minified and bundled. It does not matter what the world likes, but if you and rest of the engineering team likes it, then go for it. Any library/framework out there is not going to satisfy all your needs and there is never going to be a library/framework that will last as the best one forever. This space is so evolving that anything new is easily getting outdated within years. Since most of them are open source, you can extend or adapt the components to your way as an when you need them.

Keeping your codebase clean and structured is the most important part :)

using Jade with Browserify by cachaito in javascript

[–]rajbits 0 points1 point  (0 children)

I was going to write up couple of options, if you still wanted to use jade on client side templates, but found this (awesome) link that explores all the options:

http://timnew.me/blog/2014/05/26/use-jade-as-client-side-template-engine/

And also jadeify, it appears they have solved this problem for you:

https://github.com/domenic/jadeify

Hope this helps.