The conversation

Lessons learnedExperience excerpt · English

Ode to Java

Ode to Java. Boy, I love Java. When I switched jobs way back, a condition was that the new project was going be using Java. GC. Single file modules. No "forward". The Collection suite. Fast compiles. The magic of the ClassLoader. The ClassLoader, that was insightful. I don't know how much thought went into that when they came up with it, but, wow. That ClassLoader is behind a large swath of Java magic. It really hasn't changed much over time, but boy is it powerful. When I started Java, I started it because of the nascent Java web stack of the day. Early servlets and JSP. I picked because of two things. One, JSPs were just Servlets. A JSP was compiled down into a Servlet, and shazam, Servlet all the way down. Two, single language stack. Java in JSPs, Java in Servlets. Java in library code. Java everywhere. In contrast to the MS ASP (pre .NET) world. Mono-language meant my page building controller folks could talk to my backend folks and share expertise. Big win. Servlets were a great model. Filters were easy and powerful. Free sessions. Free database connection pools in the server. …

Original discussionJava at 30: Interview with James Gosling423 source comments · at import
2

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

KC

The servlet really is a powerful concept behind a bad name. I've seen more than once where people reinvent servlets in other languages.

Full original
PA

Seconded. I'm still using the Servlet API without drama. I click away as soon as I see a package that requires containers to install.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.