4 ms·

If you're installing a compiler on your production server, you're doing it wrong.

• falcolas 10y ago
  And yet we do that every time we install the JVM (and Ruby, and Python, and...)
  • twic 10y ago
    That's nothing - every time you serve some JavaScript, you're relying on a compiler being installed on your users' machines!
  • deepsun 10y ago
    No, when you install JVM (you probably meant JRE) on the server -- there's no `javac` (compiler) installed, only `java` -- JVM. I never needed `javac` on production server.
    • falcolas 10y ago
      The JIT is a realtime compiler, so yes, there's still a compiler when you put the JVM on a machine (whatever form you use). Of course, I know of a lot of developers who just put the whole JDK in a Docker image to save on the complexity of having to manage two different installs or containers. > I never needed `javac` on production server. Good; that's how it should be; but not how it always is.
      • mi100hael 10y ago
        JIT is part of a platform's runtime environment, not part of its build environment. Since you appear to be a super-pedant, I'll revise my initial statement to: > If you're installing any tooling or programs on a production server or opening ports other than those strictly necessary for running your production application (as a pre-built binary or package whenever applicable) conforming to industry standards for that application/server environment, you're doing it wrong.