3 ms·

This is coming from me being most comfortable with OOP and dynamic languages. If you want to write Scala to actually get things done, you will find that it's a

This is coming from me being most comfortable with OOP and dynamic languages. If you want to write Scala to actually get things done, you will find that it's a miserable language to learn and that you will need to invest significant amounts of time, energy, and sanity to learn it. Furthermore, there are no shortages of Scala apologists who are so utterly enamored with the cleverness of the language that they will not concede how much of a pain in the ass it is to learn. They will claim it is easy, and then they will have no empathy for your plight. It is actually quite shameful. The attitude in Scala-land is that you are the problem, and not Scala. When you do encounter a roadblock to a seemingly simple problem, which will be quite often, you're lucky if you find a 20 paragraph explanation on StackOverflow. Otherwise, you can hopefully find a lengthy blog post about something closely related. In either case, the attitude is that it is _not_ Scala's fault that solving problem XYZ requires you to understand several chapters of advanced concepts -- it's _your_ fault for not already knowing it.

idobai 10y ago
> This is coming from me being most comfortable with OOP and dynamic languages. If you've came from the dynamically typed side then it's surely harder to learn a programming language with enhanced type system. > Furthermore, there are no shortages of Scala apologists who are so utterly enamored with the cleverness of the language that they will not concede how much of a pain in the ass it is to learn. Because for most of us Scala was the ~30th prog lang. Scala is for the polyglot programmers and unfortunately the current education system doesn't teach anything besides Java, PHP etc. > The attitude in Scala-land is that you are the problem, and not Scala. When you do encounter a roadblock to a seemingly simple problem, which will be quite often, you're lucky if you find a 20 paragraph explanation on StackOverflow. Otherwise, you can hopefully find a lengthy blog post about something closely related. In either case, the attitude is that it is _not_ Scala's fault that solving problem XYZ requires you to understand several chapters of advanced concepts -- it's _your_ fault for not already knowing it. Can you provide us some examples when you need to read over 20 paragraphs to solve a simple problem?

idobai 10y ago

> This is coming from me being most comfortable with OOP and dynamic languages. If you've came from the dynamically typed side then it's surely harder to learn a programming language with enhanced type system. > Furthermore, there are no shortages of Scala apologists who are so utterly enamored with the cleverness of the language that they will not concede how much of a pain in the ass it is to learn. Because for most of us Scala was the ~30th prog lang. Scala is for the polyglot programmers and unfortunately the current education system doesn't teach anything besides Java, PHP etc. > The attitude in Scala-land is that you are the problem, and not Scala. When you do encounter a roadblock to a seemingly simple problem, which will be quite often, you're lucky if you find a 20 paragraph explanation on StackOverflow. Otherwise, you can hopefully find a lengthy blog post about something closely related. In either case, the attitude is that it is _not_ Scala's fault that solving problem XYZ requires you to understand several chapters of advanced concepts -- it's _your_ fault for not already knowing it. Can you provide us some examples when you need to read over 20 paragraphs to solve a simple problem?