Ok Ive got a fair picture of whats good about Ruby.
Now what would you consider to be the biggest flaws or limitations in
ruby?
I personally thought that going from a type safe language to a dynamic
one would be more of a fuzz, but I have hardly noticed any problems.
the thing I have most problems with in that respect is that I have to
reffer to the documentation for every single method to see what they
return.
eg, “Class.instance_methods” returns an array of strings, I would have
bet money on that it would return an array of “Methods”
so I guess using a 3rd party lib with poor documentation must be a real
pain in ruby, while its not that/as bad in eg c# where you can atleast
guess what to do based on return / in parameter types
the next thing that I have a hard time with is the IDE’s
since Im used to having VS.NET wiping my butt all the time, its a pain
using some notepad++ sort of IDE, however Ive found activestate Komodo
which atleast is decent except for some random hangups…
(ok that wasnt a problem with the language, its more of a lacking tool
support)
and the one thing that scares me the most, name collisions.
since its possible to extend classes to left and right and doing all
sorts of cool stuff, there must be a huge risk that frameworks extend eg
“Class” with methods that collide or such things?
it feels a little bit like installing all your applications directly on
C: root.
(I know you can get some namespace’ish thing with modules)
Anything else that I can expect to get disappointed at with Ruby?
I’ve found that the only thing I’ve worried about is threads as they
aren’t
true. However, this hasn’t been a problem with me as I haven’t done any
real multi-threading work. It’s in the back of my mind though.
I find it to be a real pain in the ass to code in anything but Ruby now.
Java and C feel grotesque, and these were the languages I had the most
experience in before Ruby. Mind you, I’m a young programmer and am
truly
cutting my teeth with Ruby.
On Sun, Jun 25, 2006 at 03:41:32AM +0900, Roger J. wrote:
Ok Ive got a fair picture of whats good about Ruby.
Now what would you consider to be the biggest flaws or limitations in
ruby?
[…]
Although they are no big deal for me, three of the most common Ruby
problems are Unicode, threads and performance. The third is not a real
problem
for most people, and you can write Ruby extensions in C very easily for
extreme cases.
I, personally, can't stand most of the build and install tools for
Ruby,
they seem to be very hostile against repackagers (I’m a Debian
Developer, part
of the Ruby modules packagers team).
Perhaps others can add more things to this list...
Regards,
Lack of available modules for certain things, such as kerberos…
That’s killed a few ruby projects for me.
Exactly how would you want that to work? (I’ve built a KDC with
associated
Ruby tools for a commercial product and we might possibly open some of
it.)
Are you expecting that your Ruby applications would be a Kerb client to
do
user auth against some remote KDC?
Exactly how would you want that to work? (I’ve built a KDC with associated
Ruby tools for a commercial product and we might possibly open some of it.)
Are you expecting that your Ruby applications would be a Kerb client to do
user auth against some remote KDC?
We need pretty much full functionality. We run a couple of KDC’s and
have our own single sign on system written in perl (modeled after the
Yale CAS system). In fact it’s most of the administrative functions
that would come in handy, since authentication can go through the SSO
system.
Chris
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.