Going public with the Beta doesn't bode well for the numerous small bugs and inconsistencies that have plagues sublime for longer than the closed Beta. Some also have been introduced with new features, but still remain unaddressed. It also probably means no new plugin Api functions and features, although many have been requested for a long time.
I guess since ST is such a well-rounded product overall that these shortcomings really grind my gears.
Sublime once had genuinely amazing support. The solution to scaling that with the product's popularity has apparently been to drop it on the floor. Expect bug reports to go unanswered for months.
It seems to have been a victim of its own success. In the run up to the final ST2 release, we saw a string of new releases showing often subtle but useful improvements (and breaking a couple of things irritatingly as well). After the ST2 release, that stream of improvements just seemed to dry up, and now it turns out a paid upgrade model is being used. I don't mind that for new features, but for obvious bugs, in a premium product (which any text editor that costs real money is, given the competition), that got-your-money-now attitude does grate. This remains true even if the amount of money itself is small and it was an easy decision to buy it in the first place (and would be for the upgrade, if I had any confidence it wouldn't go the same way, which I no longer do).
Yes, sometimes I think jps intentionally ignores bug reports that are not in the Technical support forum. ;) that said, ST lacks a coherent stratgey to collect and evaluate bug reports and feature requests. There's a technical support forum, but that can mean anything from "how do I do X" to "Here's a bug" to "I want the API to do this". It needs a bug report flow with clear rules, like you need to add the steps to reproduce, and a status indicator such as acknowleged, wontfix, the option to reference duplicates etc. User Echo kind of works for feature requests, but it seems to be abandonded as well. There's now a community bug tracking project, but jps has been silent on that too. I know it's not easy to handle support, but there's a lot of room for improvement here.
Agreed. I had searched for a couple minutes to make sure I was putting the bug in the right place when I reported it. And even then there was no great way to search that it wasn't a duplicate considering how easy it is for forum posts to collide on a search.
I see new API stuff added all the time in the ST3 alpha update notes.
Plus: what are those "small bugs and inconsistencies"? I've been using ST2 for a year, and ST3 since it was publicly available an an alpha, and can't remember anything other than totally insignificant issues.
