[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion, decentralized version control, and the future.

From: B. Smith-Mannschott <benpsm_at_gmail.com>
Date: 2007-06-29 22:36:45 CEST

On Jun 29, 2007, at 05:45, Justin Erenkrantz wrote:

> On 6/28/07, Giovanni Bajo <rasky@develer.com> wrote:
>> And this time (if you allow me my humble two cent) get it right
>> and cut the
>> development time down to 1/10th by using a more evolved language
>> than C.
>> Python comes to mind, but anything would do.
> One thing I'd hope we avoid with "Subversion 2.0" is second system
> syndrome and such a desire smacks of it.
> Moving away from C means we'd most likely remove all reasonable
> extensibility mechanisms. One of the reasons that I view SVN as a
> success is that we made it fairly simple for third-parties to
> integrate with SVN - C is by far the best language for that.

> Rewriting all of Subversion in Python/C++/Java/Ruby is also *way*
> easier said than done. As we discussed at the summit, I don't have a
> problem with the higher-level parts - such as the command-line client
> - being implemented in Python which wraps around C libraries. But,
> libsvn_wc, libsvn_repos, etc. only being accessible via Python? Yuck.

True. I *do* think it would be worthwhile to consider embedding a
scripting language (Lua and Guile come to mind). This would allow
features that don't need the performance of raw C to be implemented
more concisely and maintainably. This approach has worked out pretty
well for EMACS.

// Ben

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 29 22:36:45 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.