<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Christian:<br><div><div>On 2011-05-09, at 4:02 PM, Christian Lohmaier wrote:</div><blockquote type="cite"><div>Hi Peter, *,<br></div></blockquote><div><snip></div><blockquote type="cite"><div>Oh, different build configurations is of course no problem, that would<br>just be adding a configure switch --with-macosx-sdkversion -  but<br>maintaining the actual code for two different variants is. I just<br>don't see the Mac-part has enough manpower to do so.<br></div></blockquote><snip><br><blockquote type="cite"><div>Again the problem I see is:<br>* Developers use newer version, they don't even notice that they<br>introduce incompatible code<br>* There are very few mac developers in total to begin with, those who<br>then have 10.4 to actually work on a fix is even lower<br>* Mac-users don't usually engage in doing QA/Testing either, Feedback<br>from Mac users comes very late (if at all)<br>→ you'll end up with code that won't work for 10.4, but nobody<br>able/willing to fix up that code/writing a backwards compatible copy<br>that does the same for 10.4 using a different API<br><br>And so far I didn't hear of any specific feature or similar that would<br>require 10.5 or 10.6 API/libs...<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br><blockquote type="cite"><div>I'm aware that this will not work forever. Alone because Apple likes<br>to break compatibility despite shipping the older SDKs - but I'd<br>rather make it harder (i.e. not making it easier) for people to<br>introduce stuff that is not supported on 10.4 (i.e. stuff that needs<br>to be duplicated for 10.4 anyway) as long as the 10.4 code also works<br>on 10.5 and 10.6.<br><br>ciao<br>Christian<br></div></blockquote></div><br><div>I genuinely understand and truly respect your pov.</div><div><br></div><div><div>Mac's have been my sole livlihood for the past 25 years </div><div>going back the the Mac Plus.</div></div><div><br></div><div>Out of curiosity how many Mac developers?</div><div><br></div><div>Are they all using command line hacking?</div><div><br></div><div>Now I'm 73 and there is no way I want to go back to that way of development.</div><div>For me the Xcode IDE has been very productive for the past many years.</div><div>More so than MPW - it's unixy style predecessor.</div><div><br></div><div><blockquote type="cite"> I'm aware that this will not work forever.</blockquote><br></div><div>Precisely. So maybe the time is now to start up an Xcode IDE version.</div><div>If there is support for that I would consider helping.</div><div><br></div><div>For me using the command line is like cutting people open to do a gall bladder removal.</div><div>Whereas Xcode IDE is like laparoscopy.</div><div><br></div><div>Anyway I think you get where I'm coming from.</div><div><br></div><div>with my respects to you</div><div><br></div><div>Peter</div></body></html>