Merb + Rails merger

"Merb in Action" => "Rails3 in Action"

Table of Contents
1. Building Your First Rails 3.0 Application
2. Overview of the Rails stack(s) + architecture
3. Creating Rails Applications
4. Using DataMapper for Models
5. Using ActiveRecord for Models
6. Other Choices for Models
7. Processing Requests
8. Routing in Rails 3
9. Customizing Views
10. Working on the Client Side
11. Supporting Characters
12. Using the Plugin API
13. Testing Your Applications
14. Deploying a Rails Application
15. Scaling Rails

Appendix A Just enough advanced Ruby
Appendix B The migration story
Appendix C Rails 2 to Rails 3
Appendix D Merb 1 to Rails 3

Rails 3 will have mountable applications, not engines or slices.

I just got an email from manning about "Merb in Action".
  • Rails becomes more modular, by building on rails-core with the ability to opt in or out of specific components and making it possible to replace parts of Rails without disturbing other parts.
  • Merb performance improvements flow into Rails, including benchmarking applications so developers can see which optimizations have real-world impact.
  • A defined public API with a test suite, so users and plugin developers have a stable API to build against.
  • A "core" version of Rails, like Merb's current core generator, that makes it easy to select just the parts that are important for your app.
  • DataMapper and Sequel support as first-class ORMs, along with ActiveRecord as the default.
  • Rack support in Rails 3, to improve the state of modular, sharable logic between applications.
So far, it seems that merb google group is the best source. And Matt Aimonetti answers all the concerns.

Yehuda Katz says
"If you want to learn Merb for modularity and power that is not currently present in Rails, stick with Merb. We'll provide a good upgrade path to Rails3 (and feel free to contact me personally to keep me honest on that promise), and you'll have a leg-up when the same power makes its way into Rails. While Rails3 will still be very similar to Rails2 for current Rails users, it will look a lot like Merb for those users who are currently drawn to Merb."

"We always said that there would be breaking changes in Merb 2.0. Now, some of those breaking changes will be in tandem with the Rails3 merger. However, we will treat them like any other breaking changes, and make sure the deprecation notices flow freely and the transition path is clean. Make sense?"

Matt Aimonetti says,
"The great advantage of using merb now, is that it has a public API so we will be able to easily migrate it to the new 3.0 API. Concretely, we are planning on being able to replace merb-core by rails-core in your merb app and to use merb-helpers and other plugins with rails-core."

I think "Merb in Action" would take longer than expected. And it's required to rewrite the whole chapters that are published. Of course, book's title will not be changed but I'm just worried about Merb. It would be called Rails3.0 by many other people, especially inside Rails community.

As Ezra said,
Merb is dead, long live Merb(Rails-3.0)!
Matt Aimonetti said,
I don't think Ezra is right. Merb isn't dead. First off, merb will still be around until the next release (rails 3.0) and we will keep on supporting it even after that (maintenance).
So many merbists are disappointed by this news but there is nothing can be done. Engin Yard's decision looks solid. I've accepted it, after all. I've read many articles enough to say that I will stick with Merb. There were some people who even want to switch to Django. I decided to practice Merb more than before. Because Merb would be the core changes in Rails3. And it could happen that Merb core team is too busy. But evangelist like Matt Aimonetti will help us. I hope taking this path would be natural to Merb2.


오픈소스 merb-book 한국어 번역

Now, merb has many resources to learn.

튜토리얼 및 기타 소개 동영상들 : MerbCamp videos,
스크린캐스트 : http://merbunity.com/screencasts

and there is open source merb-book which is started by Matt Aimonetti.
Well, I saw Chinese and Japanese but no Korean one. I think that there are probably not enough rubists in Korea. Anyway I sent a message to him that I want to start if there is no one. And here it is.

I've completed "Merb-More" Chapter. But there are still unfinished chapters in English.
Merb-More 챕터까지 모두 한국어로 번역을 완료했지만, 영어로 된 원본이 아직 빈 곳이 많습니다. 번역하는데에는 네이버 단어장, 구글번역기, 바벨피쉬, 그리고 제 경험을 최대한 살려서 번역했습니다. 많이 부족하므로 오타나 잘못된 번역을 알려주시면 고치도록 하겠습니다. 한글로 된 merb 책이 나오려면 아직 오래 걸릴 것 같습니다. (영어 책도 아직 출판되지 않았습니다.) 참여를 원하시는 분은 메일 보내주시기 바랍니닷.

I finished the translation.
현재까지 작성된 영어 원본에 대한 번역은 마쳤습니다. 제 생각에는 본격적으로 책들이 쏟아지는 2009년 전반에는 이 오픈소스 책도 많은 개선이 있을 것 같습니다.

Rails와 Merb가 합쳐지는 이 시점에서, Pragmatic Bookshelf, Apress 등에서 나온 책들은 의미가 희석되었다고 생각합니다. 워낙 빠르게 변하다보니 책들이 따라가지 못하고 있습니다. 오픈소스 책의 발안자인 Matt Aimonetti가 Rails 코어팀에 합류했기 때문에 이 책이 그나마 현재 나온 책중에서는 가장 참고할만한 책이 되지 않을까 싶습니다. Rails3.0에선 Merb의 기능들을 흡수할 예정이기 때문입니다.

