tag:blogger.com,1999:blog-8221886912876606828.post6149334304362373710..comments2023-06-23T00:44:05.938-07:00Comments on Elided Branches: Why I'm Moving Away from the Play FrameworkCamille Fournierhttp://www.blogger.com/profile/05090020862261633248noreply@blogger.comBlogger57125tag:blogger.com,1999:blog-8221886912876606828.post-55259560502272195932015-08-10T20:17:57.922-07:002015-08-10T20:17:57.922-07:00Nils, that sounds about spot on, especially the &q...Nils, that sounds about spot on, especially the "abstraction orgy" part, well saidFlood Zonehttps://www.blogger.com/profile/09780996493835282874noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-78761929725861993342015-06-04T03:11:17.389-07:002015-06-04T03:11:17.389-07:00Hi, This is Jamuna from Chennai. I have read your ...Hi, This is Jamuna from Chennai. I have read your blog and I got some knowledgeable information through this blog. Really useful blog. Keep update your blog.<br /><br />Regards...<br /><a href="http://javatraininginchennai.com/" rel="nofollow">Java Training in Chennai</a>Anonymoushttps://www.blogger.com/profile/18198692114065110449noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-14226403631796804882015-05-25T13:19:01.885-07:002015-05-25T13:19:01.885-07:00We are in 2015, Play is still not so popular yet, ...We are in 2015, Play is still not so popular yet, it doesn't means its bad, in fact its very good and interesting but at least for now its a very hard to setup. Its main tool, sbt is very very complex to understand, more than maven itself which is not easy at all but more people already understand its tricks and know how to setup.<br />Even templates with akka, spray and play really doesnt works in windows machines I don't know why but its very common reporting errors in windows, besides the fact, most of people I know works on Windows!<br />Its a long path, I don't believe on Grails, trying stick with Angular.js and backend some restful pure java maybe. Play is still a dream.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-25312223754891307952015-05-25T13:18:59.102-07:002015-05-25T13:18:59.102-07:00works only for you.works only for you.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-20312364912553668082015-05-25T13:18:56.941-07:002015-05-25T13:18:56.941-07:00the problem is not the changes constantly, its the...the problem is not the changes constantly, its the legacy code which must be refactorized losing time and money.<br />I think you are in the wrong field. IT is about money not about changing.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-72030311255447685322015-05-25T13:18:45.445-07:002015-05-25T13:18:45.445-07:00its not so productive, and we dont have much freed...its not so productive, and we dont have much freedom for changing things.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-78976036284042957692015-05-25T13:01:07.882-07:002015-05-25T13:01:07.882-07:00its not so productive, and we dont have much freed...its not so productive, and we dont have much freedom for changing things.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-7926452116008710172015-05-25T12:52:17.969-07:002015-05-25T12:52:17.969-07:00the problem is not the changes constantly, its the...the problem is not the changes constantly, its the legacy code which must be refactorized losing time and money.<br />I think you are in the wrong field. IT is about money not about changing.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-71379929652052052032015-05-25T12:51:06.933-07:002015-05-25T12:51:06.933-07:00works only for you.works only for you.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-16598051722743863982015-05-25T12:50:06.180-07:002015-05-25T12:50:06.180-07:00We are in 2015, Play is still not so popular yet, ...We are in 2015, Play is still not so popular yet, it doesn't means its bad, in fact its very good and interesting but at least for now its a very hard to setup. Its main tool, sbt is very very complex to understand, more than maven itself which is not easy at all but more people already understand its tricks and know how to setup.<br />Even templates with akka, spray and play really doesnt works in windows machines I don't know why but its very common reporting errors in windows, besides the fact, most of people I know works on Windows!<br />Its a long path, I don't believe on Grails, trying stick with Angular.js and backend some restful pure java maybe. Play is still a dream.jonas brothershttps://www.blogger.com/profile/01187919186863895643noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-8053927449357802272015-02-01T08:32:33.228-08:002015-02-01T08:32:33.228-08:00I've been using Play 2.x for Java , Stripes 1....I've been using Play 2.x for Java , Stripes 1.5.7 , Spring 3.x and Spring Boot. <br /><br /># Play for Java is good for prototypes and some serious callback functionalities<br /><br /># Stripes simply AWESOME --> with lambda u have done almost very layered clean codes.<br /><br /># Spring MVC - earlier it sucks, with BOOT - we can write more prototype and micro services.<br /><br />I support Stripes + Play 2 can achieve any shit.....<br /><br />Stripes + Spring + Guice =anyone can say m one of the enterprise programmer.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-66347298916741758102015-01-19T06:51:27.434-08:002015-01-19T06:51:27.434-08:00I'm blushing now :)I'm blushing now :)Anonymoushttps://www.blogger.com/profile/15424779355376696816noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-88912125678270954662015-01-14T15:23:39.098-08:002015-01-14T15:23:39.098-08:00Igor you are shameless!
I concur. Run like hell f...Igor you are shameless!<br /><br />I concur. Run like hell from Play and get your butt on Activeweb! It's ... developing framework with its heart in the right place. pmhttps://www.blogger.com/profile/09814165728855157709noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-15060431356041685132014-11-18T03:53:41.302-08:002014-11-18T03:53:41.302-08:00Hello there!
I run into the HashMap's bug som...Hello there!<br /><br />I run into the HashMap's bug some time ago. But reading your writing, my felling is that you were expecting your program to run serially and got annoyed because i) it was running concurrently, and ii) it was hung in such a harmless piece of code. If you want to understand what really happened in details, you must read http://mailinator.blogspot.com.br/2009/06/beautiful-race-condition.html<br /><br />Besides that I want to know if you still have this opinion about Play Framework. I came across it almost 2 moths ago while I was coding an Akka-based project. So, do you still have this opinion?Pedro Arthur Duarte (aka JEdi)https://www.blogger.com/profile/08905861369603212834noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-87339270819092318162014-10-07T13:46:22.546-07:002014-10-07T13:46:22.546-07:00My post is a little old but still relevant I think...My post is a little old but still relevant I think. I think the Typesafe guys have stability and backward compatibility in their roadmap, but for the time being it is certainly abrasive. Perhaps someone could step-up and inspire a little more confidence?<br /><br />I still recommend Scala Play over Node.js due to their choice platform languages:<br /><br />Scala (Pros):<br />- Type-safe, leverage compile-time sanity checks to reduce test overhead and turn-around on feedback<br />- Sealed traits and case classes, love these<br />- Both functional and object-oriented<br />- Easy to read (i.e. Cog[A >: B] and Widget[-A] instantly tell me everything I need to know)<br />- Built-in functional features such as mapping, folding and options<br />- Operator overloading increasing readability (e.g. { val future = actor ? "Hello" } >> function (){ var future = actor.sendMessage("Hello") }, I am particularly tired of an excess of braces, commas, and camels)<br />- Brevity of expressing anonymous functions<br />- Wildcards (i.e. _ and _*)<br />- Encapsulation<br /><br />JavaScript (Cons)<br />- Dynamic typing and duck typing in lieu of static typing<br />- Fundamentally non-modular<br />- No parametric polymorphism<br />- No operator overloading<br />- Lack of control over object lifecycle<br />- Almost no encapsulation<br />- Hard to read ('function' keyword, braces and commas, callback hell)<br />- No IDE can seem to get context-aware code completion right.<br />- Outdated basis: "JS had to "look like Java" only less so, be Java's dumb kid brother or boy-hostage sidekick. Plus, I had to be done in ten days or something worse than JS would have happened."<br /><br />In general I can instantly understand the structural relationships in a Scala project just by reading the source whereas due to JavaScript's nature as a late-bound dynamic language it often requires that I run JavaScript code and step through it manually to understand the structural relationships.<br />Knurdhttps://www.blogger.com/profile/05570170609420849934noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-13918174603532914972014-04-27T12:41:00.365-07:002014-04-27T12:41:00.365-07:00What's good about 2.2.2? Typesafe Activator? W...What's good about 2.2.2? Typesafe Activator? What about if we have an existing DAO already, can we use Play just for the views and its controller?JThttps://www.blogger.com/profile/11119497694824099194noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-51910734846807431462014-04-21T09:08:56.912-07:002014-04-21T09:08:56.912-07:00Haven't you tried Play 2.2.2 yet?Haven't you tried Play 2.2.2 yet?Deepuhttps://www.blogger.com/profile/06387000136668333691noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-20576130020701637882013-09-28T13:57:48.855-07:002013-09-28T13:57:48.855-07:00vertx :)vertx :)El Gazalihttps://www.blogger.com/profile/07783087994466391026noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-47330537499652295362013-07-20T10:43:00.347-07:002013-07-20T10:43:00.347-07:00I like that. Fork it!I like that. Fork it!Anonymoushttps://www.blogger.com/profile/02014285619524398028noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-39944399282518104982013-06-19T14:34:25.119-07:002013-06-19T14:34:25.119-07:00It's good to know that Play has some of the sa...It's good to know that Play has some of the same issues as Grails 2. Grails 1 (1.3.7) was quite fun to develop with and even though the developers didn't put a lot of attention on "enterprise" capabilities (such as robustness or small war files or ability to run behind load balancers or keeping stable interfaces in a framework or, or, or, etc...) I still had great hope that Grails would be an excellent framework as it grew up. Alas, 2 came out with a lot of bad ideas (that re-write of the unit testing made no sense and only cost companies a lot of money for nothing). In addition, the Grails folks got very picky about some minor issues with Groovy Mixins so they broke the whole thing by creating their own very broken version of a Mixin and then making it so that their testing code worked differently if you were using Mixins. In the end, you had to convert to the Grails (broken) Mixin and then do a ton of work to get it to work in all environments (unit, integration, war file, etc...). Overall, Grails convinced us to start looking at Dropwizard and I was fascinated that other frameworks are pushing people towards Dropwizard. I just hope the Dropwizard community learns from the mistakes of others. It's off to an excellent start though.BluesPowerhttps://www.blogger.com/profile/11095614855894153651noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-11883183379042668092013-05-23T15:27:42.775-07:002013-05-23T15:27:42.775-07:00+1+1Anonymoushttps://www.blogger.com/profile/14889502647043099793noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-39661817396603873092013-03-18T07:51:01.154-07:002013-03-18T07:51:01.154-07:00Why should you throw away everything? I am still u...Why should you throw away everything? I am still using Play 1.2.4, and it works just fine. And if you don't expect things to change, your wrong. Technology is always changing and so is the web. If you want to stick something that doesn't change, you should've studied politics or something. Your in the wrong field bud.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-67125027163405347132013-02-25T07:20:47.031-08:002013-02-25T07:20:47.031-08:00Congratulations. You made the right choice.
Unfor...Congratulations. You made the right choice.<br /><br />Unfortunaly we choosed this framework, I was not involved in the decision and nobody checked the history of the framework.<br /><br />Just for make you laugh: the last version of play was 2.0.4, 2 months ago.<br /><br />They released version 2.1. You might expect that there is some upward compatiblity, unless some big issue in 2.0.4 should be fixed and if the fix breaks the compatibility.<br /><br />Nope.<br /><br />One has to change substantial parts of the code, so that it is just not possible to test the advantages and issues of the new version on the same code base than 2.0.4.<br /><br />And why ? Just because they didn't like some class names, and several other cosmetic reasons.<br /><br />And the worst is, they find this perfectly normal.<br /><br />My 2 cent's guess is that Play 2. developpers (us!) will have to throw away everything and restart from scratch when 3.0 will come if they want to keep using a maintainted framework. Or get the complete source and do the framework's maintenance themselves. Good luck.<br /><br />And this is only one-among-many reasons I DO NOT recommend Play.<br />mrlhttps://www.blogger.com/profile/13926558835682514333noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-90284602531559080752013-01-15T07:26:38.277-08:002013-01-15T07:26:38.277-08:00We had very good experience with play. All product...We had very good experience with play. All products now are in production. So, play 1.2.5 is ready for production, no problem to run tests from IDE - in IDEA it works just fine at least. And I'm happy to work with this framework. <br /><br />I remember some Issue with applying evolution scripts (we fixed it for our own branch, but it was not a bug, we just expected different behaviour for our own case). I took us 2 hours and no problem. <br /><br />I recommend Play! It is a light in java word of web-frameworks! Sergeyhttps://www.blogger.com/profile/01647492987420639165noreply@blogger.comtag:blogger.com,1999:blog-8221886912876606828.post-53237688114189143812012-12-28T06:52:34.832-08:002012-12-28T06:52:34.832-08:00We are moving away from Grails to Node.js due to t...We are moving away from Grails to Node.js due to the the "too much magic" behaviour. There are quite a few abstraction layers and they will leak. You can get funny stack traces with GORM, Hibernate, Spring and your own code happily interacting. We are really satisfied with Node.js because it's really possible to have thin, understandable abstraction and the code of third-party modules is not the abstraction orgy that Spring and Java generally seems to encourage. Nils Kassubehttps://www.blogger.com/profile/13944225425837816094noreply@blogger.com