Thoughts on using jade with Meteor?

Do any of you guys still using mquandalle:jade?

Are some of you using it together with coffeescript and stylus?

Or have all moved on to React, JSX, ES6 and Less in 2016?

To test the practical usability of this wondefully noiseless syntax trio (jade, coffeescript and stylus) with Meteor, I have been trying to rewrite the simplest possible example, the leaderboard example, using these three packages together with the latest 1.4 version of Meteor and the Meteor guide app structure with import/export declarations.

I keep running into problems published in other meteor forums threads that received no answer:

Debugging these problems is particularly difficult because:

  • I am still a newb learning this stack

  • they seem to be build issues (not sure though)

  • the Webstorm Meteor debugger does not work properly with CoffeeScript (not stopping on breakpoints) and the numerous open issues filed concerning these bugs seem to receive zero attention from Webstorm support (not enough votes to be addressed I guess)

  • the VSCode node debugger and the VSCode chrome debugger, in addition to be very hard to configure, are not made to work together to debug Meteor code and they both suffer from the same kind of CoffeeScript+Meteor source map leveraging bugs than Webstorm, making breakpoints in CoffeeScript code unusables

  • there is no way AFAIK in neither of them (Webstorm or VSCode) to put breakpoints in jade templating code

  • the jade template engine does not generate AFAIK any source maps that could be exploited by a debugger.

My idea was to first try with raw Blaze and then try raw Blaze + ViewModel and then Blaze + Riot.js to better understand the pros and cons of these three apparently concise and simple alternative for UI components.

So what is the deal? I am trying near the end of 2015 a still-born obsolete stack that its adopters of 2015 have already abandonned?

Thank you very much in advance for any experienced meteorite insight on these puzzling questions.