No seriously I want to know. Don't act all like haxxorz from the '70s.
You are anonymous after all.
I myself am a newbie who was introduced to /prog/ramming using Borland's Turbo Pascal. Then I began using gedit when I began learning OOp in Java. And recently I began learning Vi but I'm still quite clumsy with it. All I am wondering is if it's really a good idea or just a waste of time?
So how many of /prog/ prefer a GUI editor over a CLI editor or even an IDE over an text editor?
>>40
Agreed. Although longer method/constant names do need autocompletion, especially in code that's saturated with them.
Name:
Anonymous2010-07-12 8:13
I like IDEs for OO programming. They give you a quick outline of your classes and methods, and code completion is awesome.
e.g. you type "someObject." and eclipse presents you with a list of all methods of the object, with a description and return types for each of them.
much better than having to look up the javadocs every few seconds in my opinion. sure, if you are only dealing with the basic classes like String, you won't need this because you just know all the methods. however, when dealing with new stuff its an incredible time saver.
for small C stuff I use vim, for larger projects geany can be quite nice.
>>42
If Java were less verbose and javadoc weren't so broken you could do what real programmers do and have the documentation open in a second window in a tiling window manager.
Name:
Anonymous2010-07-12 8:33
>>43
just typing a dot or pressing ctrl+space is still faster than opening the relevant doc in a second window and looking for the specific method.
>>44
I'm having a hard time picturing you coding. Are you just sitting there, eight hours a day, banging out line after line of random library functions?
Name:
Anonymous2010-07-12 9:59
>>1
I'm actually a hacker from the 60's. I shared the software with my community and we were free!!
Name:
Anonymous2010-07-12 10:34
>>46 I shared paper reels of software that made lights blink with the guy across the hall and it was pointless enough that nobody cared
Name:
Anonymous2010-07-12 10:44
>>47
Hey, it was fun and it was great money. What we did was a real mystery to everyone. It really was an age of computer magic.
I've swithced to vim + pylint + ipython after long search for good python IDE.
I've used kdevelop for C++ back in kde3 days, but I guess I would stay with vim nowadays.
Generally IDE is good when your codebase gets so bulky and scattered that you can't find your own way around anymore. Maybe that's why Microsoft is so into it.
When I use an editor, I don't want eight EXTRA KILOBYTES of worthless help screens and cursor positioning code! I just want an EDitor!!
Not a "viitor". Not a "emacsitor". Those aren't even WORDS!!!! ED! ED! ED IS THE STANDARD!!!
>>1
…an inappropriate number of points in ellipsis? Sure, when I'm a little boozed I like to go wild and put four or even five (!) points there. But not too often, and never when I'm sober, because it makes me look like a faggot.
Name:
Anonymous2010-07-12 14:37
>>36 dozen plugins that exist
Exactly. There's intellisense and omnicompletion and a bunch of plugins and whatnot, one combination works for one language or one platform other combination doesn't.
I couldn't get it working fast enough, so whatever, it's not that important. Though, if anyone knows how to get something like intellissense for C# in gVim on Linux and Windows, I would like to hear.
Meanwhile this is all I need: inoremap <C-Space> <C-n>
inoremap <C-S-Space> <C-p>
GVim4life. It has everything you could possibly need:
vim project for easily organizing files
ctags/taglist for inline docs and jumping to code
omnicomplete for code completion
:make for building, jumping to errors
clewn for graphical interactive debugging
countless plugins for useful things, like surround, align, nerdtree
and all the vim goodness you expect out of a rockstar text editor
Name:
Anonymous2010-07-12 15:51
>>15
This is the part that makes me the most nervous about using an IDE. Those pages upon pages of settings, all hidden away... You can hardly tell what the hell options it's using to build a given file. Someone could set a special compiler flag for one file somewhere, and you would never know it until it causes a bug, and then you're tearing your hair out for days.
I like makefiles because they are auditable. They constitute the complete set of explicit instructions for building the project; there are no hidden flags or mysterious options fucking with your build. They are properly revisioned. You can get a log of changes to it, and look at diffs between versions to see what's changed. Good luck doing that with an IDE project; the damn thing changes every time someone adds a file.
>>56
Just leave the Compile key alone and run make from a separate window.
Name:
Anonymous2010-07-12 21:04
I must say I've fallen in love with Textmate recently, on OSX. It tickles my fancy
Name:
Anonymous2010-07-12 21:46
Vim is more than enough for large projects, for me at least.
It's even a little too much at times, and leaves me wishing for something simpler.
But it's the best solution for me, so I still use Vim.
Name:
Anonymous2010-07-12 23:37
>>58
You watched the screencasts didn't you? Goddamnit.
>>66
Any sufficiently clever DSL macro hack is indistinguishable from FIOC.
Name:
Anonymous2010-07-13 18:54
I wuv TextMate. It looks like the shit, it is easily extendable, It works for all the languages I throw at it, (Python, Perl, C, C++) it works very well with git, and I can start and aim it from Terminal, which is unusual for OS X GUI IDEs.