@hipkiss91 I would try to stick to separated libraries who do what I want instead of a whole framework, since libs are easier to replace than an opinionated framework, one might argue that frameworks are maintained as a whole .... religious wars and stuff ....

but I'm not a real node programmer , since I'm polyglot it's just one of many languages to me, so I guess a real node coder knows much more than me. I always try to be as modular and close to the original language as possible so I don't have to rely on blackbox logic but really understand what's going on.

But this is just my opinion :)

@chilimatic Cheers! It's just a huge field (frameworks & langs such as type/coffee/js etc) and I'm trying to figure out what I actually need. So far I have been just running with pure JS (ES5 - In the process of learning ES6) but I'm wondering if there is a better way.
Thinking about it - all these languages/methods just get compiles into ES5 anyway, so I guess I don't really need them. However I do need something to help with managing the code - aggregator/compiler/obfuscator/minifier - Hence why I'm leaning more towards rollup because of it's tree shaking ability. (This will REALLY help) I'm just not sure about the rest. And I agree with you I don't like the blackbox magic either.

hmmm i see, about the "transpiled"-languages in the end they will compiled into an es5 solution so they work or you just don't care about browser compatibility g which is my favourite approach.

TS/js++ are strongly typed and afaik with TS you have to define a lot of interfaces and you IDE (static code analysis) already warns you if you use something wrong.

If you like use dynamic code I would stick to ES6 + Flow this is one of the classic battles between the "dynamic" and the "typed" fractions. For me it's an dialect that's all and I don't know if those languages really improve the performance (to me they mainly make sense if you got multiple developers who work on the frontend application logic so you can get an "typescript compiler error" before you get a runtime error in the browser VM)

But once again, taste is it easier to write small dynamic modules that need a deeper knowledge of the language or is the code base so big that you can't expect everyone to understand what's happening and you want them to be able to always deduce what's going in what's coming out

-> classic example would be C void* pointers VS C++ templates one thing is harder to read and the coder has to know what he does but it's simpler and smaller the other thing bloats the code but you exactly know what's happening .... again religious wars gg*

but as I mentioned I'm not a specialist in Node or JS those are just generalizations on my side :)