containers VS Apache NetBeans

eclipse-temurin:11 https://hub.docker.com/_/eclipse-temurin

Then you build the container. That will download that container that already has linux with java on it, like this one: https://hub.docker.com/_/eclipse-temurin

You can shrink the docker image greatly by starting with an Alpine based one like this https://hub.docker.com/_/eclipse-temurin

> Just imagine the vast number of poorly cached CI jobs pulling gigabytes from Docker hub on every commit, coupled with naive aproaches to CI/CD when doing microservices, prod/dev/test deployments, etc.

I hit the rate limits that others talk of in the comments, which motivated me to use Nexus for both proxying and storing my own container images.

So far, it's been pretty good, I actually wrote about the process on my blog, "Moving from GitLab Registry to Sonatype Nexus": https://blog.kronis.dev/tutorials/moving-from-gitlab-registr...

Another thing that I tried, however, was to only rely upon Docker Hub for the base images that I want (Ubuntu in my case) and then build everything I need on top of that, doing things like installing Java/Node/Python/Ruby/... manually, adding utilities I want across all of the images etc.

Once again, I wrote about it on my blog, "Using Ubuntu as the base for all of my containers": https://blog.kronis.dev/articles/using-ubuntu-as-the-base-fo...

That approach is absolutely more work, but also is something that's underexplored and works really nicely for me. Now I mostly rely on the OS package manager repositories (or mirrors of those), put less load on Docker Hub, don't risk running into its rate limits and also have common base layers across most of the images that I build, which in practice means less data actually needing to be downloaded to any of the servers where I want to utilize my images.

Of course, the downside is that getting something like PHP running was an absolute pain (tried with Apache, didn't work for some reason, then moved over to Nginx), and I technically miss out on some of the more complex space optimizations because if you look at the Dockerfiles for some of the more popular images, like OpenJDK, you'll occasionally see some interesting approaches, like getting the software package as a bunch of files and "installing" them directly, as opposed to using something like apt/yum: https://github.com/adoptium/containers/blob/08dd7d416cee0fe0...

Then again, personally I'd much prefer to rely on packages that I can get from something like apt directly, even if some of those versions can be a bit older (or add the project's official apt repositories as needed).

The FROM looks incorrect. When i watch the Youtube video it mentions adoptopenjdk which is deprecated (https://hub.docker.com/\_/adoptopenjdk). You now should use https://hub.docker.com/_/eclipse-temurin/.

Eclipse Temurin is maintaining a rich collection of Java images.

Intially only the 17 was the musl-native variant, later added 11 and very recently (6 days ago) for 8 as well: https://github.com/adoptium/containers/issues/72

This page doesn't give any details about what's changed in this release.

More informative page: https://github.com/apache/netbeans/releases/tag/20

The IDE we use on this course is called NetBeans, and we use it with the Test My Code plugin.

I believe Netbeans is the preferred IDE for the mooc. There is a plugin for IntelliJ, but I've heard mixed reviews.

> For the most part, Eclipse has fallen into obscurity.

I guess it depends on the locale/company/environment?

In most conferences, online videos, as well as among the people I know personally, JetBrains IDEs (IntelliJ IDEA for Java) seem to reign supreme: https://www.jetbrains.com/idea/

They have a community version, personally I pay for the Ultimate package of all the tools. They're slightly sluggish, want a lot of RAM, but the actual development experience and features make up for that.

I know that Eclipse is sometimes used more in an educational setting, however there are also both some specialized tools, as well as customized versions for something like working with Spring in the industry: https://spring.io/tools

In my experience, the idea behind the IDE is nice (a platform that you can install whatever you want on, entire language support packages, or specialized tool packages), but the execution falls short - sometimes it's unstable, other times it works slow and so on. That said, it's passable.

I would say that personally I'd almost prefer NetBeans to Eclipse, even after it was given over to the Apache Foundation, which have released a few versions since: https://netbeans.apache.org/

It seems to do less than either Eclipse or IntelliJ IDEA do, but for general purpose Java editing and limited work with other stacks (PHP, webdev stuff, some C/C++) it is good and pleasant to use. However, if you have projects that get close to half a million lines of code, it does just kind of break and gets way slower than the alternatives. It still somehow feels more coherent than Eclipse to me, would pick it if IntelliJ IDEA didn't exist.

Some also try doing something like using Visual Studio Code with a Java plugin: https://code.visualstudio.com/docs/languages/java

That said, I only used that briefly when I needed something lightweight for a netbook of mine, the experience was somewhat underwhelming. The autocomplete or refactoring wasn't as good as IntelliJ IDEA and just felt a little bit tacked on. Then again, that was a while ago, I don't doubt that progress is being made.

(free) Apache NetBeans is there from ages, and one person on my team still uses it for PHP/web stuff (including the use of xdebug with it) because you know, it works. Some of us care about *what* gets into the repository, not *how* it gets done, as long you're productive.

Existem outras IDEs igualmente famosas: Eclipse IDE e NetBeans.

1. NetBeans

Nobody mentioned (wonder why), but 10 years ago I used work in NetBeans. I thought it was fantastic and I can see it is still being developed.