<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I didn’t mean for this to sound negative, more constructive. Oh I know how quickly things can get out of hand with spending time on open source ...<div class=""><br class=""></div><div class="">That being said, for things like “Max 7 now uses a larger buffer on this object” and making the buffer larger doesn’t actually change how the expected out of the object works, why not update it? The Max devs have a vested interest in not breaking their customers patches too. Even easier when someone has already compared and tested those differences for us developers and can greatly help guarantee making a change will not be detrimental.<div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">--------<br class="">Dan Wilcox<br class=""><a href="https://twitter.com/danomatika" class="">@danomatika</a><br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com" class="">robotcowboy.com</a></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Dec 23, 2015, at 8:24 AM, Dan Wilcox <<a href="mailto:danomatika@gmail.com" class="">danomatika@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Oh I know. It just seems a shame to say: "Well, somebody might have a patch somewhere from 10 years ago that relies on a 10 year old version of a library that mimics a 10 year old version of Max running on a 10+ year old computer/os and we can't break that, ever."<br class=""><br class="">For vanilla objects yeah, I get it, but for externals isn't it also reasonable able to say: "It's been 10 years maybe I might need to update that patch that uses that 10 year old external lib."<br class=""><br class="">I'm not saying break things arbitrarily but, in the case of Max, they don't want to break people's patches either (and I bet there are more patches out in the wild than Pd patches). What has max changed object-wise between 4.6 & 7 that actually breaks things? I'd say very little and, if so, the whole argument is kind of moot so why not just introduce those non breaking changes made by Max?<br class=""><br class="">If only we had someone who could extensively test, compare versions, and make notes about these differences. That would make not easy to see what might be a problem an what's easy to add. Oh wait, hasn't Alexandre been spending alot of time doing just that?<br class=""><br class="">IE if an object historically had one output and and update adds another, how does that break old patches that only use 1 output?<br class=""><br class="">enohp ym morf tnes<br class="">--------------<br class="">Dan Wilcox<br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class="">robotcowboy.com<br class=""><br class="">On Dec 23, 2015, at 4:29 AM, katja <katjavetter@gmail.com> wrote:<br class=""><br class=""><blockquote type="cite" class="">On Wed, Dec 23, 2015 at 4:44 AM, Dan Wilcox <danomatika@gmail.com> wrote:<br class=""><blockquote type="cite" class="">What about versioning? If people *have* to have older compatibility, then<br class="">why can’t they just run an older version of cyclone? Newer development can<br class="">take place on the current version and you can clearly note api<br class="">changes/updates in a CHANGELOG. Say tag cyclone right now as version 1.0.0<br class="">and all further development is version 2.0.*<br class=""></blockquote><br class="">Versioning is important but it can't solve all issues that arise when<br class="">diverging. While it is easy for a user to update to a specified<br class="">version of a library with deken, Pd patches already out there 'in the<br class="">wild' (to quote Jonathan) don't specify which version they need.<br class=""><br class="">Katja<br class=""></blockquote></div></div></blockquote></div><br class=""></div></div></body></html>