I could basically say the same thing about Java: it's a nice programming language that has its use cases but man do I not like the ecosystem it has. So many libraries and frameworks use XML configurations and it's like, am I programming in Java or XML? Then there are frameworks or some applications where everything is overengineered. So many classes that are named AbstractHyperOmegaFactoryConverterConfigurator or some similar tongue twister that leaves you wondering what exactly it does, and all these classes are all over the place when I'm pretty sure most of the work these classes do could have been done with 90% less code.
See? Most of the times it's not a problem with the language, just some people haven't fully mastered how some things get done in a language they are not used to, but that's not to say all programming languages are perfect or anything.
I write Java (mostly) for corporate code... in a previous job, just for giggles, we actively had a competition running (monthly winner got a prize) for the longest method names that would still compile and make sense in English. I think the record was somewhere around 130chars - for a method name!
Hating the long names and lack of readability isn't really a reason to bash on any language - the same misuse can happen in all languages. But remember, the original post was (I presume), posted in humour...
Agreed, and that's basically my point: a lot of times people don't like certain conventions about a language or its environment and it's not really about the language itself. That or they don't have the full mastery over a programming language's mechanics so "people hate what they don't understand".
I could basically say the same thing about Java: it's a nice programming language that has its use cases but man do I not like the ecosystem it has. So many libraries and frameworks use XML configurations and it's like, am I programming in Java or XML? Then there are frameworks or some applications where everything is overengineered. So many classes that are named AbstractHyperOmegaFactoryConverterConfigurator or some similar tongue twister that leaves you wondering what exactly it does, and all these classes are all over the place when I'm pretty sure most of the work these classes do could have been done with 90% less code.
See? Most of the times it's not a problem with the language, just some people haven't fully mastered how some things get done in a language they are not used to, but that's not to say all programming languages are perfect or anything.
I write Java (mostly) for corporate code... in a previous job, just for giggles, we actively had a competition running (monthly winner got a prize) for the longest method names that would still compile and make sense in English. I think the record was somewhere around 130chars - for a method name!
Hating the long names and lack of readability isn't really a reason to bash on any language - the same misuse can happen in all languages. But remember, the original post was (I presume), posted in humour...
Agreed, and that's basically my point: a lot of times people don't like certain conventions about a language or its environment and it's not really about the language itself. That or they don't have the full mastery over a programming language's mechanics so "people hate what they don't understand".
I tend to hate the people that hate what they don't understand, but maybe that's just me. :D
You can literally write this article about any language. People always feel the need to bash a language instead of just accepting that it can be used.
Though saying that I couldn't make it through the whole article