We’ve been pretty quiet with Rubinius developments for a while, so I thought I’d bring people up to speed.

The previous year has seen a lot for the project. We were sad a number of developers were laid off the project, but that has only increased our desire to get the project to a usable state.

Some of the highlights include, but are not limited to:

• Rewriting the VM in C++
• Experimenting and building multiple JIT compilers
• Pushing RubySpec completeness and compliance levels
• Getting large scale libraries like Rails and RubyGems running

All those things are available today in our git repo on github.

Recently, Brian Ford and I published a roadmap, laying out the activities of most importance over the next few months. We’re going to try and be more vigilant about updating blogs and roadmaps in the coming months, to keep people more up-to-date.

Finally, a lot of people ask me “How can I help on Rubinius? I don’t have a lot of time.” The answer is simple:

• Download your favorite library
• Try it under Rubinius:
  • bin/rbx test/test_whatever.rb or
  • bin/rbx gem install rspec; bin/rbx -S spec my_spec_dir
• Report bugs that you find to our github Issue tracker.

The more people start to report bugs, the more coverage we get over the vastness of the ruby landscape. So while we’re hard and work getting the performance up, you can help out getting the compliance up.

Thanks again to the ruby community for all the patience you have shown the team over the years. Rubinius has been a long road, but I really feel like we’re onto something big.

In the coming months, I’m going to try and post more posts about technical aspects of Rubinius, so look for those.

The last time we checked in, I was delivering the bad news about having to let a bunch of my team go. I received a lot of kind words of encouragement during the hard time, which I want to thank everyone for.

In addition to kind words, a number of people stepped up and indicated they had positions available that my newly unemployed friends would be great fits for.

One such offer was from Daniel Yoder and Charles Hornberger at AT&T Interactive in the R&D department, the makers of the yellowpages.com. I’m extremely happy to announce that Eero Saynatkari (rue on IRC) has recently been hired by them and even given time to continue work on Rubinius!

This development makes me so happy. To see the community pull together in a tough time and even continue to make an external investment in Rubinius.

Thanks again guys! You’re what make me love being a Rubyist.

There have been some sad developments within the Engine Yard Rubinius team that I’d like to address head on.

Earlier today, I had the unfortunate task of reducing the team size to 2 people, which meant laying off the rest of the team.

I’m sure this comes as a shock to many, as it did to my friends to whom I had to give walking papers. This was certainly never a scenario that I had ever hoped to find myself in when Engine Yard offered me this dream job early in 2007.

The reason for the layoffs is not Engine Yard divesting interest in Rubinius,
but rather a necessary reorganization of budget priorities. That’s a fancy way of saying that EY could no longer afford to sustain the large team we had.

This is a sad day for me, one that I’ve been dreading. It stings not only
because of what it means to Rubinius but also because of what it means to my friends with whom I will no longer be working. They’ve put blood, sweat, and tears into Rubinius and their everyday presence will be sorely missed. I hope that they do not think badly of me or Engine Yard.

When Engine Yard gave me the go ahead to hire a team, they did it with the best
intention: to help Rubinius grow. And we have definitely done that. In the
last year, we’ve achieved amazing goals within the project:

• We went from running very little ruby code to running rails.
• We got rubygems up and running well.
• We got a parser entirely in ruby integrated.
• We wrote a whole new VM to build on.

We’ve had our fair share of setbacks, but the team has always rallied.

Rubinius will continue to move forward, continually bolstered by the awesome group of people who give up their free time to help on the project.

Tom Mornini has posted on the EY blog as well; you should read his take.

Thanks to OSNews, I know that the new standard of C++ is already finalized. Having it at 2008, it doesn’t need to change base to Hex

Let’s wait for the compilers to catch on (GCC, I’m looking at you). I hope this will bring good news to Rubinius (which nowadays switched to C++ also) as well.

Hi everyone. I’m super happy to announce that we’ve gotten the C++ branch stable enough that we’re making in the default branch. This means that those of you with existing clones are going to likely do a little work to get them sane though.

Here is what was done:

• The old master branch was rename shotgun.
• The cpp branch was copy to the name master.
• The cpp branch was then deleted.

Anyone that has up to now been working on the cpp branch has a couple of options.

1. Delete your clone and re-clone. This is the easiest. The default checkout will be code in the cpp branch and you’re off and going.
2. Fix up your current repo. I did this by doing the following commands:
   1. git checkout master
   2. git reset --hard origin/master
   3. git branch -D cpp

   This will get your local master branch repointed and properly checked out. In addition, the old cpp local branch can be deleted.

Hopefully no one experiences much pain due to this change. It’s been a long time coming and I’m really excited.
If you do run into problems, post a comment or stop on by IRC and we’ll work it out for ya.

Thanks!

เข้าใจว่าทุกคนคงเคยผ่านในรายวิชา Programming in Visual Language มาแล้ว คงจะคุ้นเคยหน้าตาของ Visual Studio มากกว่า แต่ก็มีหลายๆคนที่หันไปใช้ภาษา Ruby ซึ่งอาจไม่ค่อยคุ้นเคยกับหน้าตาของโปรแกรมสักเท่าไหร่

เพิ่งไปเจอ IDE ตัวหนึ่งที่เรียกว่า Ruby in Steel ซึ่งเป็นกลุ่มนักพัฒนาที่พัฒนาเอาตัว Ruby, Rails เข้ามาใช้ร่วมกับ Visual Studio

มาดูหนังหน้าโปรแกรมกัน (กดเพื่อดูรูปอื่นๆ)

ซึ่งแน่นอนว่า “มันไม่ฟรี”

49$ สำหรับ Text Edition และ
199$ สำหรับ Developer Edition

ความสามารถทั่วไปคล้าย Aptana (RadRails) แต่ด้วยหน้าตาที่คุ้นเคยน่าจะทำให้ใช้งานกันได้สะดวกมากกว่า

แต่เดี๋ยวก่อน! ยังมี Personal Edition ซึ่งแน่นอนว่าฟรี

สำหรับผู้ที่สนใจ สามารถดาวน์โหลดตัวโปรแกรมได้จากลิงค์ข้างต้น และ

• ebook เบื้องต้น
• video เบื้องต้น

เพิ่มเติมก็คือหนังสือ Ruby on Rail (RoR) ทั่วๆไปนั่นเอง

เอเมน~~~~~~~~~

I have a habit to use testing branch of debian. Currently it’s Lenny.

The problem is, gcc package now is version 4.3. The g++ of that version is stricter (being transitioning to C++-0x), emitting errors when compiling rubinius c++ vm. The solution (workaround, actually) is installing the 4.2 versions, then replacing the gcc and g++ symlinks (prvided by gcc and g++ packages, respectively) to point to gcc-4.2 and g++-4.2, respectively. Yes, it’s a hack.

Hey folks, sorry for the quietness here. Thought I’d fill everyone in on the current status of Rubinius.

We (the Rubinius team) have been hard at work on a couple of fronts:

• a new C++ VM: the team has been hard at work getting a new VM up and running back to the level we had the old system at. Our output has slowed to a little bit as the rest of the team has gotten up to speed on this new code base. Now, I’m sure you’re wondering why we’ve begun working on a new VM. Well, there are a few reasons:
  
  • Better organized. We’ve learned a lot in the building of the last VM about how to structure things. For instance, using C++ lets us model Ruby classes as C++ classes, providing the VM with the same familiar structure and execution as their Ruby counterparts. This lowers the barrier for understanding and using the code base.
  • Better tested. The old VM, I’m ashamed to say, had no unit tests. From day one of the new VM, we’ve been writing unit and integration tests. This has helped us a lot to keep the code base under control, as everyone who writes unit tests knows.
  • More potential. One of the big changes is keep a lot of parts of the system open. For example, we’re actively experimenting with using LLVM to speed up method execution a lot. The old code base, with no tests, was quite tangled and sadly didn’t provide any easy way forward for a lot of experiments we wanted to do
