Google Play Framework
Marion Gwilt
Support for the Scala programming language has been available since version 1.1 of the framework.[3] In version 2.0, the framework core was rewritten in Scala. Build and deployment was migrated to SBT, and templates use Scala[4] instead of Apache Groovy.
Play is heavily inspired by ASP.NET MVC, Ruby on Rails and Django and is similar to this family of frameworks. Play web applications can be written in Scala or Java, in an environment that may be less Java Enterprise Edition-centric. Play uses no Java EE constraints. This can make Play simpler to develop compared to other Java-centric platforms.[22]
Play provides integration with test frameworks for unit testing and functional testing for both Scala and Java applications. For Scala, integrations with Scalatest and Specs2 are provided out-of-the-box and, for Java, there is integration with JUnit 4. For both languages, there is also integration with Selenium (software). SBT is used to run the tests and also to generate reports. It is also possible to use code coverage tools by using sbt plugins such as scoverage or jacoco4sbt.
Anyway, I think the main difference is that play 1.x tried to build it's own stack while escaping away from j2ee, now they are part of a new and alternative stack, based on scala, akka, sbt and with the support of a company like typesafe...
The core is written in Scala, so if you aren't a Scala developer you can't fix easily a bug by yourself. This was a strength of play 1.2. Furthermore if the documentation is not very good you are lost. In play 1.2 you can simply look into the code. With eclipse you had an IDE to easily search for reference. I'm unsure if it exists a comparable IDE for Scala. I heard that eclipse an intellij works fine with it, but haven't own experiences.
The components are more loosely coupled in 2.0. In play 2.0 you can choose easily your preferred template engine or persistence layer. In 1.2 it was more difficult to choose something except JPA for persistance.
The dependencies to other frameworks are higher. For example they now need Scala and Akka. Both are nice, but complex. So you can run into big trouble if there are errors in one of these frameworks. In play 1.2 I only see such risk for Hibernate.
It's also worth noting that most commands you would use are available directly from sbt. Personally, I would only use activator to create a blank project. From then on, I do day-to-day tasks from sbt. (E.g. 'sbt run' to run the play app in dev mode, with the so it is reloaded every time a file changes.)
I just installed Ubuntu 12.04 LTS, I am very new to the Ubuntu OS and I would need help with it. I am trying to install this open source platform called Play Framework, to install it I need to add the installation directory to my system path, the documentation for Play says that I should open a terminal and type export PATH=$PATH:/to/path/play. I have tried this it did not work. I also tried sudo apt-get install play and that did not work either. I am completely lost now, I need help.
Note that the /path/to/play in the documentation should be the parent directory containing the play executable (but not including the executable; the example may be a little confusing). So, something like:/opt/playframework/play-2.2.1/is what should be added to the PATH in .bashrc.
With Dynatrace you will get observability for all applications developed with the Play Framework framework including end-to-end distributed tracing, metrics and log insights. Additionally Dynatrace deep code level insights will give you CPU profiling insights including method hotspots, insights into calls to databases, error/exception analysis, and much more. Comprehensive out-of-the box metrics will give you insights into memory allocation, garbage collection, and thread behavior.
Play Framework is an easy-to-use, lightweight framework for anyone looking to build web applications with Java and Scala, the two biggest programming languages in web development. Play Framework runs on Akka, a fast-acting computer program with a toolkit and runtime to facilitate smooth operations and prevent any unexpected hassles when designing websites. With its intricate framework architecture, Play Framework makes efficient use of CPU, memory and threads so you can expand your online business without irritating limitations.
Beginning web developers should flock to Play Framework as one of the simplest frameworks to use when working with Java and Scala. Like Ember.js, Play Framework operates under a model-view-controller (MVC) design to guide its users through website creation and maintenance without over-complicating the process.
Also, Play is discontinuing support for outdated versions like Scala 2.12, sbt 0.13, and Java 8, adjusting to its dependencies that no longer back these editions. Significant library updates include Akka HTTP 10.2, an upgrade to Guice 6.0.0 and Jackson 2.14. Play has enhanced its modular components such as sbt-web and sbt-js-engine, and transitioned to Jakarta Persistence API to support updated versions of Hibernate and EclipseLink. Some new features related to the operation of the framework itself have also been introduced. Full release notes can be found here.
Both in-game purchases and upgrade models are believed to be on their way, despite LIVE's many years as a closed system - a policy which has so far meant that no MMO or free-to-play games have been supported by Microsoft's online facility. A change to that policy may be welcomed by gamers, but the effects of a free-to-play presence on XBLA's economy are uncertain.
The story follows several developments in the past few weeks which could have influenced a decision, including Sony securing CCP's Dust 514 as a PSN exclusive, partly due to it's more open platform but largely because of the option to make the game free-to-play.
Just last night, Valve announced that 92 per cent Metacritic rated shooter Team Fortress 2 would become free-to-play after four years on the market as a traditional retail product. That game is already available on Xbox 360 via the Orange box.
df19127ead