Almost nothing changes, but it changes everything.

I want to create a new project using Play. Should I start with Play 2.0?

Play 2.0 is still under heavy development. APIs are incomplete and likely to change. Currently, Play 1.2.3 is still the best way to write Web applications in Java, and will continue to be maintained and developed by the core team and contributors even after the 2.0 release.

Play 2.0 is exciting! When can I use it in my projects?

We expect to release a usable beta towards the end of the year. In the meantime, you can try out the alpha and check the progress bars above and Lighthouse to follow the team's work.

Will all these new features slow down the framework?

We expect important performance improvements in Play 2.0, mostly because almost everything will be resolved at compilation time. Having a more complex build system may slightly slow down build performance at development time, but thanks to a better separation between dev and prod mode, it will not impact performance at runtime.

Why Scala? I would prefer support for language X instead.

We want to continue to focus on a type safe approach where as most as possible parts of your application are checked by a compiler. We strongly believe Scala will continue to gain momentum as a type safe JVM language.

Can we have feature X in the 2.0 release?

We have already planned a lot of changes in this release, and we want to avoid theSecond System effect. However if you think we missed something really important, you are free to open a discussion on the mailing list.

I want to help, how can I contribute to Play 2.0?

We are currently working hard to lay the project foundations: the build system, compilers, base API etc. This low level work is being led by Play's team of core contributors. To get involved, please follow the development mailing list and issue tracker.