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

Carsten Breuer <CarstenBreuerSvn@textwork.de>:
> Do we? Memory-allocation bugs are always a problem of discipline and
> bad coding style.

No, they're primarily a bug that arises from not baving proper dynamic memory
management. Don't lecture me about C++ -- I learned better than this
writing LISP back in the 1970s back when C++ was not yet even a gleam in
Bjarne Stroustrup's eye, then I paid two decades' dues writing C because
hardware was not yet inexpensive enough to support LISP-like languages
outside of academia. I can make a pretty good guess at your age by
the way you write, and my guess is I've been clued in about these
issues longer than you've been walking and talking.

I'm coding C++ right now on Battle For Wesnoth. It's an ugly, bloated,
over-complex language -- an octopus made by nailing extra legs onto a
dog -- and it encourages ugly, bloated, over-complex architectures. I
am pretty sure the Subversion architects know better than to go there.

The "discipline" you speak of has become a *waste of time* for anybody
not doing kernel or realtime work. With menory and cycles so cheap, p
programmer hours are best spent on solving real problems, not on low-level
resource bookeeping.

-- 
		Eric S. Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org