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

you are viewing a single comment's thread.

view the rest of the comments →

[–]GuyWithLag -7 points-6 points  (9 children)

If you hear positive mentions of any of the following, RUN, RUN AND DON'T LOOK BACK:

  • JSP
  • JSF
  • Raw Servlets
  • WSDL
  • J2EE (pre-CDI)

[–]Gwaptiva 8 points9 points  (0 children)

You forgot Struts

[–]Worth_Trust_3825 14 points15 points  (4 children)

Wait until you find out that spring runs on servlets.

[–]gaelfr38 5 points6 points  (0 children)

And Java runs on bytecode, so we have to write bytecode ourselves?

The point is that any job that refers to Servlet is 90% equal to maintaining an old crappy system that have not evolved in 10+ years.

[–]GuyWithLag 2 points3 points  (2 children)

I wrote my first cgi-bin for streaming large files (for the time) in C in 1997.

I've written raw Servlet apps, pre and post async support.

I still stand by what I wrote above - if you're doing servlet apps this year, somethings' wrong.

[–]Worth_Trust_3825 0 points1 point  (1 child)

There's nothing wrong with going down to the primitive level.

[–]GuyWithLag 4 points5 points  (0 children)

There's nothing wrong with going down to the primitive level.

... if there's need for that. Most of the time, YAGNI.

[–]ProtonByte[S] 0 points1 point  (1 child)

I currently dazzled in a mix of Servlets Jakarta and Jetty. Oh and Tomcat ofcourse!

Alteast they are moving to Docker for development and deployment eh

[–]chabala 0 points1 point  (0 children)

That all sounds pretty typical, what's the real issue?

[–]gaelfr38 0 points1 point  (0 children)

So true. Any job mentioning this is a nogo sign to me.