From: Julian Browne <julianbrowne@...>
Date: 2010-09-10T02:16:19+09:00
Subject: Re: What OS do you use for Ruby development?

--0015175cb2b66a81ee048fd6c9c3
Content-Type: text/plain; charset=ISO-8859-1

I'm on the RubyInstaller mailing list too so know what you are talking
about. Great work.

Most gems issues are related to compilation as you'd expect. As far as
timeframes go I started with Rails in 2005 I think. Again, like a lot of
people, I was just looking for a web dev framework that didn't suck. Once
I'd seen the Ruby beauty as distinct from the Rails abstractions I was
pretty much hooked. FWIW I think Windows makes a fine enough dev environment
for Ruby once you get used to the lack of OS level scripting support - which
of course is way better on Mac and Linux distros. And the fact that they
represent the reference platforms so it's a little harder to live on the
edge away from them.

Anything that reduces barrier to entry is good in my book. Makes all the
difference.

On 9 September 2010 17:11, Luis Lavena <luislavena@gmail.com> wrote:

> On Sep 9, 12:53 pm, Julian Browne <julianbro...@gmail.com> wrote:
> > [Note:  parts of this message were removed to make it a legal post.]
> >
> > Like a lot of Rubyists I came to the language at the same time I got into
> > Rails. InstantRails was quite popular at the time so I defaulted to
> Windows
> > because it was just so easy to get and entire db/web server/rails
> > environment up and running. Textpad has always been a favourite editor of
> > mine so I kind of stuck with that. Even now I'll still occasionally use
> that
> > stack (XAMPP now instead of InstantRails) but it's become harder and
> harder
> > to stick with Windows as my use of specific gems has grown. I cracked too
> > eventually and went down the Mac route which is yards better.
> >
>
> Interesting and helpful response. I was wondering the timeframe on
> which you used Ruby and had these issues.
>
> You see, we develop this thing called RubyInstaller which tries to
> simplify both installation and usage of Ruby and its gems by better
> documentation and building tool kit.
>
> We can't provide packages as InstantRails, but the tools are available
> for others to package and distribute.
>
> I know, off topic, but still interested to hear that.
>
> --
> Luis Lavena
>
>

--0015175cb2b66a81ee048fd6c9c3--