News for hackers. Stuff that matters.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by mohi13 on Wednesday January 03, 2018 @01:18AM (#16058930)
I vividly remember starting my first java project a few years back and starting my first node project a year back, personally getting started with node was easily 5x more complicated with so many weird tooling before a first line of code is written.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by iovrthoughtthis on Wednesday January 03, 2018 @11:20AM (#16062244)
Really?

1) Install node.

2) Write script. e.g.

  console.log('hello');

3) Run script:

  > node script.js

  hello
Java

1-10) Download Java *

11) Ensure JAVA_HOME is set right

12) Write java

  public class Hello {
    public static int main(String[] args) {
        System.out.println("hello");
    }
  }

13) Compile java

  > javac Hello.java
14) Run java

  > java Hello
  hello
* Yes, this is obviously facetious.

EDIT: Code formatting thanks to https://news.ycombinator.com/formatdoc

Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by ricardobeat on Wednesday January 03, 2018 @04:30AM (#16059646)
Are you thinking of node or a web project? Node requires zero tooling and is distributed as a single executable ~10-20MB on all platforms + already comes with npm.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by mohi13 on Wednesday January 03, 2018 @07:31AM (#16060430)
Making a web service via nodejs vs a web service using say dropwizad, all these web pack business is pretty complicated.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by ricardobeat on Wednesday January 03, 2018 @04:33PM (#16065398)
I’m still confused. Webpack is a frontend build tool and completely unnecessary for writing a web service.

Also, from the Dropwizard tutorial:

1) configure Maven 2) create a config class 3) write a mapping.yaml for “Jackson” 4) create an application class 5) create a representation class 6) create a resource class 7) register the resource 8) configure maven again (!) for building a .jar 9) finally run it.

With node you literally write 5 lines of code importing the http module and run `node server.js`. I can’t possibly imagine what steps could be more complicated than Dropwizard. I consider webpack overly complex myself, but it’s a completely self-inflicted option and not a standard for nodejs development at all. I’d be curious to know what docs you were trying to follow if you can recall.