[#23657] [Bug #1550] String#lstrip! raises RuntimeError on Frozen String Despite Making No Changes — Run Paint Run Run <redmine@...>

Bug #1550: String#lstrip! raises RuntimeError on Frozen String Despite Making No Changes

13 messages 2009/06/01

[#23729] [Bug #1583] Time + String no Longer Raises TypeError? — Run Paint Run Run <redmine@...>

Bug #1583: Time + String no Longer Raises TypeError?

14 messages 2009/06/05

[#23770] [Bug #1595] rake unusable on windows install — Robert Gonzalez <redmine@...>

Bug #1595: rake unusable on windows install

10 messages 2009/06/09

[#23869] [Bug #1640] [PATCH] Documentation for the Rational Class — Run Paint Run Run <redmine@...>

Bug #1640: [PATCH] Documentation for the Rational Class

12 messages 2009/06/16

[#23903] [Bug #1648] Rational#div Raises NoMethodError for Invalid Argument — Run Paint Run Run <redmine@...>

Bug #1648: Rational#div Raises NoMethodError for Invalid Argument

9 messages 2009/06/17

[#23977] [ANN] meeting log of RubyDeveloperKaigi20090622 — "Yugui (Yuki Sonoda)" <yugui@...>

Hi,

41 messages 2009/06/23
[#23979] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Run Paint Run Run <runrun@...> 2009/06/23

Thanks for the update. :-)

[#24173] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — "NARUSE, Yui" <naruse@...> 2009/07/07

Sorry for late response,

[#24174] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Luis Lavena <luislavena@...> 2009/07/07

On Tue, Jul 7, 2009 at 12:12 AM, NARUSE, Yui<naruse@airemix.jp> wrote:

[#24242] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Charles Oliver Nutter <headius@...> 2009/07/09

On Mon, Jul 6, 2009 at 10:18 PM, Luis Lavena<luislavena@gmail.com> wrote:

[#24010] [Bug #1685] Some windows unicode path issues remain — B Kelly <redmine@...>

Bug #1685: Some windows unicode path issues remain

26 messages 2009/06/24
[#29189] [Bug #1685] Some windows unicode path issues remain — Yuki Sonoda <redmine@...> 2010/04/01

Issue #1685 has been updated by Yuki Sonoda.

[#29200] Re: [Bug #1685] Some windows unicode path issues remain — Bill Kelly <billk@...> 2010/04/01

Yuki Sonoda wrote:

[#29892] Re: [Bug #1685] Some windows unicode path issues remain — Bill Kelly <billk@...> 2010/04/29

Hi,

[#24058] [Bug #1696] http downloads are unuseably slow — Steven Hartland <redmine@...>

Bug #1696: http downloads are unuseably slow

19 messages 2009/06/27

[#24063] [Feature #1697] Object#<=> — Marc-Andre Lafortune <redmine@...>

Feature #1697: Object#<=>

15 messages 2009/06/28

[ruby-core:23998] Re: [ANN] meeting log of RubyDeveloperKaigi20090622

From: James Gray <james@...>
Date: 2009-06-23 22:04:46 UTC
List: ruby-core #23998
On Jun 23, 2009, at 4:19 PM, Jeremy Kemper wrote:

> On Tue, Jun 23, 2009 at 2:30 PM, Joel VanderWerf<vjoel@path.berkeley.edu 
> > wrote:
>> James Gray wrote:
>>>
>>> Amalgalite has a lot of things going for it:
>>
>> + RTree support compiled in (not a default for sqlite)
>>
>> + Jeremy Evans added an amalgalite adapter to sequel (though it is
>> apparently not yet as fast as the sqlite adapter)
>
> Amalgalite is great, but it does *embed* SQLite in Ruby. So when you
> upgrade Ruby, you're also upgrading SQLite. What if we embedded other
> libraries we offer bindings for? I think it's a practice to be
> discouraged.

Obviously, there are plusses and minuses to both sides.  I don't want  
to get into a huge debate.  However, I do think we should at least  
list some of the advantages for going embedded, since we've listed the  
minuses.

I have a big SQLite project and I had nothing but trouble when we used  
an extension that dynamically linked to the library.  I frequently  
used SQL functions that were only in certain versions thus my code  
would work fine on some boxes, but not others.  Also, it would be  
super hard to reliably support features like the discussed hot backups  
because those require very current versions.

I just think it's really great to know if Amalgalite compiles, you  
know it works (bugs excepted, of course) and you know exactly what it  
can do.

> Also, in general, I prefer to see stdlib shrink instead of grow.
> Bundling with Ruby is a good way to retard independent library
> development.

I think deciding to ship a simple database with Ruby is excellent.   
Rails uses SQLite by default and how great would it be for new users  
to have reasonably high chances that just works?  Also, it's great to  
know you can count on having a decent database for any Ruby  
application.  I feel it's a really big win.

We're also nowhere near the first language to include a database in  
the standard library, or even SQLite specifically.

Anyway, I've given my opinions.  They are just that and I really don't  
wish to fight.  I'll be quiet now, Scout's honor.

James Edward Gray II

In This Thread