Twirl
sbt-digest
| Twirl | sbt-digest | |
|---|---|---|
| 1 | 2 | |
| 552 | 32 | |
| 0.4% | - | |
| 8.7 | 6.4 | |
| 6 days ago | 9 days ago | |
| Scala | Scala | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Twirl
-
On the future of Play Framework
You could quibble with this description, but Play is an opinionated packaging of several technologies—all of which could be used alone or cobbled together by hand. Out of the box, you get tooling that compiles web assets through a pipeline (sbt-web, with features like versioning through sbt-digest), a powerful templating language (Twirl), a routing DSL, request handlers (Actions), of course, a non-blocking HTTP stack (Akka HTTP), and a few other bells and whistles useful to building full-stack web applications. These are a lot of parts to maintain together. It's a considerable challenge to provide so much under the auspice of one project. Play's combination of all these parts also necessitates specific ways to build your web application or service—which, I think, a lot of developers don't like, which has contributed to it falling out of favor.
sbt-digest
-
On the future of Play Framework
You could quibble with this description, but Play is an opinionated packaging of several technologies—all of which could be used alone or cobbled together by hand. Out of the box, you get tooling that compiles web assets through a pipeline (sbt-web, with features like versioning through sbt-digest), a powerful templating language (Twirl), a routing DSL, request handlers (Actions), of course, a non-blocking HTTP stack (Akka HTTP), and a few other bells and whistles useful to building full-stack web applications. These are a lot of parts to maintain together. It's a considerable challenge to provide so much under the auspice of one project. Play's combination of all these parts also necessitates specific ways to build your web application or service—which, I think, a lot of developers don't like, which has contributed to it falling out of favor.
-
Since PlayFramework has stalled in development, any tips on migrating to akka-http?
You can use stuff like https://github.com/sbt/sbt-digest for asset fingerprinting
What are some alternatives?
Scalate - Scalate is a Scala based template engine which supports HAML, Mustache and JSP, Erb and Velocity style syntaxes.
http4s-jwt-auth - :lock: Opinionated JWT authentication library for Http4s
Beard - A lightweight, logicless templating engine, written in Scala and inspired by Mustache
sbt-web - Library for building sbt plugins for the web
Hepek - Typesafe HTML templates and static site generator in pure Scala
akka-http-webjars - Serve static assets from WebJars
ash-ra-template - Expressive & customizable template system featuring Clojure language processing
akka-http-session - Web & mobile client-side akka-http sessions, with optional JWT support
Akka - A platform to build and run apps that are elastic, agile, and resilient. SDK, libraries, and hosted environments.
Play Pagelets - A module for the Play Framework to build highly modular applications
http4s-akka - An akka integration to handle websockets with actors.