In venue, tea had been served in Japanese Tea Ceremony style.
I attended these sessions:
N.B. These summaries may be imprecise.
- Organizer greetings
- speech: Shugo Maeda
- Keynote Address: Ruby toward the Future
- speaker: Matz
- I was pointed out that I spoke rapidly in yesterday, so today I effort to speak slowly.
- The 21st century is Programming golden age
- 1940's: no computer
- 1950's: no language
- 1960's: no algorithm
- 1970's: no experience
- 1980's: no networks
- 1990's: no performance
- C++ compiling during 1 night
- And now: 21st century
- Sufficient performance and price
- Higher Literacy
- Java runs on my daughter's cell phone, and its performance is higher than workstation I ever had have for compiling first Ruby source code.
- Timely technology is highly evaluated.
- World Wide Web
- Open Source
- Ruby
- Ruby's target field
- Network : High speed and ubiquitous in 21st century
- Text processing : E-Mail, XML, and so on
- OO : Commonsense in 21st century
- Ruby's performance
- Not best performance
- But often bottlenecks are at Network and at Database.
- Focusing for Productivity and Enjoyable
- Productivity
- Software matters = Productivity matters = Humanity matters
- Humanity matters are re-focused in recent years.
- Enjoyable
- the essence of software development
- Software developers are important
- Human Factors are important
- Ruby for me
- 1990's: hobby, just for fun
- Early 2000's: Fulltime job, still fun, and sharing happiness
- Late 2000's: Ruby on Rails appears, then change from "my Ruby" to "our Ruby"
- I was shown by DHH that marketing is useful in OSS.
- Changing the business rule
- Symbol of passion
- Beloved language
- Toward the future
- Tool to change the world
- Humanistic software development
- From Urban to Province
- Owing to WWW and OSS
- Because software is just an 'information'
- Empower Software development in Japan
- Issues
- Performance
- From slow language to useful language
- In 1.9, Ruby becomes faster with your contributions.
- And continue efforts to improve the performance.
- Trustworthy
- Trustworthy language
- Secure
- Stable
- not means "no change"
- Trustworthy interpreter
- Stable
- Predictable
- Rational
- Trusting language
- Ruby trusts its users.
- You use ruby for NICE things.
- Persistence
- I have kept Ruby development for 16 years
- I will want tot try it 50 more years
- Some person checks search counts by Google as Love/Hate Ratio
- Ruby is top beloved language by far
- Love is power, motivation
- Love changes all
- Love creates the future
- Rails3:Convergent evolution
- speaker: Jeremy Kemper
- A long time, there is a collision in Ruby culture and Rails culture
- Only Rails community had grown rapidly while Ruby community keep the size.
- At first, thanks to Matz for thinking the future of Ruby.
- I was a Scheme user, and a Lisp user at past.
- I had turned to the Ruby user because simplicity of Ruby is quite clear for me, then I keep using Ruby now.
- Great equalizers: HTTP, HTML
- Ruby usage for profession
- cgi.rb never pull the abilities of Ruby, and not useful for profession.
- Ruby on Rails appears
- feel QWAN(The Quality Without A Name)
- CoC(Convention over Configuration)
- Effects by Rails
- epicentre
- simplicity
- happiness for developers and customers
- But people who have no understanding of Ruby cultures have increased in Rails community.
- Rubyists have considered Rails users as a "storm".
- We should nurture people who have no understanding of Ruby cultures as new Rubyists rather than eliminating them.
- To do so, there are 2 barriers in current Rails.
- Attitude of rails user
- They think they can do anything in anywhere by Rails.
- They think outside of Ruby cultures.
- Inner structures: Spaghetti codes
- To do "concentration in core competence" for Rails
- To make Rails more modular
- To make Rails more Rubyish
- So, Rails 3
- We call "Unicorn Project"
- Keep CoC
- many revolutions from Merb
- Rails 3 unifies Rails 2 and Merb
Rails 2 Merb audience evelopers, enterprise users and designers developers, ruby programmers and plugin-authors principles programmer happiness, strong conventions and fluent design programmer happiness, flexibility, modularity and speed - New features in Rails 3
- speed up
- hello world: 2.78 times
- render collection: 6.27 times
- more faster with Ruby 1.9
- agnostic
- Any testing framework
- Any model or O/R mapper
- Any ajax frameworks
- relational
- Arel: improved ActiveRecord
- Duck type
- for any Model library
- for any View library
- for any Controller library
- Ready for Ruby 1.9?
- Currently, recommending for Ruby 1.8.6.
- In my opinion, we should be ready for Ruby 1.9.
- Speed
- String#encoding
- Time.parse is ready for "Year 2038 problem".
- Enumerator
- Hash#hash
- Kernel#require_relative
- More improving Ruby 1.9 is essential for...
- running ruby-debug
- behaving as a[:b] == a['b']
- tuning GC
- forking friendly
- doing copy on write
- I Think standardizing Ruby is unnecessary
- Big business may need ISO standard.
- But small agile business may not need it.
Q from attendee In current session, Matz said that Ruby will keep on changing 50 more years. Should Ruby developers think about backward compatibility for Rails? A from speaker If Ruby will change so, we would improve the Rails.
In organizer greetings, Shugo Maeda said formal greetings and one geeky phrase like that:
Recall the mind to enjoy programming
And Jeremy Kemper's session is Wowful because I seem he is improving Rails more Rubyish and understanding Ruby culture same as Ruby core team.
No comments:
Post a Comment