3 ms·

I say... can you show me the light? I love django...it's no bullshit and no frills yet has everything I need. Node.... is hellish. Callbacks haunt me. New tools

• manyxcxi 11y ago
  Callbacks, arrow code, error handling, and the daily shifting sands of the JS landscape really pained me when I was first getting my bearings with node but I was determined to build a continuous deployment server with it until I was happy with my feature set and comfortable with node. I was going to be building the system no matter what, but I figured it was the best time to learn node and that the async-ness of the language would be a huge benefit (it mostly was). Eventually, I found my rhythm and I now really like node (it's been three years). It has a lot to do with picking packages that are stable, or at least have responsible leadership, and a modicum of documentation. You get used to minimizing arrow code, and you learn to pass errors until you run into that one obscure darned library that throws them (or leaks them) and you have to write a bunch of stuff to seal it up. The deployment system runs great, and I really like writing tiny to medium sized worker applications, parsers, scrapers, and web services with node. I find running node in production to be a bit of a chore compared to Python, PHP, and Java- but like all things JS it's evolving and I'm still learning.