4 ms·

JS still puts the bread on my table. Not the perfect solution, but it is in high demand. FE: I'm surprised the OP didn't mention Elm [1]. Elm is not ( maybe y

JS still puts the bread on my table. Not the perfect solution, but it is in high demand. FE: I'm surprised the OP didn't mention Elm [1]. Elm is not ( maybe yet ) popular enough for production uses ( at least outside of Silicon Valley ) and the better alternatives ( TypeScript, Flow ) are actually JS with sugar. Frameworks BE: NodeJS is much more than JavaScript itself. It is quite easy and cost-effective. Because of NodeJS we have "full-stack developers" again ( I'm coming from Perl CGI Scripts - when everyone was "full-stack" back then ). Go is super strict about it's formatting, so you practically have ES/JSLint in the compiler itself. I don't see a big problem in this sense. > I won’t regurgitate the web only to say that a simple Google search will reveal JavaScript’s many internal inconsistencies and traps that literally make JavaScript a “digital minefield.” Sorry, but I know the JS traps and I'm pretty well paid, because of that. I am not in psychosis and I love what 1: http://elm-lang.org/examples/hello-html http://elm-lang.org/examples/hello-html

k__ 10y ago
Same here. - Servers? Node.js - Web apps? Browsers - Cross-platform desktop apps? Electron - Cross-platform mobile apps? React-Native Will it deliver the best possible solutions (performance, size, etc.)? Probably not. Will it deliver economically acceptable solutions? I think so. Most of my customers don't even care which language I use, they just want their app idea implemented somehow. And many react positively when I say JavaScript, because they know a bunch of people developing in it, so when I get hit by a meteor, they don't have to find one of those rare Qt C++ gurus.
- swah 10y ago
  Is your motivation for writing backend code in Node.js code sharing or just avoiding the mental burden of changing languages?
  - k__ 10y ago
    A bit of both. I seldom write my own libraries I could share, but I use many 3rd party libraries on client and server. So using the same language AND the same libraries helps a lot to minimise "the mental burden" of developing in general.

k__ 10y ago

Same here. - Servers? Node.js - Web apps? Browsers - Cross-platform desktop apps? Electron - Cross-platform mobile apps? React-Native Will it deliver the best possible solutions (performance, size, etc.)? Probably not. Will it deliver economically acceptable solutions? I think so. Most of my customers don't even care which language I use, they just want their app idea implemented somehow. And many react positively when I say JavaScript, because they know a bunch of people developing in it, so when I get hit by a meteor, they don't have to find one of those rare Qt C++ gurus.

swah 10y ago
Is your motivation for writing backend code in Node.js code sharing or just avoiding the mental burden of changing languages?
- k__ 10y ago
  A bit of both. I seldom write my own libraries I could share, but I use many 3rd party libraries on client and server. So using the same language AND the same libraries helps a lot to minimise "the mental burden" of developing in general.