On Fri, Feb 08, 2002 at 10:03:18AM -0500, Matt Cashner wrote: > On (02/08/02 15:25), [EMAIL PROTECTED] wrote: > > > Do you think you can cope with that ? :) There are people (like me) that > > like doing software design more than coding, and they will probably flood > > you with specs :) > > when i say "specs" i mean a feature specification. i design my own code, > thanks. same goes for the rfc. i want a consensus on what an 0.01 version > of an object layer should do. i havent paid attention to the many many > discussions and i wont until there's a consensual specification.
It is not as simple as you seem to think it is. First of all, are we talking about the same thing when speaking about design ? Although analysis, design and implementation interact with each other, usually analysis results determine design and not vice versa. So when I speak about design, it is not about code in any way, but for example a statement that threading model xyz should be used. We cannot just say that data access should be serializable because that is not detailed enough. So if you want to influence rfcs and design, you would have to take part in the discussions. Or there will be a spec where the implementation is not given but a lot of constraints. About the above statement with the coping etc, that was meant to be a joke. At least I think that design is far more interesting than coding (but a lot harder). You might have the same opinion, but then you have to take part in the design process. > i guess what i'm saying is that its time for the object layer folks to put > money where their email is. i'm offering to do your coding for you if you > guys can come together and draft an rfc. Well I think I understand it. But I have to repeat that it's a big topic and a single person probably cannot find the best solution. Additionaly the object layer folks want to have influence on the solution, not only on the result (since the solution actually determines future possibilies). You can however determine the solution by a very detailed feature wishlist, but this is just formal bloat. So the actual problem is that different folks think differently about what to build and how to build it. The code itself is certainly something that needs a lot of time, energy and motivation. But the real problems are solved before that. What I would like to know however is if you really would volunteer to just produce code. Only some people like that and I dont know wether you do (i'd guess you dont, but you seemed to say that .. ). so for now this all means more emails ... :/ torvald