• We’ve been working a lot of Ryan Davis’s ruby_parser project lately. We’re actively looking to use that code base as Rubinius’ internal parser. This is towards our goal of more Ruby code, but as anyone who’s written a parser will tell ya, it can be a real pain.
  Ryan has made great progress getting it working and integrating it with Rubinius’ Compiler.
• Conferences: Wilson Bilkovich was just in Berlin, talking technical about Rubinius at RailsConf Europe. I’m here in Austin, at Lone Star Ruby Conf, finishing up my keynote that I’ll be giving later today.
  The whole team will be at RubyConf in November as well, and a few are likely going to OOPSLA as well.

I know that a lot of people are eagerly anticipating Rubinius, and I want to thank you all for your patience with me and the rest of the team.

This is a dream project, and turns out to be pretty darn hard and a lot of work. I’ve made the mistake in the past about talking about when I think that we’ll release 1.0. Something I don’t think I properly understood a year ago was the level that people are looking for a 1.0 to operate at. If we released a 1.0 that was 10x slower than MRI, we’d probably be in pretty tough shape.

At the some time, I know people want to play with Rubinius. We fell off doing monthly releases a while back, and we’re going to start getting back on that soon. Hopefully that will give people insight into the project’s progress more.

Again, thanks to Engine Yard and everyone else for wonderful support.

Hi everyone. Been too long since the last update, so wanted to get everyone up to speed.

Rubinius

Things have been a little quiet on the Rubinius front, as I’m sure a lot of you have noticed. We’re still hard at work, currently getting the new C++ VM into shape.
This new C++ VM fixes a lot of fundamental problems the shotgun VM had (type safety, expression ordering, etc), which is a major reason we’re migrating our work to it.

Things have been a little quieter, commit wise, as the rest of the team gets up to speed on the new VM that I’ve been working on. Shotgun has been put into maintenance mode, with updates to the current main coming mainly in the form of bug fixes to the kernel.

I know that the advances we’re making in the new VM everyone will love, from more performance to less crashes to better code organization.

Comic-Con

I’ve just returned from Comic-Con, having spend 4 days in the sun down in San Diego with the rest of nerdom.
It was quite a fun con though quite tiring. We managed to get into some good panels, but didn’t make it into the Hero’s and Lost panels. Seems you had to arrive at 6am to even attempt to get a seat. The line to get in was literally a mile long (no really, I’m not kidding.)

Conferences

Since we’ve been hard at work trying to get Rubinius to 1.0, I haven’t done too many conferences this summer. The next one I’ll be at is Lone Star Ruby Conf down in Austin. Should be fun, I’ve never been to Austin before and people seem to like the city.

Hello,

I just came across a new group created on FaceBook, which covers major subjects like… (1) Ruby (2) Rubinius (3) IronRuby (4) Rails and (5) Merb.

The main goal is to discuss all this major topics under on roof. This group is specially created by Indian developers, with a mission to promote Rails and other related languages/frameworks in India.

I would highly recommend joining there.

Thanks

I’m super proud to say that we’ve release version 0.9.0. It’s a snapshot of the work we’ve already been doing, but we’re trying to formalize our releases a bit more.

We’re going to be doing another release, 0.10, next month, as well. We’re working to do more releases, more often.

Download it now!

Hace un tiempo que estoy probando rubunius (una máquina virtual para ruby desarrollada por Evan Phoenix inspirada en smalltalk-80) y además estoy colaborando con rubyspec un proyecto que nació como parte de rubinius. Rubinius está en proceso de desarrolllo, para probarlo hay que bajarse los fuentes y compilarlo, o… para los que usan debian o algunos de sus derivados pueden bajarse el siguiente .deb que cree hace algunos días, que lo disfruten .

I’ve been a little out of touch lately – crazy accounting project for school – but was able to carve out a little time to chat with the guys at Engine Yard who are doing some cool things with Ruby.Engine Yard employs Evan Phoenix, the founder of the Rubinius project. The project aims to deliver a virtual machine for Ruby and will be previewing Rails running on Rubinius at RailsConf 2008 later today.

According to Evan, Rubinius is an implementation of a Ruby platform, just like the standard Ruby interpreter, IronRuby, MacRuby, JRuby, or countless other implementations. What’s interesting is that since Ruby doesn’t really have a specification, it’s difficult to say that platform xyz is not a compatible implementation of a Ruby runtime. In response, Rubinius decided to create a test suite that could help standardize Ruby as a language across the growing number of VM implementations for Ruby. The test suite is available at RubSpec.org. According to Evan, many of the other implementations are using the test suite. I can see this leading to a formal standards body (a la the JCP, but without one vendor with overwhelming control) to guide the Ruby language. A standardization process would be good news for enterprise customers that want to reduce vendor lock-in.

As an aside, an interesting thing about the Rubinius project is that anyone can get commit access after submitting one patch. While the project is sponsored by Engine Yard, they don’t appear to be controlling commit access (ah, this would make Josh happy . As a result, there are over 150 committers to Rubinius, some of whom are very active and others who have submitted only a few patches.

It’ll be interesting to watch the Ruby community mature and see if Rubinius’ truly open governance model will catch on with other early OSS projects (or rather, with the companies that back these projects).

A heads up that I’ll be participating in the RailsConf Community CodeDrive, hacking on Rubinius

Come hang out with me and other project hackers and share the love!

Bring your questions, quandaries, criticisms, and code!

See you Thursday morning at 10am!

We hit a major milestone tonight. As most people know, we’ve been working to run Rails on Rubinius by RailsConf to have something to show off, even if it’s pretty slow.

Well, I’m super proud to say that tonight, rails served up both static and dynamic pages under Rubinius. Previous to tonight, we’d been blocked just trying to get Rails to even load. I decided to just try loading it up and bang on it enough to get it up and going.

In a scary way, it didn’t take very much code. Which meant we were very close already.

It’s pretty late, so I’m going to keep this short. Big thanks to everyone who’s contributed to Rubinius and had faith in us. Enormous thanks to Engine Yard, without whom I don’t know if we’d been able to reach this amazing height.

More updates to come…
]]> http://blog.fallingsnow.net/2008/05/03/welcome-to-the-club/ Sun, 04 May 2008 06:00:09 +0000 evanphx http://blog.fallingsnow.net/2008/05/03/welcome-to-the-club/

I’ve like to formally welcome the maglev development team over at Gemstone to the Ruby environment club.

For those of you that haven’t yet heard of maglev, it’s a brand new Ruby VM being developed by the folks over at Gemstone. Gemstone is the makers of probably the most advanced object-oriented database used today, and have traditionally been a Smalltalk shop till recently.
With the tide rising on Ruby, I’m happy to see another player enter the field. This only means that Ruby is continuing to mature and see that the community is healthy.

I was personally excited to read an interview with Bob Walker and Avi Bryant concerning maglev, because Rubinius is mentioned more than a few times. They’re looking at Rubinius for a couple of reasons. For one, the RubySpec suite we’ve developing and are about to spin off. The more people that we see using the suite and depending on it, the more mature it will become. Not having a spec for Ruby is commonly touted as a reason that it’s a toy, immature language, and anything we can do to dispel that thinking is good for the community.

The other reason that I’m excited about maglev is that they’re taking a very similar approach to the problem of building a Ruby environment. Like Rubinius, the VM is minimal and most of the kernel is implemented in Ruby.
My hope is that the kernel of Rubinius can be refactored and developed to be generic enough for other environments to use. While I know little about maglev’s current environment, they’re a natural build off the work in the Rubinius kernel. I’d hate to see people develop the code functionality of a ruby environment yet again (I count 5 code bases to this effect currently: MRI, JRuby, Ruby.NET, IronRuby, and Rubinius).

Being able to use a generic Ruby kernel is not unique to a smalltalk style VM. With some luck, it could be used by the folks in other environments as well. In my eyes, this is a big win for everyone. For one, this would mean a common code base that consists of the primary Ruby functionality, and thus would mean a vastly reduced worry of fragmentation. Plus it would alleviate the need for this code to be written again, letting future environment developers focus on taking Ruby to the next level in terms of platform integration, performance, etc.

