RE: [cgiapp] Why perl lost steam...

> -----Original Message-----
> My interest in peeking at Boulder was really OT, but let me explain a
> little more about why it intrigues me. It seems to offer some simple
> ways to search for data in sets of simple data files like those=20
created
> when using the CGI->save method, almost an SQL like way of retrieving
> data from this format. And HTML5 supports a client side data storage
> function that uses the same format, so the two should be easily shared
> and synced between the client and server. And it may be worth looking
> into how the functionality of Boulder might be recreated with JS for
> the client side.
>=20
> I would offer that there is a difference between something being
> obsolete and being ignored. Certainly when Mr. Stein created "Boulder"
> he was aware that MySQL existed. What was his motivation? Is Boulder
> still being used to suit those purposes and more? If so, it's not
> really obsolete is it?

[DP] I can't comment on Boulder as I have never used it. I am a big fan=20
of SQLite because it has a small foot-print, it lightening fast and very=20
portable.

> And I am certainly not arguing that CGI::App and other Frameworks are
> not appropriate for small apps, what I am thinking is there may be a
> good reason for a simpler, ultralight, framework for small apps to
> exist.
>=20
> I suppose most of the functionality of that framework I imagine=20
already
> resides in CGI.pm. I just don't think it's been integrated into an
> approach that's easy for beginners to excited about.

[DP] I would say you are using CGI very appropriately, for a small,=20
self-contained app.=20
Dp.