4 ms·

In the spirit of Steve Ballmer, JavaScript, JavaScript, JavaScript, JavaScript (voice growing hoarse and weak)

• PaulHoule 4y ago
  How many people really run a JavaScript web server? Most of us who are doing front end work are using a lot of node.is code as part of the build process but I think most of us are using some other platform for the server. It is not so fashionable to talk about but everywhere I have worked since 2007 or so decade (consumer-oriented startups, enterprise-oriented startups, more staid organizations) has used either the JVM or .NET as a back end.
  • byoung2 4y ago
    I am a nodejs engineer so 100% of the last 5 companies I've worked for used node as a server.
  • yrgulation 4y ago
    I never worker at a company or served a client or heard of any in my circles that use .net or jvm for their backend. As of recently most use nodejs and thus js.
  • darepublic 4y ago
    JS or more so TS backend ecosystem is improving. Tools to generate type definitions from db schema and vice versa. Mature toolchain is -- specify db schema and get proper swagger doc and type contracts auto-generated for you.
  • BrandoElFollito 4y ago
    From my limited experience, I wild day that this is more for modern and new projects that embrace devops and other fashionable trends (no irony). They can start from scratch and give some freedom. I tried once, with the idea of "one code base" but it ended up being two code bases without strong links (I was certainly doing it wrong) Enterprise software, au least in my industry (large, well established high tech) is dreadful. It is so complex that everyone is scared of prodding it to much and obviously you wild not change the core web server. It is some tomcat anyway. I am not a pro dev but work in information security (and develop for fun at home) but even to the untrained eye this does not look good.