Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Posted by Nick Laiacona on Feb 10, 2008
Dion Almaer has published a podcast of his interview with Steve Yegge, the creator of Rhino on Rails. An earlier blog post by Steve generated a significant amount of interested by the developer community. Rhino on Rails is a Javascript port of the popular Ruby on Rails framework. It is currently under active development for internal use at Google. Steve Yegge and his team hope to make Rhino on Rails open source this summer. Yegge first announced last summer at Foo Camp and in his blog. Questions Almaer asked:
- What does it mean to port Rails to JavaScript?
- What can't you do since JavaScript doesn't have the same meta programming facilities?
- Rails = a group of Active*, so did you re-implement everything?
- What do you gain out of having JavaScript all the way down?
- Does it actually make sense to have jjs? Server side JavaScript generating client side JavaScript? Argh!
- What is the state of Rhino?
- Will Rhino support JavaScript 2?
- How does the JVM help you out?
- What are the ramifications of implementing ActiveRecord with Hibernate
- Fun other languages to play with
Yegge revealed some interesting details of the project during the interview. The principal reason he choose to port Rails to Javascript on the JVM is the support Javascript enjoys within the Google corporate environment. Rhino on Rails is a true port of Ruby on Rails, starting from version 1.2. Users of Ruby on Rails should find Rhino on Rails's API familiar. It does not currently include Active Record, the powerful domain model library on which Rails database model objects are built. However, Yegge is aiming to add this functionality. When released, Rhino on Rails will probably operate within a Jetty container. It may also contain support for GWT. Yegge points to concurrency support in Rhino on the JVM and his implementation of Rails as scalability advantages over Ruby on Rails.
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
The 5 Mandates of Software Development Teams - Presto Manifesto
Regaining control of the data centre
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
No comments
Watch Thread Reply