141–149 of 149 posts
Earlier quoted context omitted.
You can easily import your preferences into your new workspace. I mean, it's not even difficult to find, File>Export and File>Import.
But why are they separated by workspaces in the first place?
Earlier quoted context omitted.
I believe Eclipse has it's own Java compiler, so it was probably a compiler feature.
> I believe Eclipse has it's own Java compiler, so it was probably a compiler feature. It does, and it's much better than javac for IDE use cases. That's one of my biggest pain points with IntelliJ. They've tried to implement some kind of incremental compilation on top of javac, but it doesn't work reliably and often forced 5-minute from-scratch recompiles on the last project I worked on.
Eclipse is one of those tools that I've found to give dividends over the years, I mainly used Eclipse CDT for C/C++ development, and then moved on to Scala and the normal Java based Eclipse. There's also DBeaver for Database work.
The learning curve was steep, mainly around setting up projects so the compiles happened outside the IDE. I mainly used Eclipse to discover the code (call hierarchy was a godsend) and for finding definitions, autocomplete etc...
Over time though the investment has paid of, going from Java, to C/C++ to Scala, to DB work (dbeaver) all have Eclipse underneath it and the same principles apply.
A few free plugins like Vrapper that give Vim emulation are also super nice.
A huge plus is that if/whenever I switch jobs, I don't need to harass anyone in the finance department over licenses. This scales up from the scrappiest of startups to the largest of red-tape laden mega-orgs.
Eclipse has fallen out of fashion but I doubt it'll die, its one tool in my toolbox I can always reach for.
Eclipse I find to be a mixed beast; if you get it into your 'sweet spot' or ideal configuration, it can be perfect. Mine is Gradle based projects (the integration seems to work fine, or use the CLI), and keeping things simple with POJOs, a bit of Spring Boot etc for more complex things. I've worked with truly horrible projects/configurations e.g. Websphere Application Developer which is/was based on Eclipse but with everything and the kitchen sink bolted on. It was slow, buggy, took 30 minutes between firing the IDE up and being able to work etc. EJB's, DB2 database access etc - just a nightmare.
So to me they're both sort of what you make of them; I find the Eclipse plugins to meet all of my needs well, the times I've tried IntelliJ or paired with someone that uses it, I don't agree with the purported benefits.
Earlier quoted context omitted.
While it may be hard to show that Java's demand has decreased - and overall it may well not have since many companies which were using Java will continue to do so just by inertia - but for the latest generation of programmers, specially ones focused on ML / Data Science, Java feels like ancient history
Yep. As a professional developer, I'm way over being excited and enthusiastic about Java; on some days, and having sampled more modern languages, I downright hate it. My guess is that the grandparent poster is mistaking this disillusionment for a decrease in demand. Like COBOL, I believe Java will continue to be the bread and butter of application programmers long after crossing popularity curves with a dead slug.
One nice thing about Eclipse is that its free and there a ton of plugins for almost every language out there. I use Pycharm as my primary IDE but I still have Eclipse installed in case I want to do something in Perl or Java. And to be honest there are always a couple of little features here and there that I miss.
Earlier quoted context omitted.
Yep. As a professional developer, I'm way over being excited and enthusiastic about Java; on some days, and having sampled more modern languages, I downright hate it. My guess is that the grandparent poster is mistaking this disillusionment for a decrease in demand. Like COBOL, I believe Java will continue to be the bread and butter of application programmers long after crossing popularity curves with a dead slug.
What's a good replacement for Java that has static typing and tool support? Is there one yet?
Another statically typed language, non-JVM, with decent momentum is Go. It's like C with a slew of sorely needed improvements. Very straightforward and there's often a single, obvious way to get something done. As a result I find I'm very productive in it. Performance is topnotch too. Tooling is quite good. I'm not sure it replaces Java as an "Enterprise" language for large-team projects though.
Kotlin is another "better Java" language on the JVM. Pleasant enough to work with, but not as large an adopting community. Tooling is good if you like IntelliJ.
C# is Microsoft's challenge to Java. Has borrowed some good ideas from Java and extended them, interfaces well with Windows (obviously). Tooling is good if you like Visual everything and Microsoft.
Now may be a good time to switch to a language that more fully embraces functional programming. F# and OCaml are possibilities, Erlang has a great rep for stability, and Haskell is said to be very powerful but with a daunting learning curve.
I'm experimenting with all of these and have the damndest time making up my mind. There's kind of an embarrassment of choice.