Conservative. Idaho. Software engineer. Historian. Trying to prevent Idiocracy from becoming a documentary.
Email complaints/requests about copyright infringement to clayton @ claytoncramer.com. Reminder: the last copyright troll that bothered me went bankrupt.
"And we know that all things work together for good to them that love God, to them who are the called according to his purpose." -- Rom. 8:28
As much as I like emacs, and terminal emulator, I think an IDE is the right way out of this, and I have done more recent Java than C. Of course, I think Java is now obsolete.
But for Java, I usually have used Eclipse - for about 10 years. I ran into a project where a bunch of nasty Java code had been written by contractors 12.5 hours away by time zone, and Eclipse proved by far the easiest way to read it and get into it, not to mention debug it.
This year I switched to IntelliJ for my 9 year old Android app, but that's only because Android Studio - which is based on IntelliJ - seems to be the future for Android development. I find it less intuitive than Eclipse.
For debugging, and IDE is pretty much the way to go, and I even use one for C for Microchip processors (in this case, NetBeans based).
I did some golang earlier this year, and did all the debugging with the equivalent of printf statements. Kinda ugly, but the project was only a couple of thousand lines of code, so it worked.
Yeah, I would much rather use Eclipse than emacs for Java work, for a variety of reasons.
ReplyDeleteI am a vi person for text editing.
ReplyDeleteBut for Java, I usually have used Eclipse - for about 10 years. I ran into a project where a bunch of nasty Java code had been written by contractors 12.5 hours away by time zone, and Eclipse proved by far the easiest way to read it and get into it, not to mention debug it.
This year I switched to IntelliJ for my 9 year old Android app, but that's only because Android Studio - which is based on IntelliJ - seems to be the future for Android development. I find it less intuitive than Eclipse.
For debugging, and IDE is pretty much the way to go, and I even use one for C for Microchip processors (in this case, NetBeans based).
I did some golang earlier this year, and did all the debugging with the equivalent of printf statements. Kinda ugly, but the project was only a couple of thousand lines of code, so it worked.