Sublime Forum

Updates for the stable Sublime Text

#5

[quote=“mwb1100”]

But you can also complain when it appears that the support you thought you might get doesn’t materialize.[/quote]

It looks like getting a reply on the forum is also too much to ask for.

0 Likes

#6

I agree with this. The lack of any continued support for ST2 is making my seriously reconsider my decision to pay for it. Is this how it’s going to be in perpetuity? Will those of us who pay for ST3 and find bugs there also be left in the lurch until we’re made to pay for ST4? This seems to be setting a precedent that I’m not comfortable buying into.

0 Likes

#7

You know what? Don’t buy it.

I paid for ST2. I use it every day, all day. Whatever I paid for it, I more than got my money’s worth. Even if it never gets updated again. It’s an career expense, a tool I needed.

I am using the ST3 beta. When it comes out, I will pay for that too. PAst experience has shown it’s a tool that has worked well for me, day in and day out, enabling me to do my job better.

Now, if it doesn’t work right for you, or you’re not comfortable with spending ~$75 a year on the tool you use every day, or don’t like the way Sublime is developed/updated, please just go buy another editor. :wink:

0 Likes

#8

[quote=“handycam”]You know what? Don’t buy it.

I paid for ST2. I use it every day, all day. Whatever I paid for it, I more than got my money’s worth. Even if it never gets updated again. It’s an career expense, a tool I needed.

I am using the ST3 beta. When it comes out, I will pay for that too. PAst experience has shown it’s a tool that has worked well for me, day in and day out, enabling me to do my job better.

Now, if it doesn’t work right for you, or you’re not comfortable with spending ~$75 a year on the tool you use every day, or don’t like the way Sublime is developed/updated, please just go buy another editor. :wink:[/quote]

I DID buy it already. I expect to get support for what I’ve paid for. No, buying ST3 isn’t what I’m going to do.

The support provided for ST2 has literally been ZERO - no reply from the developer, no updates, no statement, NOTHING.

So, please excuse me if I don’t care about the opinions of people who throw their hands up and say “yeah, sure, pay $$$ every year to get the latest version and access to the latest BETAs”. That doesn’t solve the problem of bugs.

It looks like far too few people can understand exactly how software development is supposed to work. You get a stable release and that stable release gets maintenance updates. A thousand new features are worthless if bugs get carried over and new ones are introduced.

Also, this doesn’t excuse the lack of support from the developer. If you take my money, I expect SUPPORT.

0 Likes

#9

ST2 was available as a beta for a long time with amazingly frequent updates, bug fixes and everything. Problems were posted here and sometimes fixed within a day. Based on this history, ST2 had a long and prosperous life span. The ONLY problem is that Jon should have called the version ‘stable’ much earlier so that people wouldn’t complain about the lag of updates. If you forget about this labeling issue, I don’t know about many other software products that had such an active developer who provided so frequent updates. For many people that is something they love about ST.

0 Likes

#10

Perhaps that’s the case, but it still doesn’t change the fact that ST2 hasn’t received an update for a very long time. It’ll be 12 months since the last update in a few months. The fact that he was releasing new builds quickly is indeed admirable, but that’s needed when building a new version of a piece of software.

It wouldn’t be such a big deal to release an update every 2-3 months to fix a few bugs. Some people have already said they wouldn’t buy ST3 and any future version because he’s not supporting the stable version - AT ALL.
I don’t know what other people expect from what they pay for, but I expect to have bugs fixed in the current stable version of a piece of software, not in the version to be released 3 years from now after paying for 3 more upgrades. Then I have to pay for 3 more years to get rid of the bugs introduced in those versions and so on. The problem wouldn’t be the money, but the time. Otherwise we’d all write our own ST like editors.

At the time when I’ve bought ST2, it was in BETA and I really thought some of the bugs would be fixed. Instead, they never got fixed. I’ve got it to crash on me a couple of times without any kind of explanation. I get messages that a plugin took too long to execute from time to time, even though this problem wasn’t occurring in a previous beta for me.

I’ve gone through the plugins and the set of enabled plugins didn’t seem to make a difference.

0 Likes

#11

While I think you’re right to be upset that the stable branch of ST2 hasn’t been updated in quite a while, and that Jon might not be the most responsive developer in the world, if you’ve purchased a copy of ST2, why not try out the latest dev or nightly build? In my experience, both branches have been rock solid (I run exclusively nightly builds of ST2 and I’ve never had an issue), and while Jon was working on ST2, the nightly branch received bug fixes every few days. If you’re willing to give it a try, ST3 also gets updates very few days, and for now, your ST2 license will work. Just a suggestion. :smile:

0 Likes

#12

No, thank you, I don’t wish to run into the same bugs everyone is running into. I don’t want to repeat the experience I’ve had and I’m still having with ST2.
I wish to receive updates after the BETA is done and I’m not looking to trade the problems I’m having with ST2 for problems I’d have with ST3.

Furthermore, I have a very small number of plugins, but I really need those plugins, so I won’t be giving up on ST2 to switch to the extremely unstable and buggy ST3.

