Live data from Hacker News

Eclipse GlassFish: This Isn't Your Father's GlassFish

foojay.io

11–20 of 49 posts

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#11
post #2

Probably would be a good idea to include at least a single sentence somewhere near the top explaining what the heck a glass fish is.

In the Java world it is rather common to use something called application servers. These are meta-applications that provide your applications an environment with things like database abstractions and the like, as well as admin interfaces.

It solves some of the same problems you might reach for Kubernetes or OpenShift for, your application gets access to external resources in structured ways and you get to look at dashboards.

GlassFish is an example of such an application server. WildFly is more common, and is the artist formerly known as JBoss. If you have some knowledge in the enterprise Java ecosystem you can quickly and easily (or maybe not, it depends) deploy your creations into these.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#12
post #2

Probably would be a good idea to include at least a single sentence somewhere near the top explaining what the heck a glass fish is.

> what the heck a glass fish is.

In Biodiversity, a glass fish includes a few group of Asian fishes that show crystal transparent bodies to hide from predators. Specially when young. They are vertebrates that evolved transparent muscles. Two gens are kept in aquariums: Parambassis ranga and several ghost catfish from gen Kriptopterus.

We can assume that the programmer likes aquariums. The word Yakarta is not random, as is related with the catfishes distribution.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#13
post #7

Unfortunately the name Glassfish has been pretty tainted by now. If you say your platform is based on Glassfish they'll automatically assume you're an old donkey not up to date on latest Java technologies like Spring Boot.

I love the irony / (perceived) sarcasm in your comment, :p.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#14
post #2

Probably would be a good idea to include at least a single sentence somewhere near the top explaining what the heck a glass fish is.

probably this article isn't for you if "glassfish" isn't a familiar term.

if curious (or fomo) it would have taken you about 15 secs to find out what glassfish is, which is still probably 15 less than what you wasted on this mini rant. from there it's up to you to go down the rabbit hole.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#15
post #6

Why would you compare Eclipse GlassFish instead to Payara or Wildfly/JBoss? Anyway, that bickering between JEE application server vendors is what caused Spring to win. It doesn't matter it has update churn that is almost as bad as in JS ecosystem, just the fact you don't have to think about AS helped adoption. Well that and significantly easier testing. And Spring Data with generating queries from method names. And y…

Spring and JEE (or Quarkus) are very similar, from the viewpoint of an application developer both have the same JAX-RS REST and Hibernate/JPA API's. IMO the kind of person who only knows Spring and doesn't understand modern JEE is exactly the kind of person you don't want to recruit.

Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use? Spring itself is a wildly adopted standard. It is a semi open standard in that anyone can use it freely, but in that it's not supposed to be implemented by others.

The same is true for Micronaught or Quarkus. Learn the frameworks. But they are not a new open standard.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#16

Why would you compare Eclipse GlassFish instead to Payara or Wildfly/JBoss? Anyway, that bickering between JEE application server vendors is what caused Spring to win. It doesn't matter it has update churn that is almost as bad as in JS ecosystem, just the fact you don't have to think about AS helped adoption. Well that and significantly easier testing. And Spring Data with generating queries from method names. And y…

Yet the WebAssembly bros are into replicating application servers with Kubernetes pods running WebAssembly containers, go figure.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#17
post #6

Earlier quoted context omitted.

Spring and JEE (or Quarkus) are very similar, from the viewpoint of an application developer both have the same JAX-RS REST and Hibernate/JPA API's. IMO the kind of person who only knows Spring and doesn't understand modern JEE is exactly the kind of person you don't want to recruit.

Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use? Spring itself is a wildly adopted standard. It is a semi open standard in that anyone can use it freely, but in that it's not supposed to be implemented by others. The same is true for Micronaught or Quarkus. Learn the frameworks. But they are not a new open standard.

Except people keep forgetting they implement the standards on their very foundation.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#18
post #6

Earlier quoted context omitted.

Spring and JEE (or Quarkus) are very similar, from the viewpoint of an application developer both have the same JAX-RS REST and Hibernate/JPA API's. IMO the kind of person who only knows Spring and doesn't understand modern JEE is exactly the kind of person you don't want to recruit.

Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use? Spring itself is a wildly adopted standard. It is a semi open standard in that anyone can use it freely, but in that it's not supposed to be implemented by others. The same is true for Micronaught or Quarkus. Learn the frameworks. But they are not a new open standard.

> Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use?

People don't really talk about Jakarta EE as "the standard". Haven't been doing that for quite some time.

You learn it so you don't hand Spring the ultimate monopoly. I thought we all didn't like monopolies? Why give Broadcom one?

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#19
post #6

Earlier quoted context omitted.

Spring and JEE (or Quarkus) are very similar, from the viewpoint of an application developer both have the same JAX-RS REST and Hibernate/JPA API's. IMO the kind of person who only knows Spring and doesn't understand modern JEE is exactly the kind of person you don't want to recruit.

Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use? Spring itself is a wildly adopted standard. It is a semi open standard in that anyone can use it freely, but in that it's not supposed to be implemented by others. The same is true for Micronaught or Quarkus. Learn the frameworks. But they are not a new open standard.

There's nothing to be gained by picking a winner, especially if it doesn't really matter because the important APIs are the same.

Newer frameworks like Quarkus are specifically built for container usage and applications built with it are a bit faster and smaller than Spring boot.

Re: Eclipse GlassFish: This Isn't Your Father's GlassFish

#20
post #2

Probably would be a good idea to include at least a single sentence somewhere near the top explaining what the heck a glass fish is.

Thank you for your feedback. I'm the author of the article and will review how I can improve this.

However, at a brief glance back at the article, The second sentence in the first paragraph says it's an "application server". Further below the illustration image, there's a text in bold that says "Eclipse GlassFish is now a production-ready, enterprise-grade platform".

So I'm really curious, whether the article didn't make it clear, or there was a lack of interest on your side.

Post reply on HN