3 ms·

Do you have any clue how many layers there are below the java/javac layer? What made you decide that that particular layer is where it's at, and that just one l

• agumonkey 5y ago
  Good point. Somehow the compiler is the critical tool, eclipse was failing to provide value while impeding me to work too early for me. I was happier with a makefile most of the time because I had the information in short form under my eyes. With the jvm you have a spec, it's somehow meaningful, Eclipse APIs were quite horrendous and if you need to go that low to understand why your project fails to run it's not a good tool.
  • agent327 5y ago
    I completely understand that. I'm not a java programmer; my experience is limited to fixing one tiny bug, in one java program, and I struggled a bit with Eclipse before realising building from the commandline was also possible and pretty simple. But I do most of my work in Visual Studio, which I prefer over vim+make+gdb because a powerful IDE does give you a significant advantage over a 'mere' text editor. I also find that working in vim imposes a much higher mental load than doing the same in MSVC (and don't get me started on vi without the 'm'...).
    • agumonkey 5y ago
      I have no conclusion on the matter to be honest. Like many I wasted time trying to setup emacs for language L and had a broken support system (especially regarding debugging). But I often felt that IDEs brought as much cost as value. And up until very recently, linting and ergonomics were below what I'd got with emacs (and if you've seen the regular posts about magit you have an idea of what I mean).