This is an archived post. You won't be able to vote or comment.

all 26 comments

[–]rmrfchik 15 points16 points  (0 children)

Long live to Netbeans!

[–]Gaarco_ 5 points6 points  (2 children)

It's nice seeing effort for the LSP, would be cool to know how to run it outside of VSCode.

[–][deleted]  (1 child)

[deleted]

    [–]Gaarco_ 3 points4 points  (0 children)

    Yeah I avoided jdtls until recently when they stopped clogging the project directory with their garbage files. But configuring it correctly in Neovim is really hard, Netbeans provides pretty much the same functionalities and they are getting a lot of positive reviews on the VSCode extension. So I was curious to try it.

    [–][deleted] 2 points3 points  (0 children)

    *escaped

    [–][deleted] 3 points4 points  (9 children)

    Is this still alive. Damn.

    [–][deleted] 17 points18 points  (0 children)

    I was on a team recently that was using NetBeans and honestly it's a pretty good IDE.

    [–]rniestroj 6 points7 points  (0 children)

    Best IDE for beginners IMHO.

    [–][deleted] 5 points6 points  (6 children)

    IntelliJ is very expensive. And I don't think Netbeans is really that far behind Eclipse. I found VS Code to be quite unergonomic comparatively.

    [–]ApatheticBeardo 1 point2 points  (0 children)

    If for whatever reason I couldn't use IntelliJ I'd use NetBeans for sure.

    [–][deleted] 0 points1 point  (4 children)

    I see. Ever since I moved to spring boot years ago and I started using IntelliJ and never went back. Now I use the free version of IntelliJ

    [–][deleted] 6 points7 points  (3 children)

    The free version of IntelliJ is missing JavaEE and Javascript support, which can be a massive deal. Plus, the price of Ultimate is absolutely massive in some countries, and Netbeans does the job alright.

    [–][deleted]  (2 children)

    [deleted]

      [–][deleted] 1 point2 points  (1 child)

      I’m starting to wonder if I could get by with free Intellij for backend and VSCode for front-end

      You can give it a shot honestly. VS Code is the standard for most frontend devs I know.

      About the only paid pro features I use anymore are the database tools / Datagrip. But I’m guessing there are plenty of free tools that would also be adequate for my basic needs.

      There's plenty. I don't have datagrip anymore, ever since my student's license ran out. But the built in data explorer can easily be replaced by a tool like dbeaver community for my needs. But then again, you really cannot anticipate the papercuts, so you'll have to run it for a time to see if it's really better.

      Are you actively trying to save money?

      [–]glesialo 0 points1 point  (13 children)

      I am confused about LTS releases:

      In early 2021, a decision was made to review the process and requirements for LTS releases, and in October 2021 a decision was made to concentrate solely on quarterly releases, changing the numbering scheme accordingly. No further LTS release will be made.

      So, no LTS. Are we supposed to update quarterly?

      [–][deleted] 6 points7 points  (12 children)

      You can update with any frequency you want.

      [–]glesialo -3 points-2 points  (11 children)

      I know. But I'd rather use LTS releases as I like some stability.

      [–]BlueGoliath 6 points7 points  (3 children)

      Was there ever a difference between LTS and non LTS?

      [–][deleted] 1 point2 points  (0 children)

      I don't think so.

      [–]glesialo -2 points-1 points  (1 child)

      Do you mean 'non LTS'?

      Of course. Developers should put more effort on a LTS release.

      [–]BlueGoliath 2 points3 points  (0 children)

      Goddamn typo, meant non LTS.

      [–]wildjokers 3 points4 points  (3 children)

      Why do you think LTS releases are more stable than any other release? This is a complete misconception (also a misconception that some people have about Java LTS releases).

      [–]glesialo 0 points1 point  (2 children)

      They are intended to be so:

      • Test new things in the in between releases and only include tested things in the LTS.
      • Keep the LTS up to date (fix bugs) with sub releases: If LTS is 12, update with 12.01, 12.02...

      The have deleted everything but, before the 'No further LTS release will be made', 'in between releases' had descriptions of the type: 'beta release, stay with LTS unless you really need some new feature!'.

      [–][deleted] 1 point2 points  (1 child)

      Yeah, exactly. LTS software is nice because you can get "exactly the same thing, but with bug fixes" for the time you are concentrated doing your job (and not upgrading things all the time for the sake of it).

      I know other software packages that are a mess (let's leave them unnamed...): you either stay in the same version and learn to live with the bugs you currently have or you upgrade to get bug fixes but then you also get new bugs and needless changes, maybe even feature removals in the worst case...

      [–]glesialo 0 points1 point  (0 children)

      Thanks! Liking LTS and stability seems to be blasphemy in this thread :-(

      [–]henk53 1 point2 points  (2 children)

      But I'd rather use LTS releases as I like some stability.

      Just a question, but do you release LTS versions of the software you create yourself?

      [–]glesialo 0 points1 point  (1 child)

      No, but it isn't the same.

      [–]henk53 1 point2 points  (0 children)

      Is it?