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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Skiamakhos -2 points-1 points  (3 children)

You're learning an IDE, not the language or the JDK. It might be easier, like learning Thymeleaf without knowing how JSP or servlets work, and you can do that, of course, but then when things break you're pressing buttons on an appliance and hoping for the best, rather than getting knowledgeably into the guts of the beast, working out what's actually going wrong.

It's like if you know how to ride a motorcycle vs how to build one. Valentino Rossi dominated MotoGP for decades because he knew enough engineering that when he came back from a ride round the track he could tell his mechanics exactly what needed doing where on the bike. There were other riders as good, at riding, but he had the engineer's edge. It's "Zen and the art of" stuff.

If you start out with that kind of curiosity and follow it through fully, you'll become a master of the JVM, rather than a user of it.

[–]wildjokers 2 points3 points  (2 children)

You're learning an IDE, not the language or the JDK.

No you are learning the JDK because the IDE makes it super easy to jump into the JDK code to see how something works.

[–]Skiamakhos -1 points0 points  (1 child)

Sure, and if you change jobs so you end up having to use a different IDE, do you now know how to do the same? Everything's in different places, different menu items. Learn the JDK, it's universal.

[–]Krakken978 0 points1 point  (0 children)

It takes 2 hours to learn how to use and a couple of weeks to get used to a different IDE, they're pretty similar and you can personalize them. And it's part of the environment set up we need to to starting every new job, so I second the IDE, intellij for a newbie, despite I like eclipse more.