-
Notifications
You must be signed in to change notification settings - Fork 1
My conclusions
peterszatmary edited this page Mar 5, 2016
·
5 revisions
Despite really useful advantages i will not use Play! because of
- no backward compatibility (in major versions)
- Scala first approach. (No all API is written for Java. And because of i am a Java developer its important for me).
- lack of learning materials (better is to say that the problem is really fast aging of learning materials because of no backward compatibility)
I can use Scala API, yes i can. But i think that Scala is not a future.
Scala have also useful advantages but
- is to complicated to start with (is more complicated than Java for example)
- have binary compatibility (i dont see any advantage here)
- is also functional also object oriented (in my opinion the language need to choose one and use it)
I saw reactive concepts with Play! framework that are really strong. But Play! is reactive because of Akka under hood. Next I will try Elixir and Phoenix. Elixir is reactive on language level. Awesome ! Elixir is Erlang with new syntax close to Ruby. Also very sexy. Elixir comes from Erlang. And Phoenix is web framework build on top of Elixir. I hope that the combination of Elixir + Phoenix will be big bingo in developing the real time reactive fault tolerant maintainable web applications. I hope so... I will see.