- #HOW TO USE ECLIPSE COMPILER INSTEAD OF JAVAC HOW TO#
- #HOW TO USE ECLIPSE COMPILER INSTEAD OF JAVAC INSTALL#
- #HOW TO USE ECLIPSE COMPILER INSTEAD OF JAVAC CODE#
Recompiling after a save would unshow/show method parameter names (which didn't change) in function calls which again pushes text around that one may be reading/interacting with. Options dialog (shift+shift) would populate candidates at different time intervals and push the list around such that if you saw an option you wanted immediately and down+enter it would do the wrong thing.
#HOW TO USE ECLIPSE COMPILER INSTEAD OF JAVAC CODE#
However, I strongly thing that the first-time experience of opening VS Code is miles better than that of Eclipse, and I guess I am criticizing that a little bit.
#HOW TO USE ECLIPSE COMPILER INSTEAD OF JAVAC HOW TO#
I'm not saying that Eclipse is bad, just that I don't know how to use it. Contrast with opening a file in a brand new, unconfigured VS Code setup. I have literally no idea what I'm supposed to do next, or how to fix that I can only see a tiny bit of my code by default. I opened a Python file, and it's visible in the middle third of the window, surrounded by wide sidebars and a bottom section with labels like "Markers", "Servers", "Data Source Explorer", and so on. I countered that VS Code was very easy for me to find my way around even though I'd never used it.įor giggles, I just installed Eclipse for the very first time on this computer. You said it's not reasonable for someone who hasn't used a certain IDE for 10 years to be able to navigate around in it easily. Things that don't come easy is how to create new file templates, enforce code styling, configure database connections (if you work that way, I don't), how to package your software, and the plethora of other things IDE's do for us these days. The basics, like refactor some code, move some source files around, create a new file, etc - sure, those should come easy. If you can master a brand new (to you) IDE in minutes, then it's frankly not a very powerful IDE. Every IDE has different productivity-enhancing features (beyond basic code suggestions and auto-complete). You have to learn how to use your IDE - and once your do, productivity can go way up (this is why people do not switch IDE's very often, you must invest in your IDE to master it).
The point is, any new environment is going to be jarring at first.
#HOW TO USE ECLIPSE COMPILER INSTEAD OF JAVAC INSTALL#
and other IDEs which will not be named - took inspiration from Jetbrains innovation to narrow the gap.Īs an alternate anecdote, I spent hours trying to figure out how to compile some basic C code in VSCode - neck deep in configurations and hidden menus with special button combinations, etc - only to break down and install some random plugin. IntelliJ was so far ahead of Eclipse in terms of pure usability and delightful advanced completion and refactoring features in the early days, but eventually Eclipse 1st is which IDE they used first, and like every editor war, this is all about habit and finding that the workflow you built around one tool doesn't fit another, and then the second is about which phase you adopted the tool in. I suspect there are two components to the Eclipse vs IntelliJ bias in folks. When it came to refactoring, renames, etc, I felt empowered with IntelliJ to safely do those with their refactoring tools in way which Eclipse was a very slow follower. I could run a build whenever I wanted to find out if things were broken in some way. but in my entire career I don't think I ever looked for it. I think there is an IntelliJ "problems view" or something like it. As an IntelliJ user since 2003 I've heard this comment from Eclipse users multiple times, and always been puzzled about it.
0 kommentar(er)
