|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 9
Messages: 9
Messages: 9
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Web Framework Shootout Podcast Released
The podcast, split into two 1/2 hour parts, captures a team of Manning authors and guests discussing (among other things) various Java and non-Java web frameworks. Manning's Marjan Bace assembled the panel, and moderates.
The authors and guests include Yehuda Katz, Chad Davis, Max Carlson, Robert Hansen, Bear Bibeault, Chris Richardson, Dan Allen, Emanuel Bernard, Peter Armstrong and Obie Fernandez. Technologies discussed include Seam, Flex, Open Lazlo, Merb, Ruby on Rails, and Hibernate.
The debate gets quite lively in part two, and the language is a bit strong in parts. However, it does capture the quandry of a web developer when they ask "What web framework should I choose..."
You can subscribe to the podcast feed here:
Via RSS: http://chariotsolutions.techcast.com/rss
You may also sign up via our podcasts page (contains the iTunes link and a shownotes page):
http://www.chariotsolutions.com/downloads/podcasts
Direct links to each podcast episode:
Part 1
Part 2
Enjoy,
Ken Rimple
|
|
|
Message #253008
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Web Framework Shootout Podcast Released
I am very disapointed with the level of the technicality in the arguments made.
How can all these book writers and lead developers be such poor debaters. I learned nothing!
I excpeted to hear serious arguments supporting Seam or Struts, but instead I heard nothing.
The Ruby guys owned almost everyone else, no one really had any serious counter arguments to their claims. And they didnt make such brilliant arguments either!
The Ruby arguments were, Ruby is far way ahead of the competition, the smartest developers work on Ruby and use textmate and macs (those are the real words they used)
The counter arguments was, yea, Ruby people are the smartest (!!!) but twitter is slow(!!!)
I mean, okay, I am not an expert on so many things, but does this mean that active records is better than hibernate and that deploying a RoR application on a webserver is like more advanced that using ... say glassfish to deploy your web app writen in Struts2 and Grails, are application servers useful at all !!!! Is RoR really the most polished piece of code ever (IN HUMAN HISTORY)
Come on, this debate was poor, very poor
|
|
|
Message #253024
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Agreed. Lots of ranting, bashing, emotion. Little else.
Agreed. The arguments were completely juvenile. There was lots of ranting and bashing and emotion, and very little calm and intelligent comparison.
The world *needs* a good web framework comparison. There is a maze of choices, lots of misinformation, and these frameworks take huge quantities of time for developers to fully grasp. A quality overview and comparison would be excellent.
But this is awful.
For example, the Rails representative predictably says: There is no way that anyone in their right mind would do a web project in Java. The only reason to use Java is for legacy reasons... even then it's terrible...
That's a valid perspective. He should back it with specific reasons rather than rant how terrible Java is at a vague level and cite "expert" testimonial.
I've used Rails. I liked it. However, I am much happier and more productive using Stripes in Java. Why? Honestly, I'm wise enough to admit I don't know Rails enough to make a thorough, intelligent comparison. I just built a few small apps and that was enough to say, I get it, it's cool, but I'm better sticking with Stripes.
ASP.NET, JSF, Struts, Stripes are frameworks I've used extensively and can make insightful comparisons between. I've used most of those for dozens of high-pressure projects over 3+ years, I've used them in teams, I've seen other developers fall into common pitfalls, etc.
A good shootout would have people who have that kind of deep experience with the frameworks they are comparing and would be able to make useful level-headed evaluations among them.
|
|
|
Message #253025
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Web Framework Shootout Podcast Released
When I read The Ruby arguments were, Ruby is far way ahead of the competition, the smartest developers work on Ruby and use textmate and macs (those are the real words they used) I laughed my ass off. I’ve actually seen these guys come into our JUG with macs and use textmate to generate a simplistic shopping cart type app. When you ask them about interactive debugging, transaction handling, ETL, job scheduling, security, integration, messaging or other features they look back with a blank stare. Enterprise development is much more than generating a front ends for web apps. I’d say maybe 70% of our code has no visual component at all.
|
|
|
Message #253042
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Web Framework Shootout Podcast Released
YESSS... that's what has always been my sort of question, ok ROR let's you develop simple applications faster... (even though I don't know a whole lot about ROR), but Are you (ROR supporters) telling me that ROR can all the tools to handle transaction mgt, messaging layer, web services consuming/producing, etc.... the list goes on... I would say ROR developers must be those who are developing standalone type of web apps...(another php which is a bit better than php) not doing any enterprise development.
|
|
|
Message #253046
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Web Framework Shootout Podcast Released
This was the not-Struts, not JSF - well then what discussion.
The best take-away from the discussion came from the POJO-in-Action guy Chris Richardson who was concerned with frameworks that tightly coupled or drove domain model design - primarily Seam and Ruby. The domain model will last longer than the various frameworks that come and go.
Flex is best if you can dictate Flash player version. (Hard for corporate intra/extranets).
Open Laszlo solves the problem by generating code across Flash players and to Javascript as well.
Seam like Ruby increases developer productivity without the attitude.
GWT looks good since it supports a service layer but has undeveloped/rough components. Now that ext and myGwt have changed licenses and GWT-Ext has lost steam - who knows.
This discussion was low value compared to the the other presenetations. Overall a good conference.
Other take-away. Don't hire Ruby consultants since the solution to all problems is Ruby.
|
|
|
Message #253052
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
ETE Conference Presentation Materials...
Andrew,
In a way, this sort of presents the Java web framework landscape as it is today--a bit of a mess, with lots of options and no clear front-runner (everyone may argue with me as I duck now)... :)
If you want to review the other presentations from ETE, as well as other conferences we've presented on in the past, we have made them all available for free on our website:
http://chariotsolutions.com/downloads/presentations
|
|
|
Message #253165
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Thanks,,
Thanks guys, I have not listened to this but I always like to read your comments,,,,
|
|
|
Message #253470
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Suggestion
Instead, I think it may be better if each of them talk about the flaws in the framework they're familiar with. This will be more informative for all of us.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
