Your SlideShare is downloading. ×
Charles Nutter Presentations
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Charles Nutter Presentations

797
views

Published on

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
797
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
26
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. JRuby on Rails
      • Charles Oliver Nutter
    • 2. Agenda
      • Who Am I
      • What Is JRuby
      • Why JRuby on Rails
      • Demos
      • What Now
      • Conclusion
    • 3. Who Am I
      • Charles Oliver Nutter
      • Senior Staff Engineer at Sun Microsystems
      • JRuby Core Developer
      • Rubyist wannabe living in a Java world
      • Based in Minneapolis, Minnesota, USA
    • 4. Why Go To Sun?
      • Work full-time on JRuby
      • Opportunity to make real progress
      • Sun folks get it, want Ruby to succeed
      • Java folks need Ruby
    • 5. Why Stay in Minnesota
    • 6. What Is JRuby
      • 100% Java impl of Ruby...Ruby on the JVM
      • Pure interpreted, native threaded
      • Born 2001, product of many developers
      • Largely Ruby 1.8-compatible
      • Slower than Ruby...for now
    • 7. Ruby calling Java
      • require ‘java’ include_class “javax.swing.JFrame” include_class “javax.swing.JButton” frm = JFrame.new(“My frame”) btn = JButton.new(“My button”) frm.set_size(300, 300) frm.content_pane.add(btn) frm.show
    • 8. Ruby calling Java
      • include_class “java.awt.event.ActionListener” class MyListener < ActionListener def actionPerformed(event) event.source.text = “New text” end end btn.add_action_listener(MyListener.new)
    • 9. Why JRuby on Rails
      • Java is pervasive
      • Java libraries are exhaustive
      • Many still believe Java is the “everytool”
      • Java webapp developers are unhappy
      • Rails webapp developers are happy
    • 10.  
    • 11. What do Rails Devs Get
      • Scads of libraries; if you need it, there’s a lib
      • JDBC - universal database support
      • “Good” EE stuff: clustering, failover, deployment, remote management
      • Extensive monitoring capabilities
      • A gateway to the “enterprise”
    • 12. What do Java Devs Get
      • A web framework that’s usable
      • A useful schema management tool (finally)
      • Markup that doesn’t suck
      • Four extra days per week
      • Happiness
    • 13. Depot 2
      • ActiveRecord-JDBC to MySQL
      • Rails integrated with Java EE
      • Java Management Extensions (JMX)
    • 14. What Now: Short Term
      • Fix broken bits
        • Marshal-based session
        • Interpreter bugs
      • Performance
      • Script-based Java EE/Java library support
    • 15. What Now: Long Term
      • Implement remaining C extensions: Mongrel, SSL, others you’d suggest?
      • Continue expanding ActiveRecord-JDBC
        • Abstract out schema definition
        • Solidify automatic CRUD support
      • More GUI tool support
    • 16. Conclusion
      • JRuby on Rails mostly works right now
      • JRuby will not be “done” until it’s fully working
      • ActiveRecord-JDBC opens many doors
      • Java EE is actually fun with Rails
      • More Rails is more Rails...JRuby enables!
    • 17. Information
      • Email: [email_address]
      • Blog: headius.blogspot.com
      • JRuby: www.jruby.org
      • ActiveRecord-JDBC and Mongrel-Java: rubyforge.org/projects/jruby-extras
      • More JRuby at RubyConf and JavaPolis