Which is the oldest Delphi version you are going to use MMX Code Explorer in (and probably would pester me once I drop it)?
Which is the oldest Delphi version you are going to use MMX Code Explorer in (and probably would pester me once I drop it)?
If you are using it only in newer Delphi versions than XE, then simply don't vote at all. Instead feel free to add a comment here. (Why are polls on G+ limited to 5 items?)
If you are using it only in newer Delphi versions than XE, then simply don't vote at all. Instead feel free to add a comment here. (Why are polls on G+ limited to 5 items?)
I've never used it. Sorry.
ReplyDeleteDelphi XE7
ReplyDeleteBerlin.
ReplyDeleteDelphi Berlin and up
ReplyDeleteTokyo
ReplyDeleteNever used but I'm going to test it and only for Tokyo and up
ReplyDeleteI'm oldfashioned :D
ReplyDeleteUse it with Delphi 2006 and Delphi 2007.
Tokyo :)
ReplyDeleteTokyo. The only reasons I have all the rest back to D5 (except 6) is for backward compatibility of OTA tools and like you I'm starting to limit how far back I go to circa 2009/10 when generics, anonymous methods, (build-in) regular expressions and (build-in) zip support were introduced.
ReplyDeleteI'm not sure if I am going to use it at all. I have downloaded it but not yet installed.
ReplyDeleteThere are a lot of users of old versions. D7 remains popular. I use D6 a lot.
ReplyDeleteWould not willingly work without it now. I licensed ModelMaker first, and that was a love/hate relationship because of the IDE features not available in ModelMaker.
ReplyDeleteOddly, and despite numerous suggestions, it took a few years before I finally licensed MMX. Routinely much more useful than Modelmaker, and especially so in a team environment where it would be difficult to get all members to agree on ModelMaker.
I use D2007 out of need, but it is a legacy project, and will not be there forever. Were you to drop all pre-XE for future features, I would not be concerned.
The main problem here is actually Delphi 7 requiring special handling all over the place and prohibiting to move forward by magnitudes compared to the other versions listed above. Given that the time I am able to invest is limited, it would be a bit unfair for all other users when a significant part of that time is used for keeping Delphi 7 supported.
ReplyDeleteAfter all, dropping support wouldn't make it unusable for Delphi 7. It just will not get any updates after that.
The majority of enhancements I have in mind wouldn't benefit older Delphi versions anyway. F.i. the already available uses sort has only a meaning for XE2 and up. Also, following the formatter settings when inserting or manipulating code is pretty useless when no formatter is present. A big bunch of OTAPI interfaces simply don't exist in older Delphi versions or are of limited functionality.
The impact of dropping Delphi 7 support may not be that big in the end, while the simplification of my development process will probably be huge.
I would think that the actual state for Delphi7 is good.
ReplyDeleteOn my side I'm using D2007 for maintain some old tools, but if there is not a new MMX it is not a problem, because the latest is working fine there.
Tokyo, and if we don't upgrade to the next version I rather see us freeze the whole dev environment at that point in time.
ReplyDeleteBerlin and up.
ReplyDeleteIMHO You should drop support for everything prior Delphi 10.x.
ReplyDelete10.2.3 and up
ReplyDeleteXE7
ReplyDeleteBerlin, maybe XE2.
ReplyDeleteDelphi 2007 for non-unicode projects; Delphi XE4 or up for unicode stuff.
ReplyDeleteDelphi 5!
ReplyDeleteAmir Aavani Current minimum supported version is 7. Seems unlikely to think that Uwe is going to add support for 5.
ReplyDeleteI understand that software being created with with D5 or D7 is still around. Sometimes a product is just good enough, or developers lost interest.
ReplyDeleteBut I don’t understand developers who actively maintain a codebase without ever upgrading their tools.
All the extra work you out into dealing with ancient tools are probably costing way more than upgrades would.
Delphi 5 was released in the 90s! I had a modern mobile phone with an LCD display.
Tool makers have to decide:
(1) Support dinosaurs who don’t even bother to upgrade, slowing modern users down.
Or:
(2) support modern users and slow users of ancient software down.
If (1) is chosen, modern users cannot do anything against being slowed down. If (2) is chosen, dinosaurs can always choose to upgrade, and benefit from all developments.
Wouter van Nifterick Well said!
ReplyDeleteActually the users of older Delphi versions are not slowed down at all. They are just not sped up.
Very hard to make a case for an open source project to maintain support for old delphi versions lacking Unicode and generics. Anything that makes it less time consuming for Uwe means better chance of the project thriving. And for users that are stuck on old. Delphi's, the existing versions of MMX won't stop working.
ReplyDeleteI am happy with the version I have installed in Delphi 7, so I don't need updates for that.
ReplyDeleteI use XE4 for current projects, Windows Desktop only and currently can not warrant the upgrade cost as XE4 does everything I need to maintain our inhouse Stock Control systems.
For now, Berlin and up..
ReplyDeleteFWIW, the Parnassus plugins support only XE and above -- and even that causes me headaches. I have been tempted for some time to drop support for everything before XE4, or even before XE6/7 or Berlin.
ReplyDeleteMany language and compiler fixes, RTL improvements, etc, in those newer versions. After using them, going backwards really feels like, well, going backwards.
I would simply make the current version available for older versions of Delphi and just provide new features for the later versions of Delphi.
ReplyDeleteDavid Craggs It will probably boil down to something like that.
ReplyDelete