• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Thoughts on choosing a source code control system?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thoughts on choosing a source code control system?


  • Subject: Re: Thoughts on choosing a source code control system?
  • From: Ian Joyner <email@hidden>
  • Date: Tue, 14 Mar 2006 10:19:24 +1100

On 13/03/2006, at 5:38 PM, Art Isbell wrote:

On Mar 12, 2006, at 6:28 PM, Ian Joyner wrote:

But maybe my unease with these systems is that they seem more file- based because that's "the way computers and Unix work", rather than patch-based which would result from thinking about the development process at a high-level of abstraction.

darcs (<http://abridgegame.org/darcs/>) claims to be patch-based.

Thanks Art, Darcs looks like some impressive thought has been put into it, and it's written in Haskell (so we can Curry our functions!). Must admit I was in analysis and design mode yesterday, coming up with some radical ideas for one of our products because we were getting vague requirements, more indicating a radical rethink was needed and I was very much in why-would-you-want-to-do-that mode, and with some working out user scenarios and fundamental redesign, we might make a lot more people happy.


Alas, I have too frequently seen development managers who have hardly written a line of commercial code in their lives pushing gannt charts, flow diagrams, and all sorts of other tools and then the code that arises from these is so appalling that you wonder what they were for. Good tools in good hands yes is worth it. But as Bertrand Meyer once said, he realised while shaving one morning why the diagramming folk liked diagrams so much and avoided programming (which they saw as something for a lesser breed of person – the programmer) – it's because "diagrams don't crash".

However, my projects are now at a point where we will have to be more disciplined, so I might look into Subversion and Darcs myself, but I think I'd really like to see a development environment where all of this was integrated and I did not have to learn several different tools – SCM seems like more of an afterthought in Unix environments (but then Xcode is just some wrapper on the Unix C-based development environment :-( ). It also leaves me wondering if WebObjects programming is that simple.

Ian

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Thoughts on choosing a source code control system? (From: email@hidden)
 >Re: Thoughts on choosing a source code control system? (From: Ian Joyner <email@hidden>)
 >Re: Thoughts on choosing a source code control system? (From: Arturo Pérez <email@hidden>)
 >Re: Thoughts on choosing a source code control system? (From: Karl <email@hidden>)
 >Re: Thoughts on choosing a source code control system? (From: Ian Joyner <email@hidden>)
 >Re: Thoughts on choosing a source code control system? (From: Art Isbell <email@hidden>)

  • Prev by Date: Re: Site management strategies with Subversion
  • Next by Date: Re: Site management strategies with Subversion
  • Previous by thread: Re: Thoughts on choosing a source code control system?
  • Next by thread: Re: Thoughts on choosing a source code control system?
  • Index(es):
    • Date
    • Thread