4 ms·

I think the first JavaScript book I bought, circa 1998(?) briefly mentioned server-side JavaScript, and then until Node came out, I never saw it again. It's fai

• dboreham 10mo ago
  JS on the server seemed to me to be a solution looking for a problem. We already had plenty of arguably adequate server side languages. JS was the weird language you were forced to code in for the browser so why on earth would you want to use it elsewhere? Well I suppose the answer was "because there's a zillion people who know how to use it". But that wasn't true until it was.
  • petesergeant 10mo ago
    No, the answer was that Node.js will run circles around Apache, because Apache was built before async was discovered[0]... 0: https://www.youtube.com/watch?v=bzkRVzciAZg https://www.youtube.com/watch?v=bzkRVzciAZg
    • cr125rider 10mo ago
      It’s good to know the differences between libuv based event loops, threads, and processes. I think your comment simplifies that too much.
      • petesergeant 10mo ago
        You might enjoy the linked video
  • shadowgovt 10mo ago
    > why on earth would you want to use it elsewhere Mostly because I don't want to reimplement my data structures (and data structure manipulation functions) just because they're being operated on in another machine. I want to represent those values and relationships once and be able to manipulate state on both the client and the server with the same operations. My projects end up having one `src` directory with `client`, `server`, `shared` subdirectories.