Comments for Realjenius.com

Comment on Check Out the Play Framework by Maxi

Maxi — Tue, 13 Jul 2010 13:58:44 +0000

Really amazing framework!!!
at last a java tool, without the innecesary complexity of java \normal\ framework

Comment on Check Out the Play Framework by Brent Foust

Brent Foust — Sat, 12 Jun 2010 07:52:50 +0000

I thought Wicket was the best Java Web framework, until I came across Play. There is nothing to compile (it’s handled automatically) — just modify the source or add new files and refresh the page in the browser.

Play feels similar to other MVC apps, seemingly modeled after Rails, but improves upon the syntax of, for example, Wicket templates — no namespaces required (all those “wicket:” prefixes muddy up the markup). And the iteration is just a little more terse: no “it.” references. Just:
#{list MyClass.findAll()}
${_.title()}
#{/list}

Of course, the “_” may be named, instead. But it’s nice to have a short form.

Play makes it easy to add new tags (with parameters, if desired), work with JPA entities, inherit templates from other master templates, and call any Java libraries you wish. It also has several pre-built Modules available for working with (for example), GWT, akka, bespin, pdf, guice, lucene, spring, and even Scala.

The error messages in Java code are extremely friendly, showing a formatted snippet of the problem with correct line numbers. But a syntax error in a Template file can be a pain to track down, since a generic NullPointerException is reported.

The Eclipse plugin is barely sufficient, but supports syntax coloring and creation of the basic three file types: Model, View, and Controller; as well as running all test cases.

Play is a well-conceived and implemented Java Web framework that finally makes it fun and easy to start a new Web project. Just type “play new myApp”, followed by “play start” and the new app is viewable at “http:://localhost:9000″.

Comment on Check Out the Play Framework by Costis

Costis — Wed, 03 Mar 2010 12:20:14 +0000

After being disgusted from working for 5 years with ASP.NET (I am a victim of Webforms), I started looking for other frameworks that could bring happiness to my web development work. I spent a few months with Cakephp and Django. I liked both of them, especially Django, but I wasn’t feeling comfortable with PHP and Python. Then I stumbled upon Play! framework and never looked back. I’ve been using it for a month and I am totally pleased with it. The documentation is not very good (nothing compared to Django’s docs), but the support via the google group is excellent. Working with Java, Intellij IDEA and Play! framework is a joy. The pluggable architecture (like django), the code-test cycle, JPA for data access, no compiles, Groovy for templates and blazing performance with the included HTTP server are things that made me fall for this framework.

Comment on Check Out the Play Framework by Sakuraba

Sakuraba — Wed, 03 Mar 2010 10:10:31 +0000

I am switching from Grails to Play, because it is faster, more stable and requires less restarts. They have an awesome browser based test runner for all your tests, which makes testing a lot faster and easiert as doing it with Grails. It is amazing. My Integration-Tests for Play run in microseconds, whereas with Grails it takes at least 10-30 seconds to bootstrap the entire environment and then run my tests.

Besides the screencast, there is the usual suspect – a tutorial about creating a blog application – that takes you through all of the basics of Play in a very nice way: http://www.playframework.org/documentation/1.0.1/guide1

Comment on Distilling JRuby: The JIT Compiler by Paul

Paul — Thu, 26 Nov 2009 21:11:32 +0000

Hey,

thanks for the fantastic writeup. I’m trying to diagnose an issue to do with Jruby performance and this was a great help. There is some info on the different command line JIT flags that can be set for Jruby here:

http://kenai.com/projects/jruby/pages/PerformanceTuning#JIT_Runtime_Properties

Comment on JRuby “IO.foreach” Performance by Vladimir Sizikov

Vladimir Sizikov — Wed, 04 Nov 2009 09:59:41 +0000

Heh, this was fun to read, as it was real fun to watch the evolution of the fix.

Comment on Distilling JRuby: Tracking Scope by The Rubyist: September 2009 Edition

The Rubyist: September 2009 Edition — Fri, 09 Oct 2009 04:30:02 +0000

[...] Distilling JRuby: Tracking Scope [...]

Comment on Distilling JRuby: The JIT Compiler by Thiago Arrais (arrais) 's status on Thursday, 08-Oct-09 11:08:28 UTC - Identi.ca

Thiago Arrais (arrais) 's status on Thursday, 08-Oct-09 11:08:28 UTC - Identi.ca — Thu, 08 Oct 2009 11:08:57 +0000

[...] http://www.realjenius.com/2009/10/06/distilling-jruby-the-jit-compiler/ [...]

Comment on Distilling JRuby: Tracking Scope by R.J.

R.J. — Sat, 26 Sep 2009 17:21:27 +0000

Very cool – thanks for the tip!

Comment on Distilling JRuby: Tracking Scope by Thomas Enebo

Thomas Enebo — Sat, 26 Sep 2009 16:32:47 +0000

Excellent article and continuation on exploring JRuby internals. I endorse these as good explanations of how things work inside JRuby. Keep up the good work…

One thing which probably could have saved you a little time: jruby -S ast -e ‘a = 3; b = a’
Unpublished, but very useful for debugging parser problems…