Re:Ask HN: Going full stack with JavaScript, any regrets?
by OtterCoder on Wednesday August 09, 2017 @10:06AM
(#14968940)
I would agree with Xenopticon, as a solo operator, it's been a huge boon. However, I have noticed a bit of a split in the way I code.
The problem is that I tend to write two kinds of JS. On the server I write ES7 and use currying, iteration, and promises as the main paradigm, while on the client side code I tend to write more compatible, imperative, event oriented code.
It's a bit of a bizarre split, and it does impact my productivity. Perhaps I would be better off using Babel, but I tend to avoid adding steps to my toolchain, since I'm the only one who will maintain it.
The problem is that I tend to write two kinds of JS. On the server I write ES7 and use currying, iteration, and promises as the main paradigm, while on the client side code I tend to write more compatible, imperative, event oriented code.
It's a bit of a bizarre split, and it does impact my productivity. Perhaps I would be better off using Babel, but I tend to avoid adding steps to my toolchain, since I'm the only one who will maintain it.