Comments on: The magical, mystical “1.0″ http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/ Kevin Dangoor on Software Development Fri, 21 Nov 2008 11:37:07 +0000 http://wordpress.org/?v=2.6.3 By: Ian Landsman http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3214 Ian Landsman Wed, 05 Oct 2005 15:03:42 +0000 http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3214 Like Taz says, once people are using it you're going to have to keep backward compatible anyway so that's that. Calling it less than 1.0 might make you feel more comfortable, but it doesn't change the fact that you're basically locked in. Like Taz says, once people are using it you’re going to have to keep backward compatible anyway so that’s that. Calling it less than 1.0 might make you feel more comfortable, but it doesn’t change the fact that you’re basically locked in.

]]> By: tazzzzz http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3162 tazzzzz Tue, 04 Oct 2005 18:20:57 +0000 http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3162 While there may be a discrepancy between what your vision is and what you have, if what you have can already provide value to people and not make them miserable because of bugs, then I think it's ready to be 1.0. Look at how many people are using Rails in different capacities. Rails hasn't been dubbed 1.0, but I'm certain that DHH considered backwards compatibility when making changes. And I still contend that backwards compatibility is not *that* hard, particularly in dynamic languages. Python and Java have evolved *a lot* over the last 10 years with very little in the way of backwards incompatibilities. While there may be a discrepancy between what your vision is and what you have, if what you have can already provide value to people and not make them miserable because of bugs, then I think it’s ready to be 1.0.

Look at how many people are using Rails in different capacities. Rails hasn’t been dubbed 1.0, but I’m certain that DHH considered backwards compatibility when making changes.

And I still contend that backwards compatibility is not *that* hard, particularly in dynamic languages. Python and Java have evolved *a lot* over the last 10 years with very little in the way of backwards incompatibilities.

]]> By: Ian Bicking http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3161 Ian Bicking Tue, 04 Oct 2005 18:17:32 +0000 http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3161 I'm a programmer, I count from zero. Really I should start at 0.0.0.0 and count up to 0.0.0.1 and so forth. In my experience, the stable interface thing kind of creeps up on you, and only later do you realize you're stuck. I’m a programmer, I count from zero. Really I should start at 0.0.0.0 and count up to 0.0.0.1 and so forth.

In my experience, the stable interface thing kind of creeps up on you, and only later do you realize you’re stuck.

]]> By: Ayende Rahien http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3158 Ayende Rahien Tue, 04 Oct 2005 18:07:19 +0000 http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3158 There is a problem with breaking backward compatability. Which I think is one big problem. Beyond that, there is the discrepency between what I see in my head and what I have in my hand :-) There is a problem with breaking backward compatability. Which I think is one big problem.
Beyond that, there is the discrepency between what I see in my head and what I have in my hand :-)

]]> By: Ian Landsman http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3152 Ian Landsman Tue, 04 Oct 2005 16:53:03 +0000 http://www.blueskyonmars.com/2005/10/04/the-magical-mystical-10/#comment-3152 I couldn't agree more. Once you've presented your "product" to the general public it should have a 1.0 label. In fact I think having a 1.0 version number more clearly conveys the state of the product. Less than 1.0 seems unclear as to if it should be used at all, while 1.0 says hey it's ready to go but it's new so expect to see more improvements over time. I couldn’t agree more. Once you’ve presented your “product” to the general public it should have a 1.0 label. In fact I think having a 1.0 version number more clearly conveys the state of the product. Less than 1.0 seems unclear as to if it should be used at all, while 1.0 says hey it’s ready to go but it’s new so expect to see more improvements over time.

]]>