OSNews

Terminal, GIT/SVN, Python, Latex.

Some people prefer doing things this way. What I’m saying is that even in 2009, using a text editor is still equal in power to any other way and that this means _equality_. Anybody, in any country, with any tools they can afford can compete on the world stage. Can OSnews not see the importance of that!?

Relevant to nothing, I must interject:

WOOT WOOT LaTeX! And xterm!

Usually faster than IDE's way of doing stuff.



Let's be honest, Notepad doesn't cut it for a large project.

If you compare eclipse with emacs, you probably agree that emacs users are seen as more "pro" than eclipse users; the same applies to vim users. But both emacs and vim are really powerful, more so than an IDE if setup correctly with good plugins. But then you could say both emacs and vim *are* IDEs; the difference is that they require more knowledge on how to operate them, unlike eclipse which is a lot more easier to start with.



I could compete perfectly well with pirated software, like a lot of hungry programmers do out there in the real world. Companies already know that and they won't even care, because if you are poor today, you pirate their software to build the next big thing, then you'll get enough money to pay for it in the future. If that wasn't the case, they would be providing their tools with hardware lock keys to make the life of the poor programmers more misserable, but then they are losing potential customers and also making their platform only accessible to those that can pay.

Fully agreed. My "IDE" has always been four xterms and Emacs. Add version control system and various other tools. I couldn't imagine anything that an IDE could give me.

And besides, most of the hype is just typical marketing crap. That these new "superior" tools give outstanding boost to "productivity", etc. Kind of the same thing as with the classical "Taylorism".

And while I've tried something like Visual Studio and agree that it is a fine tool, I still strongly dislike IDEs. Mainly more because of the implicit things these typically seem to imply; a collar around your neck and that kind of drag-and-drop programming. But maybe I shouldn't dislike IDEs themselves; maybe this is a direct result of badly designed and over-complex APIs that almost every new language seem to carry.

But obviously the bottom line: each to their own, bad carpenter blames his tools, etc.

Edited 2009-12-19 06:49 UTC

Unit testing? SVN is a shockingly poor SCM too.. GIT is a nice theory, till you try to use it with a large team working on common code or interdependent modules. In my experience it's better to use a locking mechanism in SCM, because it forces methodical thinking and gets developers talking to each other. Non-locking only works in a single developer/widely dispersed scenario. If all the team members are in a single office space, communication works best; locking forces communication.



I predict that whatever you produce will either be unmaintainable by anybody except yourself or will fail to run correctly. I've seen this attitude before, usually with fairly novice gung-ho developers. It's all very well making big statements, but results need to be documented, fully tested and stable. To be honest, any coder worth their salt can code in a plain text editor - the reason many don't is more to do with the amount of time they save. That is not being lazy, that is being pragmatic.