제가 실수로 master 브렌치에 작업내용을 합치질 않았었습니다. -_-;;;
이제 github에서 다운받으셔서 정상적으로 보실 수 있습니다. 업데이트 내용은 4번째 장인 "데이터베이스와 상호작용" 부분입니다. 현재까지 작업된 영어원본까지 모두 작업완료되었습니다. 책을 받아서 보시는 분들이 계시다면, 오타나 의역에 무리가 있는 부분을 지적해주세요. :)

오픈소스 merb 책이 나왔지만 한국어 번역이 없어 매트에게 해보겠다고 메세지를 보냈습니다. 흔쾌히 해보라해서 현재 작업중이고 getting started/mvc까지 작업완료했습니다. 이제와서 보니 일본어나 프랑스, 중국 번역판에 비해 늦은 것은 아니었습니다.

책을 보는 방법

필요조건 :
a. ruby, gem
b. git

스텝 :

1. 먼저 제 github 저장소에서 merb-book을 로컬 pc로 복사합니다.
$git clone git@github.com:jaigouk/merb-book.git

2. 다운받은 merb-book 루트 디렉토리에서 다음을 실행해 주시면 됩니다.

3. 브라우저에서 http://localhost:4000 주소로 가면 책을 보실 수 있습니다. 목차 맨위에 보시면 각 언어들 링크가 있는데 한국어를 선택하시면 됩니다.

Chapter별 완성도(2009/1/4): 좋음(○), 미흡(△), 없음(X)
  1. 서문

    1. 머리말 By Yehuda Katz(X)
    2. 서문 by Matt Aimonetti(○)
    3. 공헌자들(○)
  2. 소개

    1. Ruby 언어(○)
    2. Merb 웹프레임웍(○)
    3. DataMapper ORM(X)
    4. RSpec 테스팅 프레임웍(○)
  3. 시작하기

    1. 설치방법(○)
    2. 어플리케이션 생성하기(○)
    3. 프로젝트 구조(○)
    4. MVC(○)
    5. 컨트롤러(○)
    6. (X)
    7. 모델(○)
    8. 리퀘스트 패스(○)
    9. 라우터(X)
  4. 데이터베이스와 상호작용

    1. DataMapper 세팅()
    2. 데이터베이스 스키마()
    3. 데이터베이스 쿼리()
    4. 모델 관계(X)
    5. 데이터베이스 마이그레이션()
    6. 유효성 검증(X)
  5. 어플리케이션 테스팅

    1. 테스트를 하는 이유(△)
    2. 모델 테스팅(X)
    3. 리퀘스트 테스팅(X)
    4. RSpec Cucumber를 사용한 통합테스팅(△)
  6. Merb More

    1. 인증(○)
    2. 메일러(X)
    3. 캐싱(X)
    4. 예외처리(X)
    5. 슬라이스(X)
  7. 레시피

    1. 간단한 블로그(X)
    2. 블로그 슬라이스 만들기(X)
  8. 배치

    1. Passenger(△)
    2. nginx(△)
    3. JRuby 와 Glassfish(X)
    4. 어플리케이션 번들링(X)


garage sale like notes


iPhone, and desktop notes are hard to see them all in a big picture as Roam said.

3D desktop and ruby

As the rumor says, it is obvious that Apple is developing next OSX. 3D environment is the critical difference. Bumptop desktop could be similar with it. Trends are really clear. Wiimote, Jeff Han's Ted demo, and Ubuntu Compiz fusion. The new era of HCI has come. But there're little apps which are appropriate with these environments. Adobe launched AIR, and it is still early for general users. But it is certain that adoptions are growing.

Now, we see java 3d OS. Where is shining, rich ruby desktop environment! Do we need to learn Air to mimic 3d actions?


morganstanley - Presentation from Web 2.0 Summit

Mary Meeker Web 2.0 Presentation
View SlideShare presentation or Upload your own. (tags: trends web)

Motorola hired 350 people for Android.


look, see, imagine

Recently I've read "The Back of the Napkin". And Here is what I'm thinking.
I think it is really hard to see the big picture in these days. There are just too many informations to catch up.

We're gathering informations by emails, RSS, twitter, conversations and so on. But have you really gone through all the star-marked articles? Well, I haven't.

And there are web apps that makes me do extra things. Some apps look promising to me except I don't have a mac.

After reading Alan Greenspun's "The Age of Turbulence", I'm sure that the global economy's speed is really fast like light. It's out of control in this hot, flat, crowded world even for FRB.

How can we catch up all these informations? May be, no one can. But they only pay their attentions on something meaningful to them. As Eric Schmidt says, most of us focus on the head, not the tail. Why? Because there is so little time to spend on reading, studying, and even eating. Most of people do what they have been doing. But there are specific needs. And they start to google it or to digg it. They already have established their information sources. It could be friends, social networking sites, ranking sites, or a RSS reader. Here it comes, "Look, see, imagine".

I don't have enough room to post every data that I've gathered. And it would consume a lot of ink and papers. Why there is no software that help me to see the big picture?