re: Is there such thing as a bad programming language? VIEW POST

VIEW FULL DISCUSSION
 

The number one problem that makes a bad language is pitfalls. I define pitfalls as potential bugs that tend to get exposed only after they've done some damage. Usually because:

  • It makes sense to expect it to work.
  • It works in the simple cases.
  • It doesn't work in more complex cases.
  • Once you found out it doesn't work, you have already integrated it in your code - so you need to do lots of refactoring to fix it.

There are other reasons to not like a language, but most of them are a matter of personal taste. But I think everyone would agree that pitfalls are bad.

code of conduct - report abuse