By now, a good deal of you have read Charles breakdown of Ruby implementations.
If you haven’t please go read at least the Rubinius section before reading the rest of this post, as it is largely a response to that.

Now, on to Charles section on Rubinius:

Evan Phoenix’s Rubinius project is an effort to implement Ruby using as much Ruby code as possible. It is not, as professed, “Ruby in Ruby” anymore. Rubinius started out as a 100% Ruby implementation of Ruby that bootstrapped and ran on top of MatzRuby. Over time, though the “Ruby in Ruby” moniker has stuck, Rubinius has become more or less half C and half Ruby. It boasts a stackless bytecode-based VM (compare with Ruby 1.9, which does use the C stack), a “better” generational, compacting garbage collector, and a good bit more Ruby code in the core libraries, making several of the core methods easier to understand, maintain, and implement in the first place.

A little background is in order, to put things straight. Rubinius began as a hobby, back in February of 2006 (Same month I got married, that’s how I recall).
At RubyConf 2006, I gave a presentation on what was then the initial work, which at that point constitute 3 bodies of work.

1. A VM written in ruby, using RubyInline to access some raw operations. More slow that you can imagine.
2. A VM written in C, created by hand translating the ruby code into C. Parts of this work were originally done using a translator program I’d written, which tried to convert the VM in ruby into C mechanically. This proved beyond my skill and time level, thus I felt it was more important to have something running.
3. A kernel of ruby code, implementing 95% of the core library / kernel / class library of 1.8. The terminology for this part has always been fuzzy in the Ruby community. Rubinius calls this the kernel, some call it the standard library, some the class library. It’s the implementations of the builtin classes such as Array, Hash, etc.

It’s plainly true that today, the VM is about 22,000 lines, the kernel 23,000 lines. I’ve never hidden this fact from anyone; in fact I’ve put those numbers directly into presentations. That’s been true for pretty much the entire life of the project in the public. The initial ruby prototype was only even run by me.

I do though believe that it still can claim “Ruby in Ruby”. When I present on Rubinius or am asked about this, the response I give is:
What is Ruby?
The typically response is that Ruby is 3 things:

• A syntax
• An execution model
• A kernel

Again, lets have some context. When I began this project, there was buzz about improving things like String and Array. In 1.8, this requires diving down into C right off the bat. Plus, consider languages such as C++ and Java. Java largely claims to be written in Java, since almost the entire class library is written in Java. This lets it evolve faster, because there is no mismatch between Java user code and the Java class library.
It is this that we typically talk about “Ruby in Ruby”. If I’ve not explained this well enough in person and in type, I take full responsibility for this misunderstanding.
There is the long term goal of having a VM which is mechanically generated from Ruby code, in the same way Squeak’s VM is written. But after that RubyConf 2006, there has been no additional work on this, but there is a very good reason for that.

Rubinius today has around 150 people who have received commit rights. The vast, vast majority of their work has been in the kernel, because this is the largest part of the whole system. And probably 95% of that work has been writing Ruby code. This means that for pretty much all contributers, helping with Rubinius means writing Ruby code. And thus to them, it is Ruby in Ruby.

The promise of Rubinius is pretty large. If it can be made compatible, and made to run fast, it might represent a better Ruby VM than YARV. Because a fair portion of Rubinius is actually implemented in Ruby, being able to run Ruby code fast would mean all code runs faster. And the improved GC would solve some of the scaling issues Ruby 1.8 and Ruby 1.9 will face.

Rubinius also brings some other innovations. The one most likely to see general visibility is Rubinius’s Multiple-VM API. JRuby has supported MVM from the beginning, since a JRuby runtime is “just another Java object”. But Evan has built simple MVM support in Rubinius and put a pretty nice API on it. That API is the one we’re currently looking at improving and making standard for user-land MVM in JRuby and Ruby 1.9. Rubinius has also shown that taking a somewhat more Smalltalk-like approach to Ruby implementation is feasible.

But here be dragons.

In the 1.5 years since Rubinius was officially named and born into the Ruby world, it has not yet met any of these promises. It is not generally faster than Ruby 1.8, though it performs pretty well on some low-level microbenchmarks. It is not implemented in Ruby: the current VM is written in C and the codebase hosts as much C code as it does Ruby code. Evan’s work on a C++ rewrite of the VM will make Rubinius the first C++-based Ruby implementation. It has not reached the Rails singularity yet, though they may achieve it for RailsConf (probably in the same cobbled-together state JRuby did at JavaOne 2006…or maybe a bit better). And the second Rails inflection point–running Rails faster than Ruby 1.8–is still far away.

Charles once again gets my hackles up, thought his points are true. We’ve yet to run rails. We’ve yet to run significant Ruby code faster than 1.8. I am finishing up a C++ rewrite of the VM.

I’ve addressed the Ruby in Ruby phraseology above, so lets move past that.

Performance is improving at a slow, regular pace. This is because of 2 factors:

• VM improvements. Adding more caches, more VM logic to make it’s constructs faster. This happens far more infrequently than:
• Ruby code improvements. This happens quite often, because we have so many people working in the kernel. These kinds of improvements will get us a long way, but not the entire way to 1.8 performance. That’s where VM improvements help.

Again, he brings up the sizes of the VM in comparison to the kernel. This will be the last time I address this in this post. Ruby is a dynamic language, which boasts a very rich, featureful kernel. It’s syntax and constructs allow for short, succinct algorithms.
So while, yes, the kernel is the same number of lines as the VM, it’s not unreasonable to say that it probably constitutes 10x the functionality. This is because the written Ruby code is shorter and easier to understand. That’s the whole point of this project, to make the core of it easier to work on and evolve.

Compatibility is not going to be a problem for Rubinius. They’ve worked very hard from the beginning to match Ruby behavior, even launching a Ruby specification suite project to officially test that behavior using Ruby 1.8 as the standard. I have no doubt Rubinius will be able to run Rails and most other Ruby apps people throw at it. And despite Evan’s frequent cowboy attitude to language compatibility (such as his early refusal to implement left-to-right evaluation ordering, a fatal decision that led to the current VM rework), compatibility is likely to be a simple matter of time and effort, driven by the spec suite and by actual applications, as people start running real code on Rubinius.

A quick personal response to a personal attack. I never once refused to implement left-to-right evaluation ordering, this is a bald faced lie. It’s totally true that Rubinius today is right-to-left, because that was much easier to implement way back in the day when the project began. As we started to work on ActiveRecord, we found that there was code that appear to depend on left-to-right ordering, so I brought it up with matz. And now I’m in the midst of changing it. Truth be told, I should have done my research back when the project started, it would have been easier to fix this then than now.

But I take issue with Charles statement that I’m operating fast and loose with language compatibility. We have an awesome team working on RubySpecs, which will end up being a definitive reference for 1.8 behavior. I will always be the first one to defend their behavior, and get Rubinius implementing it properly.

That’s not to say that Rubinius in the past has made temporary pragmatic decisions in implementation. We absolutely have, and in time those are corrected.
Perhaps Charles mistakes my pragmatism and Montana upbringing for a cowboy attitude.

Performance is going to be a much harder problem for Rubinius. In order for Rubinius to perform well, method invocation must be extremely fast. Not just faster than Ruby 1.8 or Ruby 1.9, but perhaps an order of magnitude faster than the fastest Ruby implementations. The simple reason for this is that with so much of the core classes implemented in Ruby, Rubinius is doing many times more dynamic invocations than any other implementation. If a given String method represents one or two dynamic calls in JRuby or Ruby 1.8, it may represent twenty in Rubinius…and sometimes more. All that dispatch has a severe cost, and on most benchmarks involving heavily Ruby-based classes Rubinius has absolutely dismal performance–even with call-site optimizations that finally pushed JRuby’s performance to Ruby 1.9 levels. A few benchmarks I’ve run from JRuby’s suite must be ratcheted down a couple orders of magnitude to even complete.

He’s absolutely correct. We have a ways to go, but I don’t believe we can’t get there. Others before us have made it work, and I think so shall we.

