We should do this for software engineering holy war debates, like dynamic vs static languages, IDE or not, or whether open source is mostly good or mostly bad.
whether open source is mostly good or mostly bad.
Wait, I’m confused. There are still people claiming that open source is mostly bad?
I thought each language performs certain roles better, so it depends on the task involved.
Programming is mostly text, so the debate should be vi and emacs, and it’s a fruitless one. Learn both.
Any reason to keep your source code unavailable? I can see a monetary one, and a psychological one (insecurity).
Any time you have to deal with a big field, you should cut it down into human-readable sections.
Neither vi nor emacs is an IDE. A good idea can provide for features like online linting that vi and emacs mostly don’t provide.
We should do this for software engineering holy war debates, like dynamic vs static languages, IDE or not, or whether open source is mostly good or mostly bad.
Wait, I’m confused. There are still people claiming that open source is mostly bad?
I thought each language performs certain roles better, so it depends on the task involved.
Programming is mostly text, so the debate should be vi and emacs, and it’s a fruitless one. Learn both.
Any reason to keep your source code unavailable? I can see a monetary one, and a psychological one (insecurity).
Any time you have to deal with a big field, you should cut it down into human-readable sections.
Neither vi nor emacs is an IDE. A good idea can provide for features like online linting that vi and emacs mostly don’t provide.