6 ms·

Like the Stack Overflow survey, this one does not distinguish server-side/client-side JavaScript, making it look far more popular than it actually is when consi

Like the Stack Overflow survey, this one does not distinguish server-side/client-side JavaScript, making it look far more popular than it actually is when considering the data in context of server-side technologies. If 100% of the servers were running PHP, the results would likely be 50% PHP, 50% JavaScript. These survey writers need to modify their question, or add another one specifically requesting server-side tech so JS can be accurately compared with server-side only languages.

whb07 8y ago
You’re forgetting the C and C++ for the OS and other binaries. Throw in some python to bring this all together and some Go for a bit of spice. I get your point, but they probably asked “what language do you develop with”.
mawburn 8y ago
Do you think a lot of people are running JS in a container for frontend? I wouldn't consider a webserver container a "JS container", even it were mostly serving a React/Vue/Angular app. By the way it's worded, it sounds like the question is specifically talking about NodeJS.
- java_script 8y ago
  > Do you think a lot of people are running JS in a container for frontend? Hold my beer. --Frontend developers
  - albemuth 8y ago
    If the rest of a web app is running on containers, what's the downside to having the test/build process for the frontend in a container as well?
    - steve_adams_86 8y ago
      I like using containers as a reliable build context. I think it makes tons of sense. Once the container's done building, throw it out, take what it built, and serve it. I'd personally do this separately from the rest of the web app if possible, though. I keep frontends in their own repository.
- felixmc 8y ago
  actually! at my old job there was a project where the frontend webpack build was running in a docker container..
  - mawburn 8y ago
    Yeah, I guess when you think about it that way it makes sense. I think I might have assumed this was for production and not build environments.

whb07 8y ago

You’re forgetting the C and C++ for the OS and other binaries. Throw in some python to bring this all together and some Go for a bit of spice. I get your point, but they probably asked “what language do you develop with”.

mawburn 8y ago

Do you think a lot of people are running JS in a container for frontend? I wouldn't consider a webserver container a "JS container", even it were mostly serving a React/Vue/Angular app. By the way it's worded, it sounds like the question is specifically talking about NodeJS.

java_script 8y ago
> Do you think a lot of people are running JS in a container for frontend? Hold my beer. --Frontend developers
- albemuth 8y ago
  If the rest of a web app is running on containers, what's the downside to having the test/build process for the frontend in a container as well?
  - steve_adams_86 8y ago
    I like using containers as a reliable build context. I think it makes tons of sense. Once the container's done building, throw it out, take what it built, and serve it. I'd personally do this separately from the rest of the web app if possible, though. I keep frontends in their own repository.
felixmc 8y ago
actually! at my old job there was a project where the frontend webpack build was running in a docker container..
- mawburn 8y ago
  Yeah, I guess when you think about it that way it makes sense. I think I might have assumed this was for production and not build environments.