Sublime Forum

Sublime Text 3 Beta

#106

[quote=“C0D312”]@Anomareh

You really like to contradict yourself, don’tcha?

First you argue that Python 3 is too big a change since it will warrant people rewriting plugins (which will take some time but may prominent plugin authors have already given their support and mentioned that they are working on porting over to Python 3). Then you argue that there is not enough changes (in terms of features) but I would argue that the switch to Python 3 is pretty major.[/quote]

What? Talk about taking something completely out of context just to make an argument. Never did I say there were not enough changes in Python 3 to consider upgrading. I said that the differences between Python 2 and 3 aren’t the main reasons the upgrade is a problem.

Swapping to Python 3 is not moving forward. It’s running across the canyon before the bridge is built.

Except everyone is as ST2 is EOL and can’t even be bought anymore (and no, having the ability to buy ST3 and get a copy of ST2 for free is not having the ability to buy ST2)? ST1 didn’t see a single update (bug fix or otherwise) once the ST2 public alpha became available. I don’t see the situation between ST2 and ST3 being any different. Looking beyond how insane it is to compare a programming language to a text editor, Python 2 is still being maintained and it’s still available.

So you can see into the future? What reasons do plugin developers have to update their plugins for ST3? With a split userbase they’ll just be choosing one userbase over another. Largely because, as I stated, there aren’t enough improvements in ST3 to justify upgrading. Also, I like how you believe ST3 is going to see a bunch of new features added at some point. The majority of the new features of ST2 were available in the public alpha. Only a couple were added afterwards. I don’t see any reason for ST3 to be any different.

Besides you completely missing the point I was making, you do realize ST3 is the only thing available for purchase right now right?

Again, you somehow completely managed to miss the point I was making. Speed isn’t a viable reason in the case of ST to increase the major version. As he stated himself, speed has always been a concern and has always seen improvements. ST being faster is not something new to ST. ST’s speed has been substantially improved several times throughout the development of ST2.

0 Likes

#107

@Anomareh well, this conversation was fun at first but now I see you’re not even going to read what I’m saying so there’s no point…(plus I’d prefer if we stopped mucking up this thread for people with legitimate stuff to post)

I gotta go to bed anyway. I’ve got computer science class in the morning and we’re learning about methods! yay!

0 Likes

#108

Funny. First off, you started the discussion by responding to my thoughts on the ST3 beta. Second, you took nearly every single thing I said out of context. Third, I even obliged and directly responded to everything you’ve said. Also, I don’t see how this is off-topic in a thread designated for discussion about the ST3 beta.

0 Likes

#109

Port some plugins before making a final judgement.

I started porting efforts by writing a plugin that opened errors in ST2 where I did all my editing.

I ported an old lxml plugin that parses html buffers in a background thread, making use of the now threadsafe scoping api.

It’s constantly building a DOM as you type, without ever slowing down. You couldn’t really do that in ST2.

There’s subtle changes like all plugin modules having absolute path __file__ properties so you can write exception handlers that navigate to source of errors and navigate the backtrace.

The speed improvements are very much a consequence of changes to the plugin system and plugin loading, breaking changes that couldn’t really be backported to ST2.

Having said all that, I’m somewhat disappointed there’s not more radical changes too, with all this breakage/porting pushing ETA on ST4 well into the future.

0 Likes

#110

Subtle isn’t really the word you want to see describing a new major release when a price increase comes attached to it :confused:

“Here’s this thing that for the majority of end-users is the same as the last thing except this thing is more expensive and it’s going to break nearly everything for a while. Oh, and it’s faster. Also, you can’t buy that last thing anymore and it’s no longer supported.”

0 Likes

#111

What’s the outcome you want here?

0 Likes

#112

[quote]Upgrade Policy
A license is valid for Sublime Text 3, and includes all point updates, as well as access to prior versions (e.g., Sublime Text 2). Future major versions, such as Sublime Text 4, will be a paid upgrade.[/quote]

The download link still points to ST2 for me?

Valid concern I guess.

0 Likes

#113

Not sure what you mean.

[quote=“castles_made_of_sand”]

[quote]Upgrade Policy
A license is valid for Sublime Text 3, and includes all point updates, as well as access to prior versions (e.g., Sublime Text 2).[/quote]

Future major versions, such as Sublime Text 4, will be a paid upgrade.
The download link still points to ST2 for me?[/quote]

You can still download it, but you can’t buy it. You can buy ST3 and get a free copy of ST2, but you can’t buy ST2. Also, I highly doubt ST2 will see another update from here on out. For all intents and purposes ST3 has been released and is the only product that will see development.

0 Likes

#114

I strongly disagree :smile:

0 Likes

#115

You can still download it, but you can't buy it. You can buy ST3 and get a free copy of ST2, but you can't buy ST2. Also, I highly doubt ST2 will see another update from here on out. For all intents and purposes ST3 has been released and is the only product that will see development.
You can’t actually buy older version of software in general (except software that is sold on phisical support). Why would ST be an exception? :unamused:

0 Likes

#116

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.

0 Likes

#117

[quote=“lunixbochs”]

I strongly disagree :smile:[/quote]

I knew I’d get in trouble there :smile: Yeah, it’s “possible”, but trust me, it’s not as nice.

0 Likes

#118

Talking about being able to use the scoping, and even add_regions etc apis from a background thread

The smoothosity is maintained, more so than messing around with various co - scheduling set_timeout mechanisms

0 Likes

#119

sublimelint does absolutely everything in a thread and only merges with set_timeout for pretty much instant add_regions at the very end. Works really well. Every time I worry constant linting slows down the editor it turns out to be a different plugin I installed.

0 Likes

#120

Yes, I love your branch of sublimelint, it saves my arse all the time :smile:

0 Likes

#121

You realize my version is the original, right? :stuck_out_tongue:

I just wish jon had set_status working reliably so I could release the ST3 port.

0 Likes

#122

Yes, actually, I do :smile:

0 Likes

#123

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.

0 Likes

#124

Ok, you have legitimate concerns but saying you can’t buy ST2 seems off to me.

0 Likes

#125

UI themes and syntax coloring from ST2 compatible with ST3? And how i try ST without license? I want try work with ST3 before purchase

0 Likes