Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 May 2007 20:46:29 -0700
From:      Garrett Cooper <youshi10@u.washington.edu>
To:        freebsd-hackers@freebsd.org
Subject:   Re: SoC
Message-ID:  <464D2195.3020309@u.washington.edu>
In-Reply-To: <20070515213026.GI1017@dwpc.dwlabs.ca>
References:  <20070513040651.GB1017@dwpc.dwlabs.ca> <4647F627.7020408@u.washington.edu> <20070514202922.GF1017@dwpc.dwlabs.ca> <4649426F.8050601@u.washington.edu> <1179214317.1791.38.camel@zoot.mintel.co.uk> <464969B3.3050306@u.washington.edu> <20070515213026.GI1017@dwpc.dwlabs.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Duane Whitty wrote:
> On Tuesday, 15 May 2007 at  1:05:07 -0700, Garrett Cooper wrote:
>> Tom Evans wrote:
>>> On Mon, 2007-05-14 at 22:17 -0700, Garrett Cooper wrote:
>>>> Ruby's nice, but it's built on Perl so I have suspicions on its overall 
>>>> usability / speed given my experience with Perl over the past 4 months 
>>>> daily for work :(.. Ruby's just the new big thing for programming 
>>>> languages, so everyone's into it. Kind of like how Java was compared to 
>>>> C/C++ a few years back. But once everything dies down people will 
>>>> realize that they'll still have to program in C/C++/Perl for real-world 
>>>> applications.
>>>>
>>>> Python seems better than Ruby from what I can see, but I really don't 
>>>> like the mandatory indentation thing. Ew..
>>>>
>>> Rubies are better Perls. That's the only connection between the two. One
>>> day, a Japanese programmer got fed up with Perl, and wrote a better
>>> language (for varying meanings of better).
>>>
>>> Its not based or built on Perl in any respect.
>>>
>>> Python and Ruby both have the same targets; to speed development time
>>> and increase programmer productivity.
>> But one must make a Perl before one can make a Ruby. Maybe that was what 
>> I was trying to aim for.
>>
>> Ruby's nice, but it seems like it's going to be a bit passe in a few 
>> years like Java was for compilable / interpretable languages.
>>
>> -Garrett
 >
> None of this matters
> 
> 
> My only point is that if you need something quick to explore the format of
> pkgdb.db or INDEX.db you are pretty well assured of finding a tool you
> can work with; Perl, Python, or Ruby.  If these aren't sufficient use C.
> 
> The pkg_* tools are written in C so in C they will be modified; but no
> harm in doing initial exploration and prototyping with something else.
> 
> Let's stay focused!
> 
> Duane

Ok, finally dumped the full database. Will analyze closely later on tonight.

Cheers,
-Garrett

PS If you installed ruby-bdb, simply running "make config" in the 
ports-mgmt/portupgrade directory and selecting ruby-bdb1 won't do. You 
have to go into databases/ruby-bdb, do make deinstall, then go to 
databases/ruby-bdb1 and do make install, or something similar.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?464D2195.3020309>