What Ruby stuff will be happening at Macworld? What software is
written in Ruby, which companies are Ruby shops, will there be any
Ruby events to clear up any confusion from Rails-hype, etc?
We could likely avoid a lot of duplicitous advocacy if some people
would compile some unbiased “Why Ruby?” facts, examples, and idioms
into a Keynote presentation and export that as a quicktime file.
Then we could serve that file and point browsers to it when people
ask about Ruby. Packing that page with links to other Ruby resources
would be a convenient tool to grow the community (bookmark it for
them, then click the quicktime link and walk to the next exhibit ha ha).
Since the target audience will have advanced skills, I think
intricate examples showcasing gems, rake, C, and a lot of other foss
packages should be the goal. Make slides introducing your own
libraries and contribute them.
I’ve made a wiki page to collect notes on what should be included. I
could do the Keynote work, but I’d rather leave it to someone who’s a
guru and already has some advocacy files prepared.
Call me ambitious and optimistic, but I think the responsible
estimate is that Ruby popularity will explode this year. I think
it’s a smart move to spend some time on this now to ensure a great
and agile transition for millions of future Rubyists. Macworld will
be a good chance to further the entrenchment of two of the greatest
problem-solving tools (Ruby and Apple) by making them more familiar
with each other.
I just bought a new Mac, and its the worst dev environment for ruby
possible. I’ve put at least 5 hours (yes, 5) into getting the
ruby-mysql bindings working. And nothing gets it working. In fact,
the one mention of my error on the web says, “No known fix.” That’s
nice to hear after spending all this money! Errrrgh.
I might put linux on this box.
Linux is a great ruby environment.
I just bought a new Mac, and its the worst dev environment for ruby
possible. I’ve put at least 5 hours (yes, 5) into getting the
ruby-mysql bindings working. And nothing gets it working. In fact,
the one mention of my error on the web says, “No known fix.” That’s
nice to hear after spending all this money! Errrrgh.
I might put linux on this box.
Linux is a great ruby environment.
-hampton.
What are your specific problems?
I got a Mac to broaden my horizons, and after some initial
frustration ended up with a great environment.
Apple’s ruby installation is a little messed up, but I ended up
replacing the system readline library and building my own ruby.
There are various recipes you can find with google, as a lot of
people trying Rails wanted to develop on OS X e.g.
I seem to recall reading somewhere that MacOS X has some nonstandard
screwed-up installation defaults for MySQL that need to be
“fixed”. Is
there truth in that?
Not that I’m aware of.
You might be thinking of the fact that Apple’s install of Ruby has a
few issues. Those are easily fixed though.
On Tue, Jan 03, 2006 at 12:52:59AM +0900, James Edward G. II wrote:
On Jan 2, 2006, at 9:47 AM, Hampton wrote:
I just bought a new Mac, and its the worst dev environment for ruby
possible.
I’ve used a Mac for Ruby development since day one and I couldn’t
disagree more.
I also use MySQL with no trouble so I encourage you to start a new
thread about your problems and let us help you get it running…
I seem to recall reading somewhere that MacOS X has some nonstandard
screwed-up installation defaults for MySQL that need to be “fixed”. Is
there truth in that? Might that be Hampton’s issue?
I just bought a new Mac, and its the worst dev environment for ruby
possible. I’ve put at least 5 hours (yes, 5) into getting the
ruby-mysql bindings working. And nothing gets it working. In fact,
the one mention of my error on the web says, “No known fix.” That’s
nice to hear after spending all this money! Errrrgh.
On Tue, Jan 03, 2006 at 05:03:49AM +0900, James Edward G. II wrote:
few issues. Those are easily fixed though.
Okay, thanks for the clarification.
I keep flirting with the idea of getting a Mac in here, but keep
discarding it with the realization that A) I probably wouldn’t use it
much and B) I still don’t like one-button mice (which would be something
of a problem since I’d probably want to get a laptop).
I keep flirting with the idea of getting a Mac in here, but keep
discarding it with the realization that A) I probably wouldn’t use it
much and B) I still don’t like one-button mice (which would be
something
of a problem since I’d probably want to get a laptop).
I replaced my linux desktop with a 17" PowerBook, and it quite
happily uses my 3 button Logitech mouse (well, two with a clickable
scroll-wheel). The only thing that still gets me is my expectation
of X Window style cut & paste.
On Tue, Jan 03, 2006 at 05:53:56AM +0900, Mike S. wrote:
I replaced my linux desktop with a 17" PowerBook, and it quite
happily uses my 3 button Logitech mouse (well, two with a clickable
scroll-wheel).
I’m perfectly aware of the capability of Macs to interface with an
external mouse with more than one button. It’s the built-in pointing
device with only one button on the Apple laptops that drives me up the
wall. You can’t just plug in an integrated trackpad with more than one
button.
You can emulate the second button and the third button by pressing
down the sightseeing key and the switch key, respectively. Not that
it’s a terribly good solution.
I replaced my linux desktop with a 17" PowerBook, and it quite
happily uses my 3 button Logitech mouse (well, two with a clickable
scroll-wheel). The only thing that still gets me is my expectation
of X Window style cut & paste.
The support software for the Kensington mice and trackballs supports
application-specific settings for all of the buttons. I used this to
allow me to have copy and paste buttons that functioned across the
X11/OSX divide.
For Ruby, just build your own. That is simplest.
it is true that’s the simplest way to install ruby from sources.
I have to agree here. On my OSX workstation I’ve built readline and
ruby from source. I’ve also done it on my Intel preview box as well. On
my OSX server, I just used the ruby fix script. On my OSX workstations
I build MySQL from scratch. On OSX server, I used the OSX installer
they have for MySQL.
I’ve gotten the MySQL gem to work by pointing the gem install to the
mysql_config file:
sudo gem install mysql – --with-mysql-config=/usr/bin/mysql_config
(find your mysql_config by calling which mysql_config)
Also, a lot of articles say to use gcc_select 3.3. I find this to be
not true. I have more diffulties building the Mysql stuff under GCC 3.3
on OSX.
However
if you need to bind ruby to gnome, glade and/or gtk+2 here the prob
comes…
This is so true. Building glib is hairy all in and of itself.
in such a case (needs of gtk+ or gnome) it’s better to use darwinports.
I’ve had terrible luck with any DarwinPorts package. Also a lot of the
ports are out of date.