This is incorrect. Functional code bases exist in many production environments. Twitter (pre musk) migrated their bloated code base TO Scala because functional code bases are easier to maintain and understand.
If you think about it, it makes sense, side effect free code will be easier to maintain just due to the lack of side effects.
As I said in another response here, it’s incorrect to compare Java 21 or Kotlin and Java 8. You can rewrite your bloated slow Java 8 code in functional reactive approach in Java 21 as well.
You can make a mistake writing any sort of code. What actually matters if it’s readable enough to catch the bug. I would argue that functional languages is the best option here, especially when we’re talking about about huge enterprise applications on complicated frameworks like Akka or ZIO.
This is incorrect. Functional code bases exist in many production environments. Twitter (pre musk) migrated their bloated code base TO Scala because functional code bases are easier to maintain and understand.
If you think about it, it makes sense, side effect free code will be easier to maintain just due to the lack of side effects.
As I said in another response here, it’s incorrect to compare Java 21 or Kotlin and Java 8. You can rewrite your bloated slow Java 8 code in functional reactive approach in Java 21 as well.
You can make a mistake writing any sort of code. What actually matters if it’s readable enough to catch the bug. I would argue that functional languages is the best option here, especially when we’re talking about about huge enterprise applications on complicated frameworks like Akka or ZIO.