It shouldn’t. People are saying you can still buy ST2 and I’m stating that that is false.
[quote=“castles_made_of_sand”]Do you, for example, want Jon to backtrack, porting everything possible back to ST2 in a non breaking manner?
Do you want a promise of at least bug fixes for ST2?
It’s not as much progress as you or I’d like, but ST3 IS progress. I’d rather see a mass transition ASAP.
What I’d like to see is a promise of bug fixes for ST2 for a reasonable period and wbond officially compensated for work in speedily porting Package Control and managing the transition.[/quote]
I’m pretty sure nothing anyone says in these forums or anywhere else will change the course of ST3. It is what it is. This is a thread for discussing the ST3 beta and I was merely expressing my disappointment in it.
At this point I don’t think my main two issues with ST3 are even fixable. Those being a feature list that doesn’t justify an upgrade or a price increase and API changes that are going to devastate the plugin community.
Speaking to the first, I think the damage has already been done. The feature list could expand in the future but ST3 has already been released and development on ST2 has stopped which will now divide the userbase. You’re going to have a group of users that stick with ST2 because they don’t see it worth upgrading to ST3 and you’re going to have another group that does. Plugin developers are now forced to pick a side or go insane trying to support both.
Speaking to the second, these changes are at the core of ST3. Swapping back to Python 2 would make for a smoother transition, but it appears there was no attempt whatsoever to make the API backwards compatible. I also highly doubt that will occur.
ST3 is the Vista of ST except it’s lacking a hook like Vista had with DX10. Lets just hope ST4 is like 7.