Saturday, July 16, 2011

The 1st day of RubyKaigi 2011 (Afternoon)

In this afternoon, I attended these sessions:

  • Next version of Ruby 1.8 and 1.9
    Video (Japanese)
    • by some Ruby committers
    • There are no futures for Ruby 1.8.x
      • Ruby 1.8.7 goes only for maintenance release
      • Ruby 1.8.6 will become the final maintenance release in the next year
    • Use Ruby 1.9.x
    • Ruby 1.9.3
      • Until 1.9.2, The license is dual licenses of "GPLv2 and Ruby license"
        • GPLv3 incompatible
      • Since 1.9.3, The license will be dual licenses of "2-clause BSDL and Ruby license"
        • GPLv3 compatible
      • private constant
      • Parallel execution of Ruby-test
      • IO.write
      • Refine the GVL
    • Ruby 1.9.1 will become obsolute when Ruby 1.9.3 is released.
  • Ruby, its community and me
    Video (Japanese)
    • by Shota Fukumori
    • My first community attending is for "Generation 1991".
    • And now I'm attending some communities.
    • In RubyKaigi2011, I proposed String#prepend method, and accepted!
    • Now I have refined the parallel execution of Ruby-test.
    • Why only few junior highschool or highschool students are attending to tthe community?
      • Let's try on and join us
        • mailing list
        • write a blog
  • Shipping at the Speed of Life
    Video (English)
    • by Corey Donohoe
    • Measurement for latency
      • BrowserMob
      • Pingdom
    • Other tools we use
      • collectd
      • Nagios
      • Propane(Mac OS X)
      • Campfire
      • Hubot
    • Interaction with users
      • twitter
      • email
    • We made our original tool
      • haystack
      • How much errors are occuring and who raises these errors
      • How many users encount the errors and where the error occurs
    • Jenkins CI
      • not only trunk, but also branch
      • Janky - the webhook between Jenkins and github
      • integrate with campfire
    • Real User Metrics(RUM)
    • Silverline
      • Monitoring tool for footprint
      • We detected the process had been killed every morning at 5:00!
    • How deploy?
      • Trunk for almost servers, branch for few servers
      • Heaven : Capistrano based deployment tool for our system
    • Measure, Grow, Care!
    • Deliver value often
  • Issues of Enterprise Rubyist
    Video (Japanese)
    1. by Ayumu AIZAWA
    2. Knowing Ruby
      • Reading the book "Joyful Ruby"
      • That's Joyful!
      • I made a Ruby subcommittee in my company, and I held some ruby events in there.
      • Some people start to drop out, why?
        • There are programmers not being fun with programming, in enterprise domain.
        • I mistake a theme: series event, abstract theme
      • So I refine: ont time event, concrete theme
    3. Useful Ruby
      • To make own tools by Ruby does not spread the Ruby usage.
      • To make the tools for own team is useful!
    4. Valuable Ruby
      • Yet not spread the Ruby usage.
        • No Jobs
        • No Reasons
        • No Capabilities
        • No Standardization
      • communicate and solve step by step - Not Effective
      • Communicate with aggresive divisoin - not with conservative divisoin
      • Use ruby in ruby-friendly business domain
  • Parallel world of CRuby's GC
    Video (Japanese)
    • by nari
    • CRuby is running on 1-core.
    • GC is "mark and sweep".
    • Parallelization
      • CRuby is still running on 1-core.
      • But GC is not.
      • Parallel marking
      • Task steeling
      • Lock free
    • sweep with pop_top() and pop_bottom()
      • Many threads call pop_top() and pop_bottom()
      • Race Condition occurs in pop_bottom()when element size of deq is 1.
  • Ruby Interpreters in the Parallel World
    Video (Japanese)
    • by Koichi Sasada
    • In this fifteen years, Ruby makes the many impossibles possible.
      • Running on JVM
      • Jobs on Ruby
      • JIS standerdization
      • and so on
    • But there are many improvements yet.
      • Performance
        • On my lab, students do it.
        • NogakuDo by arton-san
      • Reducing power consumption
      • Portability
      • Modularity of RubyVM (for RiteVM)
      • MVM
N.B. These summaries may be imprecise.
And I don't translate Q&As in the article because these are the gift for attendees in there.

No comments:

Post a Comment