And the Rubinius team knows this. Over the past few months, more and more core methods have been reimplemented in C as “primitives”, sometimes because they have to be to interact with C-level memory and VM constructs, but frequently for performance reasons. So the “Ruby in Ruby” implementation has evolved away from that ideal rather than towards it, and performance is still not acceptable for most applications. In theory, none of this should be insurmountable. Smalltalk VMs run significantly faster than most Ruby implementations and still implement all or most of the core in Smalltalk. Even the JVM, largely associated with the statically-typed Java language, is essentially an optimized dynamic language VM, and the majority of Java’s core is implemented in Java…often behind interfaces and abstractions that require a good dynamic runtime. But these projects have hundreds of man-years behind them, where Rubinius has only a handful of full-time and part-time enthusiastic Rubyists, most with no experience in implementing high-performance language runtimes. And Evan is still primarily responsible for everything at the VM level.

Of course, it would be folly to suggest that the Rubinius team should focus on performance before compatibility. The “Ruby in Ruby” meme needs to die (seriously!), but other than that Rubinius is an extremely promising implementation of Ruby. Its performance is terrible for most apps, but not all that much worse than JRuby’s performance was when we reached the Rails singularity ourselves. And its design is going to be easier to evolve than comparable C implementations, assuming that people other than Evan learn to really understand the VM core. I believe the promise of Rubinius is certainly great enough to continue the project, even if the perils are going to present some truly epic challenges for Evan and company to overcome.

Thank you for the kind works of encouragement Charles. We’re getting there.
I want to say briefly as well that Charles and I are good friends, I just wanted to clear the air slightly and get everyone on the same page.

Kali ini saya akan membawakan tutorial Ruby on Rails sederhana tentang bagaimana menyimpan data sekaligus banyak. Saya tidak akan membahas sejarah semenjak apa itu ruby, kemudian juga saya tidak akan menjelaskan disini bagaimana cara instalasi ruby maupun ruby on rails itu sendiri, karena semua sudah jelas dibahas di Situs Resmi Ruby Indonesia maupun bila masih ada yang kurang jelas tentu segala lapisan masyarakat Indonesia berikut seluruh anggota-anggota yang berada di luar negeri pun boleh berdiskusi belajar bersama di milis ID Ruby.

Baiklah, kita mulai saja. Pertama buka Konsole nya (Kalau Linux), buka Terminalnya (Kalau Mac OS X), buka cmd (klik Start , klik run , ketik cmd , tekan enter | kalau Windows).

Masuklah ke direktori tempat belajar favorit Anda, lalu ketiklah perintah mesra ini:

rails countries

Seperti biasa, selalu tekan enter setelah perintah apa pun juga di komputer ya.

Kemudian masuk ke direktori countries ataupun nama project yang baru Anda beri nama tadi.

cd countries

Sampai sini Anda bisa periksa dengan perintah script/about (bila Anda memakai windows, selalu sertakan ruby script/about) saat ini saya sedang memakai gem terbaru, ruby versi 1.8.6 patch ke 111, dan rails 1.2.2 dari gem.

Saya selalu terbiasa berlatih diri dan mengantisipasi teknologi baru dengan menggunakan rails edge, caranya sebagai berikut (ya, Anda ikuti juga ya, prinsipnya semua gampang, tidak ada yang tidak bisa, yang ada, adalah, tidak mau):

rake rails:freeze:edge

Kemudian dari situ Anda tunggulah sebentar, boleh minum minum dulu boleh makan makan dulu sembari menunggu rails versi terbaru banget ini selesai didownload dan dipasangkan otomatis di direktori countries Anda itu. Lama tidaknya bergantung dengan kecepatan koneksi Internet yang Anda punya tentunya.

Sambil nunggu freezing kalo lama, sambil dengar/nonton lagu toxic Britney asik juga sambil koding (click for its source). yup, along with its jap translation for friends who also like jap like me. thanks to someone who uploaded it on Google! Domo arigato, omoshiroi na kore.

And this one ((AMV) Naruto – Linking Park – Numb – Neji & Hinata) thanks to someone who uploaded it on Google! Merci.. / iya, taunya baru merci doang -_-

Kemudian bila sudah, selalu pasang rspec. Caranya:

script/plugin source svn://rubyforge.org/var/svn/rspec/trunk/

script/plugin install rspec

script/plugin install rspec_on_rails

Awas, sekali lagi, saya disini tidak akan membahas apa dan bagaimana itu rspec, pokoknya kalau tidak jelas dengan rspec ini bisa langsung tanyakan dan belajar langsung bersama teman-temannya juga yang sama-sama sedang belajar di milis ID Ruby.

Oke. Semua plugin yang biasa saya pakai sekarang sudah ada. Tinggal kita pakai sekarang:

script/generate rspec

Ya, sudah selesai ya, kalau belum atau ada yang salah-salah ada yang error jangan malu bertanya ya, malu bertanya sesat di jalan.

Komputernya sudah berasap asap belum? Sepertinya ada yang kelupaan, apa coba?

svn? Nggak… Kita pakai git aja

Caranya gouampang

git init

enter

Awas, kalau dapat error bilang, malu bertanya ya tidak sampai sampai tujuan atau bisa juga sampai tujuan tapi berkelok-kelok sementara ada yang sampai tujuan hanya dalam kurun waktu kurang dari sekejap mata.

Lanjut, ketik lagi:

vim .gitignore

lalu di dalam editor vim tercinta itu ketikkan makhluk makhluk yang ingin dicuekin sebagai berikut:

(sebelum mengetik di vim caranya tekan huruf ‘i’ tanpa tanda petik)