0 Likes

#13

While ST3 beta has been stable for me, I agree that the lack of updates for ST2 is hugely disappointing, especially as ST2 was crashing on me several times a day (not due to plugins) and there was a period of ~6 months where pretty much nothing at all was communicated to users reporting problems. This is making me doubt whether I should pay for the ST3 upgrade when it’s finally released.

0 Likes

#14

Agree.

It was the same with the transition from ST1 to ST2, but ST2 was so much better and as I didn’t invest too much time in configuring ST1, I didn’t think twice before using ST2 Beta and forgot ST1.

Today it’s different.

Even if ST3 has some nice features, I don’t feel in urge to start using it.
I spend a lot of time configuring ST2, and I don’t want to do it again before a stable release of ST3 with all my needed plugins available.

There’s few bugs in ST2 (some are resolved in ST3) that I like to see fixed.
And maybe a few things could be done to facilitate the compatibility of plugins between ST2 and ST3 (like automatically calling plugin_loaded() in ST2).
But it looks like ST2 development is dead.

I really expect an answer from jps too.

0 Likes

#15

[quote=“bizoo”]

Agree.

It was the same with the transition from ST1 to ST2, but ST2 was so much better and as I didn’t invest too much time in configuring ST1, I didn’t think twice before using ST2 Beta and forgot ST1.

Today it’s different.

Even if ST3 has some nice features, I don’t feel in urge to start using it.
I spend a lot of time configuring ST2, and I don’t want to do it again before a stable release of ST3 with all my needed plugins available.

There’s few bugs in ST2 (some are resolved in ST3) that I like to see fixed.
And maybe a few things could be done to facilitate the compatibility of plugins between ST2 and ST3 (like automatically calling plugin_loaded() in ST2).
But it looks like ST2 development is dead.

I really expect an answer from jps too.[/quote]

I have started to add images of errors to my original post. Perhaps this will help get some attention.

0 Likes

#16

And how it’s ST fault that you are using invalid config files? (on a package that it’s not even built in into ST!)

0 Likes

#17

I didn’t add anything to the configuration of that package… the eror doesn’t even show up all the time…even though I used the package all the time…

I see that you’re a hardcore fan of ST2. Perhaps you could ignore this thread so you don’t get offended.

Oh, yeah, without those few basic packages, using this editor isn’t really worth the effort, nor the money.

0 Likes

#18

It seems that you mix packages support with the editor support. While first are community packages (which, btw, you can contribute to!), the second has fairly good support (most real bug reports has replies and fixes)

There are some stuff that i consider annoying (like lack of tooltips, sidebar customization, code folding based on indentation only and so on), but bugs on the editor itself? Not that much.

Out of curiosity: name few bugs of the editor.

0 Likes

#19

[quote=“iamntz”]

It seems that you mix packages support with the editor support. While first are community packages (which, btw, you can contribute to!), the second has fairly good support (most real bug reports has replies and fixes)

There are some stuff that i consider annoying (like lack of tooltips, sidebar customization, code folding based on indentation only and so on), but bugs on the editor itself? Not that much.

Out of curiosity: name few bugs of the editor.[/quote]

I’m not confusing anything with anything else. I get this error from time to time and it’s completely random. I’ve edited sass files for hours and never got this error. However, it simply pops up after running ST2 for some hours.

It’s not possible for bugs to have been fixed in ST2 since there haven’t been any updates to the stable version since last year.

Furthermore, I will take screenshots for each and every error from now on, so you’ll probably get to see those bugs you’ve asked for.

I encourage everyone else who’s running into bugs in ST2 to post in this thread. Maybe people will understand this thing REALLY needs some support from the developer.

0 Likes

#20

Why don’t you just delete that file?

0 Likes

#21

I think @iamntz is right. I think think your config file error is specific to your system (you’ve got some flaky plugin or you need to revert to clean install).

0 Likes

#22

I don’t consider 6 months of silence as good support.

Crashes/freezes:



Usability issues:
sublimetext.userecho.com/topic/8 … -be-wider/


0 Likes

#23

Oh, and github.com/sublimehq/Vintage/issues

0 Likes

#24

I think it’s pretty safe to say you’re not going to see any updates for the “Stable Sublime Text”.

It’s true, as someone else pointed out, that the labeling of beta and stable for the product has been unfortunate. Since the beta period for 2 was so long, it was like having a stable version that had very frequent updates despite the beta label.

My guess would be there are some things that weren’t working as they should (although I have never run into any serious bugs with 2 personally) and to improve the product the developer figured that a major update was the way to go, hence the 3 beta. Sometimes that’s what’s needed to fix things. I have NO way of knowing of course, just a guess.

So instead of the continuous outrage over the lack of updates for 2 (which I would guess are not forthcoming) either deal with it or write to the developer for a refund if you’re so unhappy with the product.

FWIW, I have been using 3 since it came out and have only run into a handful of crashes. I have more crashes in Dreamweaver.

0 Likes