On Sun, Apr 11, 2010 at 1:33 AM, Chuck Remes <[email protected]> wrote: > [...] > > As rubinius approaches 1.0 over the next 2 weeks, we need to start getting it > working on Windows. This would likely entail some refactoring of a few I/O > classes to abstract out some platform-specific items. There are already one > or two people poking at this (on forks) so there is the possibility of some > collaboration. > > Getting rubinius to compile and run on Windows is about the right size for a > summer project. >
I would say that getting Rubinius working on Windows is a bit bigger than just a summer project, but doable. The truth is that the set of skills required to make it happen are not highly available in people wanting to work on Ruby, or are not familiar with Open Source development. As it bad it sounds, is the true. The mindset of proficient Windows developers is not wrap around Open Source, but of course there are always exceptions to the rule. > Of course, there are other possibilities. Here's a short list... > > [...] I believe this list plays a more important role. It will be hard to port something to a different OS when certain things do not work and you don't know if is because your port, the underlying library or a broken 3rd party. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected] To unsubscribe, reply using "remove me" as the subject.