db/schema.rb
db/*.sqlite3
config/database.template.yml
tmp/*
log/*
public/photos/*
vendor/*

cara keluar dari vim ketik

(atau kalau dibaca : ‘titik dua’ lalu tekan huruf ‘x’)

sudah.

Kita lanjut

Sekarang setelah diinisiasi, kita masukkan file file project nya ke repo git lokal kita.

git add .

iya, sekarang tinggal kita commit

gca

lalu di dalam editor tercinta Anda itu, ketik

commit pertama!!!

oops, kalau Anda dapat error gara-gara gca, ya berarti belum pasang alias di bash Anda. Caranya ya pakai cara panjang saja dengan perintah git commit -a -m “commit pertama!!!!”

Bila sudah. SELAMAT! Anda telah sukses punya repositori lokal git

Silakan dilanjut untuk selalu testing testing ya untuk kemudian koding.

Ketikkan perintah ini untuk membuatkan kerangka kerja yang akan dipakai untuk model country:

script/generate rspec_model country name:string special:boolean

Kemudian perintah berikut ini untuk otomatis membuatkan tabel countries sesuai dari kerangka kerja yang barusan saja kita berikan di perintah ruby sebelumnya tadi:

rake db:migrate –trace

duh jangan merinding atau takut macam-macam, ini bukan film suster ngesot ataupun pemblokiran sumber daya sumber daya penting di Indonesia oleh perampok perampok yang insyaf disaat mereka menghembuskan nafas terakhirnya, tapi sengaja membiasakan agar terbiasa dengan pesan-pesan cinta dari rake secara khusus, dan dari ruby secara umum.

Lanjut, kalau sudah boleh Anda periksa status database schema Anda dengan perintah berikut:

script/about

atau kalau mau lebih spesifik caranya dengan perintah sebagai berikut:

rake db:version

Kalau mau intip intip dulu boleh:

ls spec/models

cat spec/models/country_spec.rb

oke, saatnya kita memanggil editor textmate tercinta itu. Cukup ketikkan:

e

Awas, itu shortcut di laptop saya sendiri [-( triknya itu cuma alias aja dari mate kemudian direktori apa yang diperlukan untuk dibuka, supaya tetap ringan (walau biar dibuka semua juga ringan kok, ini karena alasan narsis pribadi penulis saja)

ih

Ada yang kelupaan lagi ya? Ada!

autotest

Nah kalau di background jalan terus autotestnya baru boleh kita balik lagi ke textmate ya, buat yang nggak pakai mac, ya bisa pakai alternatif lain, misalkan radrails ini sih saya taunya ketika zamannya saya dulu belajar rails sih, kalau yang sekarang sedang hot saya sudah kurang mengikuti berhubung saya memang cuma pakai tiga editor aja (ViM, Emacs sama TextMate / disesuaikan mood sama kebutuhan sama kemampuan juga sih).

Nah sekarang kita mau ngapain nih?

Lha ini mbikin tutorial kok pakai nanya-nanya? mungkin gitu kata pengamat yang ingin meralat saya karena perhatian yang sangat. Bukan ...... ini cuma ingin membiasakan pembaca yang memang sedang belajar saat ini untuk berpikir lurus, ehm, bukan berpikir berkelok-kelok dan tersesat.

Berpikir test dulu, baru kemudian codes!

Kalau berpikir test, pasti berpikir tentang requirement spesifikasi apa yang diinginkan bisa berjalan di program.

AHA!! Anda ingin kita bikin tabel countries ini harus punya nama! Kan nggak ada pak, negara tanpa nama, ah itu sih nanti bisa gak habis habis kalau bicara OOT ke politik lagi soal negara tanpa nama tapi mencengkeram sih serahkan pada yang lebih ahli saja daripada penulis yang newbie forever inih. piss. Shi Bubeng Pendekar Tanpa Nama (Nah kalau yang barusan ini asli nama Pendekar Tanpa Nama tulisan Kho Ping Ho, nah kan kita kena virus OOT, huh)

Ayo fokus, kembali lagi ke topik...

Jadi kita akan bikin spesifikasi negara harus punya nama!

Ah dari tadi bicara spesifikasi spesifikasi spesifikasi terus, ayo dong diimplementasikan coding lagi jangan banyak bacot mulu' ... lha, ini supaya terbiasa, kalau mengigau spesifikasi spesifikasi spesifikasi di ruby apa rubinius .... aduuh jangan OOT ke rubinius dulu dong, fokus dong fokus... baru belajar neh! (hajar yang nghajar mainan mulu') langsung ingatnya spec spec spec .... iya, pakainya rspec !

caranya:

require File.dirname(__FILE__) + '/../spec_helper'

describe Country do
  before(:each) do
    @country = Country.new
  end

  it "should require a name field" do
    @country.save.should_not be_true
  end
end

iya, jadi yang asalnya should be valid itu Anda hapus saja ya. Ganti sama yang Anda perlukan aja. Anda mungkin bertanya, lho kok nggak ada fixture ? Lha memang karena kita tidak butuh.

Sambil simpan file spec/models/country_spec.rb tsb Anda boleh sambil intip gerakan gerakan bawah tanah hacker hacker di konsole/terminal Anda (haha ini hanya untuk mendramatisir saja apa apa yang berderau di panggung jengking teruk sangat itu, belajar kalau monoton itu itu saja kurang masuk, malah tidur, kalau ini, kalau pusing, takut tanya sama mas arie, ya alamat dikasih selamat kebingungan sendiri, salah sendiri sudah ditawari tanya lagi kalau masih bingung setelah baca masih sungkan sungkan gak pede mau tanya doang).

ya autotest di balik layar Anda itu bergerak gerak menandakan ada yang tidak benar, ya tentu saja, karena memang kita baru menuliskan spesifikasi spesifikasi yang menjadi requirement/kebutuhan si jelita yang ingin dibikinkan oleh Anda sebagai jockey, ehm (ngelirik yang mahasiswa ahyo hari gini nyontek? ama joki?) -_-

Argh sekarang kita lanjut implementasikan satu baris kode validasi harus ada itu tadi. Harus ada apa? Nah lo barusan dibahas udah lupa lagi ... kebanyakan OOT kali neh .. ya harus ada nama buat negara .

ini copy paste dari file app/models/country.rb

class Country < ActiveRecord::Base
  validates_presence_of :name
end

Iya, pada kenyataannya Anda hanya butuh menuliskan satu baris validates tersebut saja, ini sengaja saya kopi kan semua supaya Anda yang baru belajar jangan ragu-ragu atau takut salah, karena ragu-ragu dan takut salah itu adalah pangkal dari kegagalan, bila ingin maju dan sukses, harus berpikir positif, maju terusss, pantang mundurrr, jatuh bangkit jatuh bangkit, itu biasa... merdeka!

Nah sembari Anda bergemuruh akan semangat kemerdekaan, jantung Anda pun berdegup ingin menjentik keindahan warna hijau pertana sukses rspec yang ditampakkan oleh autotest yang berjalan di balik layar itu (hidup hacker indonesia!) Lho? -_-

Oke, sampai disini ada yang ingin ditanyakan dulu nggak?

pokoknya kalau gathering ID Ruby kalo ada saya nggak boleh pasif jadi pendengar setia, harus aktif, jadi tukang protes apalagi kalau bisa menambahkan, pasti bakal disuka sama terutama yang sudah sepah sepah dan jarang turun gunung itu.

Bangsa Indonesia harus belajar untuk berpikiran terbuka, optimis, maju, terus jangan dibiasakan selalu disuapi, dijajah, hingga terbiasa ditarik ditali lubang hidung ibarat kerbau kemanapun kehendak "angin" bertiup. Bangkit Indonesia, berlari mencapai visi hakiki bukan retorika sesat! (Ih, ini paragraf hanya untuk konsumsi diri pribadi Arie saja ini buat bahan introspeksi kayaknya lumayan juga, hmm...) biasa.. belagak bijak -_-

"Pak! Tanya! Kalo saya tanya, nanti mas Arie marah gak?", tanya Sitorus.

Saya: "Ya kalau soal rails yang dibahas tadi ngapain marah Rus... Kan katanya kalau sering marah cepat tua."

...............................................................

Ya sudah titik titik panjang diatas mewakili diskusi yang lagi belajar gitu di kos kos di warung warung di sekolah sekolah di kantin kantin di mana pun teman-teman pemula rails ini sedang belajar dan bercengkerama berdiskusi membahas solusi guna mencapai pencerahan yang ingin didapat.

Ta' lere' wae soko kene.

Lanjut, setelah model sudah lewat kita jamah, sekarang kita mulai menggauli controller. Seperti biasa, kita tentukan dulu lagi spesifikasi spesifikasi spesifikasi apa aja yang ingin dibikin.... Hmmm... coba dipikir-pikir dulu.

Perlu ada :

1. Listing Countries atau Daftar Negara-Negara
2. Form buat simpan data
3. Proses penyimpanan data dan melempar alih serta pemberi status apakah sukses atau gagal

Nah dari sana, kami belajar untuk berpikir resource atau sumber daya apa yang dibutuhkan?

Bila diterjemahkan dengan Rails dan resource maka jadinya begini:

1. GET /countries
2. GET /countries/new
3. POST /countries

Jadi langsung saja kita menerkam mangsa kita satu ini yaitu file spec/controllers/countries_controller_spec.rb

Pada mulanya:

require File.dirname(__FILE__) + '/../spec_helper'

describe CountriesController do

  ##
  # GET /countries

  describe "GET 'index'" do
  end # describe "GET 'index'"

  ##
  # GET /

  describe "GET 'new'" do
  end # describe "GET 'new'"

  ##
  # POST /countries

  describe "GET 'create'" do
  end # describe "GET 'create'"
end

Kemudian simpan, Bim salabim.... Byur Byur.... Ijo... ijo.... ijo.... (Tanda rspec sukses) Nah ini bukan menganjurkan praktek perdukunan, kami hanya menganjurkan yang positif saja, maksudnya kalau yang lagi belajar termasuk programmer yang nggak suka ato jarang mandi, jangan lupa mandi dulu sana!

Buat yang bukan programmer baca ini, jangan ketawa atau tersinggung lho, emang betul tu ada lumayan lho yang kelakuan saking gak mau pindah meninggalkan komputernya sampai gak mau bangkit dari tempat semedinya hanya untuk mandi sebentar.

Sudah OOT jangan kelamaan, ini tulisan jadi melorot nanti -_- terang aja tadi ijo soalnya memang belum ditulis apa-apa specnya. itu baru kerangka.

Sekarang coba kita mulai isi:

....

Setelah 1/2 detik penulis berpikir barusan, tahap demi tahap copy paste dicancel karena watak penulis yang gak sabaran, jadi langsung di copy paste kan keseluruhan isi file spec, kemudian juga seluruh isi file controller, bila yang ingin bertanya lebih lanjut, bisa didiskusikan kalau memang bertemu dengan Arie sendiri ataupun boleh lewat komentar atau lewat milis terserah.

require File.dirname(__FILE__) + '/../spec_helper'

describe CountriesController do

  ##
  # GET /countries

  describe "GET 'index'" do
    before do
      @country   = mock_model(Country)
      @countries = [ @country ]
      Country.stub!(:all).and_return(@countries)
    end

    it “should render template index” do
      load_page
      response.should render_template(:index)
    end

    it “should assign a listing countries” do
      Country.should_receive(:all).and_return(@countries)
      load_page
    end

    it “should route for GET /countries” do
      route_for(:controller => “countries”, :action => “index”).should
        be(“/countries”)
    end

    def load_page(params={})
      defaults = {}
      get :index, defaults.merge!(params)
    end
  end # describe “GET ‘index’”

  ##
  # GET /

  describe “GET ‘new’” do
    it “should render template new” do
      load_page
      response.should render_template(:new)
    end

    it “should route for GET /countries/new” do
      route_for(:controller => “countries”, :action => “new”).should
        be(“/countries/new”)
    end

    def load_page(params={})
      defaults = {}
      get :new, defaults.merge!(params)
    end
  end # describe “GET ‘new’”

  ##
  # POST /countries

  describe “GET ‘create’” do
    before do
      @params = [
                  { "name" => "Indonesia" },
                  { "name" => "Malaysia" },
                  { "name" => "Filipina" },
                ]
      @country = mock_model(Country)
      Country.stub!(:create!).and_return(true)
    end

    it “should directly create! (set and save) all countries ready to save” do
      Country.should_receive(:create!).with(@params).once.and_return(true)
      load_page
    end

    it “should assign a flash notice and redirect to index upon success” do
      load_page
      flash[:notice].should_not be_blank
      response.should redirect_to(countries_url)
    end

    it “should render back template new upon failure” do
      @country.errors.stub!(:full_messages).and_return([])
      Country.should_receive(:create!).and_raise(ActiveRecord::RecordInvalid.
                                                   new(@country))
      load_page
      response.should render_template(:new)
    end

    it “should route for POST /countries” do
      route_for(:controller => “countries”, :action => “create”).should
        be(“/countries”)
    end

    def load_page(params={})
      defaults = { :country => @params }
      post :create, defaults.merge!(params)
    end
  end # describe “GET ‘create’”
end

Kemudian file controllernya:

class CountriesController < ApplicationController

  ##
  # GET /countries/new

  def new
  end

  ##
  # POST /countries

  def create
    Country.create!(params[:country])
  rescue ActiveRecord::RecordInvalid
    render :action => :new
  else
    flash[:notice] = "Successfully saved!"
    redirect_to countries_url
  end

end

Hm, kemudian sekarang spec view-nya new:

require File.dirname(__FILE__) + '/../../spec_helper'

describe "/countries/new" do
  it "should display a title New Countries" do
    render 'countries/new'
    response.should have_tag("h1", "New Countries")
  end

  it "should display a form to submit multiple new countries" do
    render 'countries/new'
    response.should have_tag("form[action=?][method=post]", countries_path) do
      20.times do |i|
        with_tag("input[name=?]", "country[][name]")
      end
      with_tag("input[type=submit]")
    end
  end
end

Anda Capek nyalin ngetiknya? Kayaknya saya yang sekarang sudah mulai mengantuk setelah dinina bobokan dengan posting blog saya kali ini ... uh. (Lama gak dipijit / pegel2x huhuhu)

Dan ini view new nya. app/views/countries/new.html.erb

<h1>New Countries</h1>

<%= error_messages_for :country %>

<% form_tag "/countries", :method => :post do %>
	<ol>
		<% 20.times do |i| %>
			<li>
				Name :
				<%= text_field_tag 'country[][name]' %>
			</li>
		<% end %>
	</ol>
	<p>
		<%= submit_tag "Save!" %>
	</p>
<% end %>

Ini sekarang spec viewnya index

require File.dirname(__FILE__) + '/../../spec_helper'

describe "/countries/index" do
  before do
    @country = mock_model(Country,
      :name => "Indonesia")
    @countries = [ @country ]
    assigns[:countries] = @countries
  end

  it "should display a title Listing Countries" do
    render 'countries/index'
    response.should have_tag("h1", "Listing Countries")
  end

  it "should list countries" do
    render 'countries/index'
    response.should have_tag("li", @country.name)
  end

end

Dan ini isi dari codes viewnya index app/views/countries/index.htmlerb

<h1>Listing Countries</h1>

<ol>
	<% @countries.each do |country| %>
		<li><%= country.name %></li>
	<% end %>
</ol>

Lho lho lho? Anda jadi cemberut gitu tadi pada ngikutin dengar sabar postingan ini ngeliat saya ngantuk baru bisa akan tidur? Mustinya ikut senang dong, daripada saya nggak bisa tidur tidur hayo -_- Rasanya nggak enak lho kalo mo tidur musti macem macem dulu...

"Pak Arie! Dari tadi saya selalu lihat code code menakutkan dan konsole/terminal hacker itu pak, kapan saya boleh pegang mouse pak? kapan saya boleh tes di browser langsung untuk melihat apakah aplikasi saya bisa dipakai dan berjalan atau belum", Sitorus protes.

Saya jawab, "Oh iya, ya silakan, tinggal Anda ketik script/console lalu buka browser Anda, ketik localhost:3000/countries/new . Nah sudah disana Anda tinggal ketik."

Udah saya mau tidur dulu.

ps. Buat para sesepuh penasihat Arie yang sangat mendukung Arie menulis dengan sangat sangat sangat sangat sangat....... dimohon masukannya dan obatnya agar Arie bisa menulis sampai selesai secara step by step (request, tutorial juga, jangan langsung satu malam sekali belajar tapi abis gitu langsung sakit masuk angin trus mencret mencret kalo itu mah bukannya belajar tapi penyiksaan tuh, tapi learning by doing satu per satu yang penuh kasih sayang, please)

ps. Buat yang benar-benar sedang belajar rails, kalau ada kata-kata yang kurang berkenan, kami mohon maaf, itu semua semata-mata hanyalah ilusi seorang gembel sebelum tidur.

GLODAK!

Baru saja kepalaku terantuk ke dinding ! lupa commit dulu git nya. Ayo git, kita commit .. ah mau nonton rake spec dulu ya, boleh:

m:spike_multiple_array_form_save arie$ rake spec
(in /Users/arie/spikes/spike_multiple_array_form_save)
...............

Finished in 0.340209 seconds

15 examples, 0 failures
m:spike_multiple_array_form_save arie$ rake stats
(in /Users/arie/spikes/spike_multiple_array_form_save)
+----------------------+-------+-------+---------+---------+-----+-------+
| Name                 | Lines |   LOC | Classes | Methods | M/C | LOC/M |
+----------------------+-------+-------+---------+---------+-----+-------+
| Controllers          |    38 |    19 |       2 |       3 |   1 |     4 |
| Helpers              |     5 |     4 |       0 |       0 |   0 |     0 |
| Models               |     3 |     3 |       1 |       0 |   0 |     0 |
| Libraries            |     0 |     0 |       0 |       0 |   0 |     0 |
| Model specs          |    11 |     9 |       0 |       0 |   0 |     0 |
| View specs           |    39 |    33 |       0 |       0 |   0 |     0 |
| Controller specs     |    99 |    75 |       0 |       3 |   0 |    23 |
| Helper specs         |    11 |     7 |       0 |       0 |   0 |     0 |
+----------------------+-------+-------+---------+---------+-----+-------+
| Total                |   206 |   150 |       3 |       6 |   2 |    23 |
+----------------------+-------+-------+---------+---------+-----+-------+
  Code LOC: 26     Test LOC: 124     Code to Test Ratio: 1:4.8

m:spike_multiple_array_form_save arie$

Ya sudah ya sudah sekarang betulan mo tidurrr

git commit -a -m "listing countries and adding multiple countries have been added"

ini source code nya ada di laptop ini, nanti kalo dah nggak ngantuk akan saya update buat taroh dimana gitu akan saya update lagi, ah mulai ngaco nih ampe gw nulis sambil mata penuh air. udah oyasumi.

tut.. tuing.. tuing. .. zzzzzzzzzz

[vim] Why I emphasize “know your editor well, don’t just use it because of nothing or popularity”, cos once we “know” our editor, it can increase productivity.

The first long one gives me nice status bar, but only if I :split my vim. (I always use :spl and :vspl, ex. my code is at the top and the rspec code at the bottom vim, I probably will do :! to execute command automatically from ViM [Lazy to move around again if I'm already inside ViM])

set statusline=%F%m%r%h%w\ [FORMAT=%{&ff}]\ [TYPE=%Y]\ [ASCII=\%03.3b]\[HEX=\%02.2B]\ [POS=%04l,%04v][%p%%]\ [LEN=%L]
set nowrap
set backspace=indent,eol,start
set nu
set history=50		" keep 50 lines of command line history
set ruler		" show the cursor position all the time
set showcmd		" display incomplete commands
set incsearch		" do incremental searching

I got codes below from vimrc examples, so it’s easy to do :r or just copy paste if I use Textmate/or emacs (anyway). It’s handy so vim will detect automatically what type of file currently being edited.

" Only do this part when compiled with support for autocommands.
if has("autocmd")

  " Enable file type detection.
  " Use the default filetype settings, so that mail gets 'tw' set to 72,
  " 'cindent' is on in C files, etc.
  " Also load indent files, to automatically do language-dependent indenting.
  filetype plugin indent on

  " Put these in an autocmd group, so that we can delete them easily.
  augroup vimrcEx
  au!

  " For all text files set 'textwidth' to 78 characters.
  autocmd FileType text setlocal textwidth=78

  " When editing a file, always jump to the last known cursor position.
  " Don't do it when the position is invalid or when inside an event handler
  " (happens when dropping a file on gvim).
  autocmd BufReadPost *
    \ if line("'\"") > 0 && line("'\"") <= line("$") |
    \   exe "normal g`\"" |
    \ endif

  augroup END

else

  set autoindent		" always set autoindenting on

endif " has("autocmd")

[rubinius] untuk yang sering lupa akan nama-nama dari simbol simbol di bahasa pemrograman apa aja, terutama ruby dalam hal ini, bisa lurking di bin/name_map.rb . BTW kalau di buku buku tertentu di Indonesia “lucu” juga itu comparison disebut-sebut operator “ufo” (kalau pernah baca satu dari sekian buku perl disana)

[search from many multiple files at once in vim] it’s just from my feeling. doing shift command f inside textmate or doing grep on bash just feels the same. running grep from terminal as heavy as inside textmate. cmiiw pls (especially with bin/time and/or any benchmarking numerics result), but this one was fast, whoop…, i don’t know why

:vimgrep /redirect_to/ /Users/arie/Projects/eee/app/controllers/*.rb

oh we can do :clist to display all of our search results, or just :cnext or :cprevious to know where the result files are.

[more-vim] haha now what do you need more arie? instead of that textmate shit? oh, (1) automatic completion argh i don’t know yet about this one, i read blog posts from googling around but i still can’t get it worked beautifully. oh, i got :rub as well, nice, but i don’t think i really need that advanced feature so i just disable them (yes, including lisp, tcl, perl, python for executing commands inside vim), maybe just later when I can do scripting heavily in vim. (2) tab but not to click as i hate mouse, just call in somehow from command would be nice, i once seen this trick somewhere from rails wikibut after i tried to follow that, i couldn’t get it worked, don’t know about the progress nowadays, hey anyone has tried that? just share it with me.

[cross-culture] hm blond people who are surrounding me usually say : “See you” without looking in the eyes. Oh Malay also usually say “Thank you, come again” in Japanese but with “weird” expressions in Japanese restaurant (arigatou gozaimasu… mata). Weird Meaning they do that while cleaning dishes, bringing plates and glasses, walking around without looking at my eyes but it’s fine (compared to Melbourne people).

[Indonesian Grammar] whenever we want to put “ing” after a verb, like blogging, dancing, dating, we just replace that “ing” to be “nge” appended before the verb, so the result is : ngeblog, ngedance, ngedate, etc

[non-geek yang kuhormati] dia datang, lalu bertanya, gimana caranya supaya gampang ke revision ke-n, dijawab, coba kalau kamu nggak keberatan pake textmate, kamu bisa tinggal tekan control shift a, lalu diotomatiskan di textmate sana. Ditanya lagi, gimana caranya supaya aku bisa download source code programmu supaya aku bisa edit copy write nya. dijawab kamu buka terminal, trus ketik perintah ini svn co svn://alamate/projectname. kukirim ke skype mu ya. dan dia pun berlalu setelah berterima kasih. beuh…

[amerikana] duh makin banyak aja londo amrik disini, bahasa inggrisku bisa tambah variasi aja nanti nih[f]

[ruby migration] selain data mapper yg main hapus saat rake dm hingga tetap aja satu satu peraturan nomor 51 lakukan ini lakukan itu, kapan ngeliat migration yang bersih

[ruby migration] walau diawali dengan mencoba mereplika bug di localhost dan fine fine terus dan hati makin kesal berbulu bulu gorila tapi tangan ini juga terasa gatal dan berdarah darah arghghghgh kalau kusabar-sabarkan replikasi dari database di culik boleh juga kalo gak sampe puluhan giga satu tabel -_- (pret!)

[ruby migration] (500 records) boom boom boom boom boom! manisnya… gini nih kalo kekurangan integration testing! Idealisme seorang tukang koding emang sering gak bersesuaian dengan idealisme kenyataan hidup , sidenote makanya dulu dulu salah sendiri kenapa tolol koding bego gitu, coba pakai yang bersih kan gak ngomel2 gini!

[ruby migration] tambah manis! testing 2 environment, satu jebolan server, satu karangan piktip! rghghgh harakiri!

[ruby migration] jutek butek butek!!! ghrlrlrlr…

[marketing said?] people use facebook, less and less use email??? argh disagree! i know facebook has been increased rapidly, myspace, but I don’t think it’ll change people habit using email. Facebook email thing sucks! you know what, it doesn’t support draft automatically saved like Gmail. Don’t say this is a crazy technical thing or something like that (I even don’t start talking about session or any data sent through the net with ajaxy things yet), imagine this scenario, what if I want to write an email draft first i don’t want to send that draft immediately, i can’t do that in facebook! write it in my own happy chappy ViM Editor for email is a big no no cos I’m always online. Oh you hate Gmail because it doesn’t support things you had in Yahoo Mail? true! Gmail also sucks =)) I even tend to remove my friendster account, but whenever i want to remove it, i cancel it, because i see many indonesian people over there, but i never used friendster email (friendster email bloody suck!) i don’t use email on facebook unless i’m forced/like if i forgot my friend’s email). Ujung-ujungnya ngomel berlanjut: semuanya suck! =)) loncat – njengking – rekursif. Seriously, if you still remember about facebook regulation, it really sucks!! links: go to wikipedia search facebook and trace from there!

[textmate shortcut of the day] command alt zero (yes, 0, not O letter) to fold and unfold.

[ruby open id] jadi ceritanya melakukan penelitian ruby open id selama 2 jam? kata orang terpintar se Indonesia : Gitu aja repot????? tinggal comot dari beast aja udah tinggal pakai =)) Hus! sama sekali jangan percaya! Blogger kan penipu !! Jadi pokoknya kalo yang curhat nulis di blog = penipu. Trus ada kalo lagi jalan-jalan trus bikin catatan perjalanan = penipu. Ada ahli masak bikin tips masakan enak = penipu. Ada orang belajar bareng temen-temennya di blog biar keliatan jatoh bangun sama salah-salahnya dengan polos = penipu. Aiyyou pandainya yang cakap tu jer.

[plugin VS rubygem] matilah kau plugin, hiduplah kau rubygem. Lho jadi kemarin2x baru belajar itu acts_as_authenticated? duh… jadi sudah jadi restful_authentication gitu ya? jadi kalo dari file column , trus kan acts as trus jadi attachment fu, trus jadi hula hula. Lha kalo konsep ekstensi di radiant kan bagus toh meningkatkan produktifitas, tinggal tempel 1 jam, jadi, kok jadi rubygem sih… bah jangan percaya blogger penipu!!! sontoloyo! simelekete! (To Non Indonesian who can guess around the context and read Indonesian news, this is what you’ve got to Indonesian flavour -_-V Indomie … seleraku )

[man -M .] man -M . git-fetch inside git repo / but remember to git checkout head/man first. just like when we play around with git checkout head/html so git manual will be available locally

[linggis:ecommerce bandel] ngomong2 soal bandel, bandel itu kalo di Engdonesah artinya bandel bu’li’ (disono orang-orang nyebutnya bundel) -_-

[linggis:dilit] ya bacanya delete jadi dilit (boso jowo: sedilit = sebentar sinonim sama satu vocab lagi gw lupa tadi barusan uda di lidah padahal). sama kayak login kalo di indo sering banyak yang pronounce lojin.

[ruby shell = rush] wah yang kuat sama networking trus sama yang low low sama operating system bagus nih main ginian! daripada “turun derajat” dengan bash ato bermain perl oneliner yang gampang banget ditulis dan tak akan pernah ingin dibaca (kaburrr….)

[milis] mo nanya, tapi gak tau cara nanyanya. masalahnya tau, tapi nanti kalo ngomong nggak tau cara nyampaikannya. jadi gak jadi nanya. yaah. ada lagi, mo nanya, tapi gak tau judulnya apa, sama nggak tau namanya apa, pokoknya yang dipengenin tuh gini (sambil demokan di komputer), dah itu, gimana caranya dari gitu sampai jadi gitu. jadi gak jadi nanya. yaah. =)) itulah makanya perlu ada ketemuan offline yang gak selalu online, jadi kan bisa belajar bareng.

[wong ayu ngguyu] ne’ wong ayu ngguyu iso ngono yo -_-

[wong ayu bersin] ciii cii.. beuh bersin batuknya wong ayu ngono yo, kapan jadi jeleknya…

[ngguyune wong jerman] zukh auf gedebag gedebug yang nguing nguing gedebag gedebug kik kik ngak ngak ngak wuh wah wuh wah (hih nggak berenti2x s/d dipijat2 s/d pulang dari toilet s/d duduk nyambung lagi, bah kehabisan oksigen bisa berabe tuh).

[obat sambil koding sambil cegukan] orang finlandia bukan cuma bakat mbikin hengpon nokia tapi ternyata juga bisa ngajarin supaya bisa sembuh dari cigukan =)) kesian kali tu bule ngeliat gw sambil koding sambil cigukan mulu’ udah smbil minum kopi panas masih juga… dikasitau caranya tarik napas dalam dalam simpan semua nafas itu trus tahan napas. trus keluarkan/hembuskan perlahan2, udah gitu pas gw praktekin sembuh betulan =)) paten ! =)) linggisnya hickup hikup atau apa gitu deh..

[orang bule gak bisa ribut?] bunyi tut! tut! gempar udah =)) naik lift kalo gw begerak, gempar udah! =)) mungkin belum pernah ketemu banjir sama kalo kebakaran rame rame panik atau pas gempa atau pas mati lampu atau pas ada bom atau pas ada bangunan gede jatoh trus kepalanya putus kayak di Jakarta dulu itu, brakkk… beuh jadi horor gini. sadis sadis bawaan orang indo -_-

[alias method and alias] alias method must be inside a class. alias could be anywhere, i found there 3 difference about them, now i forgot where i read them … oh peepcode.. but anyway, here’s my irb copy paste:

m:code arie$ irb
>> def foo; 'hi'; end
=> nil
>> alias :bee :foo
=> nil
>> bee
=> "hi"
>> alias_method :new_foo, :foo
NoMethodError: undefined method `alias_method' for main:Object
	from (irb):4
>> Object.respond_to?("alias_method")
=> false
>> Class.respond_to?("alias_method")
=> false
>> class Coba
>> end
=> nil
>> Kernel.respond_to?("alias_method")
=> false
>> class Coba
>>   def foo; 'hi'; end
>>   alias_method :new_one, :foo
>> end
=> Coba
>> c = Coba.new
=> #
>> c.new_one
=> "hi"
>> exit
m:code arie$ 

ya awalnya gw ngotot metode-metode yang ada tsb kan berada dalam Object, lha si Object kan mbahnya si Object di Ruby. Tapi tetap, harus berada di dalam class. Kalau baca manual ri tentang alias method merupakan metode dari Module mixin.

[menghargai waktu] kutanya ke bule eropa, apakah orang-orang di eropa berjalan secepat kamu? dijawab, ya, kisaran gw di peringkat 20 lah, bahkan kalo gw jalan sendiri bisa lebih cepat! # Kalau aku mulai berpikir, beuh dasar orang di negara maju gila, aku akan berpikir/introspeksi dengan cara terbalik, hm, sebetulnya mereka yang cepat atau saya yang lambat -_- busssseeeetttt ni dibelakang begerak kayak Flash gitu sih!!!

[trik menghindar dari yang blank soal IT] inilah obrolan di pelosok ndeso sana (yaitu sebuah desa antah barantah yang sangat tidak tepat untuk seorang yang serba dinamis dan ambisius apalagi bila berdasi dan suka terbang merayap di rel kereta, alah) eh, dia itu kamu tau kerjanya apa di Jawa ternyata kuliahnya tu komputer aja tu liat sekarang dia pengangguran. kuliahnya dulu soalnya cuma komputer!

[mud] nggak sabar nunggu libur biar bisa tidur istirahat lagi , capek. mo ngabisin design pattern lagi.

[mud kemis pagi] hu hu hu seneng banget jadi terharu dikasih “makasih” ama dia.

[malay grammar = lah] hm so malay english use “lah” a lot

[borokokok capistrano] cap -S stage=production deploy / kalo default cap deploy doang ke staging misalkan.

[ID Ruby] bali.rb sama bandung.rb ada nggak ya -_- bakal koding bareng tari kecak noh. cak cak cak cak. ho.. hoo.. hoo… cak cak cak cak… Lumayan kali bareng temen-temen bule koding bareng yak.

[bash doang] jadi ceritanya baru seneng seneng lagi aktip sama git nih -_- trus di copy kan ini config ke .bash_history di /Users/arie di mac, trus kalang kabut pas mo svn commit kok nggak otomatis lagi SVN_EDITOR ada di PATH, argh di mac ingetin aja kalo bash_profile bisa juga ditaroh di .profile.

alias gst='git status'
alias gl='git pull'
alias gp='git push'
alias gd='git diff | mate'
alias gc='git commit -v'
alias gca='git commit -v -a'
alias gb='git branch'
alias gba='git branch -a'

[ruby singleton jargon] kalo sering lupa sama jargon class << self di Ruby, ingat aja sama banyaknya teknik-teknik metaprogramming yang dipakai di rails seperti with_options(options) trus yield. Walau tentu perbandingan ini terasa sangat jomplang karna praktik advanced di rails (yg kembangannya bisa punya banyak opsi)

[Id-Ruby Gathering on March 8th, '08] with Jakarta.rb tag for the second time, it’s the 6th id-ruby gathering in Indonesia. There will be an announcement on Facebook as well. Reminding date was set at Google. Enjoy! UPDATE: This is the facebook link for this event

[This Weekend] sleeping, continue reading design patterns book (again), continue lurking on rubinius spec files, hopefully will join the roll ASAP, just looking at cute cats in midvalley (but still design patterns + rubinius + new peepcode series are more crucial for me!).