>>39
Verbatim? Like that floppy disk manufacturer or what? I don't get it.
>>40
Yes, about that.. I'm just playing around, recently started to read "Teach Yourself Scheme in Fixnum Days", so that can't rally be counted as active use.
I think that an IDE (or lack thereof) can make a considerable impact on the day-to-day development. Consider writing C# code in Notepad versus Visual Studio. Yes, that might be an extreme example, but I've worked in environments where crappy editors become bumps in the road that slow down the daily work and increase the number of "stupid" error that are otherwise caught by the smart IDE editor. Colour syntax highlighting, auto-formatting, things like refactoring method names, etc. Those things might be blips on the radar to some but having good tools makes the real "work" more efficient and less error-prone. I used vi, vim, gvim, nedit and SlickEdit when I did development for Unix and hands down SlickEdit won simply because I was able to let the smart editor clue me in on the stupid typos and such that I made. With Visual Studio, I save TONS of time being able to find references quickly, do some refactoring with a couple of clicks, build and see build errors within the editor, etc. Certainly having a great IDE isn't going to save a project that lacks one or more of the other items mentioned, but having one certainly can save a company money, particularly if the programmers are making use of the features it offers.
>background colours are best kept for very important things
please elaborate. i call bullshit. or opinions.
also perl>python
Name:
Anonymous2007-07-24 14:29 ID:US+38A1s
My code window: (((((((((((((((lambda x (lambda x x ) y (lamdba x) ((((((((((((()))))))))))))()())))))))))))))))))))))(((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))
>>67
Pretty much.
Plus some autocmd magic to resume editing on the same line as when I last quit vim. And binding double-tap ii to esc, which is kind of nice.