Sublime Text has the strangest development cycle I can think of.
It does big-bang releases with lots of features, followed by frequent bug fix releases that quickly resolve issues, followed then by years of silence even though there are still issues... until there's a major version bump and the cycle starts again.
This then means that the plugin ecosystem is fairly under developed and inactive because there's little incentive to actively develop plugins for software that appears to be dead.
I used Sublime for many years and it was hard to let it go, the speed was great and the SublimeGit plugin was the best Git client I've used, but multi-project development was a pain because the Python/JS/etc plugins didn't have good support for virtualenvs/per-project config/etc, and it was clear that they were out of active development.
I switched to another editor and it's slower, but fast enough. It's not quite as nice in many ways but it's nice enough. Critically though it's got a great plugin for most things.
I keep hearing the argument that the plugin community appears to be dead, but I've never had any issues. It pretty quickly got support for LSP and that covered most languages I use. The JS plugins for specific libraries like react/JSX/Sass are great. There is some configuration you have to do for some plugins but that's the case with any editor.
I actually really like the development cycle, if it allows the devs to keep the same payment model, I'm all for it. Also sublime merge is just awesome, I will pay for and support whatever they build cause they seem to really understand what users want and put out really good quality software.
I had many issues with the Python ecosystem. It's fairly fundamental to multi-project workflows to be able to use virtualenvs. Most of the community and tooling has centralised on them at this point. With VSCode you can launch the editor from a Terminal session with your virtualenv activated and it "Just Works". This will for the most part pick up your auto-formatter if you have one installed, that formatter will use the config in your project directory, etc etc.
With ST3 and the available plugins I was at the stage of editing my config every time I switched project to configure the paths, and it still didn't work as expected. Getting plugins to use config from a project directory rather than their own config was often impossible (e.g. black formatting plugin using pyproject.toml instead of the sublime black formatter configuration).
If I was working on projects with no other developers this might not be much of a problem, but working on a team where all canonical config is committed into the repo was essentially impossible.
Hmm I'm not super familiar with python ecosystem though I know some python devs at my company also use sublime.
In the JS ecosystem there are quite a few project specific configs (prettier, eslint, nvm) that seem to be read in by sublime and accounted for fine from project to project (possibly requiring package level config in some cases).
> I keep hearing the argument that the plugin community appears to be dead, but I've never had any issues.
As someone who moved from Sublime to VSCode, my experience was that I didn't exactly 'miss' crucial stuff in the former, but found things to still be better in the latter.
If I wouldn't be using VSCode, I'd probably not miss too much, but using it and its plugin ecosystem, it's hard to go back to Sublime as my main editor.
This seems an increasingly common dev cycle on software that hasn't adopted subscription pricing. See it a lot in the Mac ecosystem, big numbered release that you need to pay again for, fast follow with about 4 bug fix releases then silence for 3-5 years and repeat.
Just to clarify, we’ve done major releases in 2016, 2017, 2018, 2019, and now early 2021. We also released a second product (Sublime Merge) in 2018 and did a major release of that in 2020.
There haven’t been any significant gaps in our release cadence since before I joined the company in 2016.
That said, the current dev cycle has been a little longer because people do expect more from major version releases. We’ve got a large collection of new features, improvements and bug fixes coming with this release.
We’ve addressed over 600 issues on GitHub in the current release, added some pretty significant changes, and laid the foundation for more to come. IMO, it is by far the most significant release we’ve ever done.
We’ve also got some changes planned to help shorten our release cycles moving forward!
Interesting. As a long-time ST user, I was unaware that the level of ongoing work on ST is what you say it is.
I'm not interested in using a discord server to keep up.
But a monthly blog post with "what's happened in ST this month" might go a long way for letting users understand that it is still alive. The monthly post could even include things happening in the plugin ecosystem, interesting new plugins or popular plugins with new releases. But just 2-3 paragraphs a month would suffice.
As it is, I go to the ST website and it looks like it's stagnated, I see no sign of life. I'm not interested in intensively following dev releases, but I am interested in every once in a while checking out what's been going on that I might want to know about, and seeing evidence that ST is still alive.
I don't know for sure how typical I am, but based on this HN comment thread, I suspect I'm not alone.
Maybe a Twitter account that focuses on what's new and what's coming down the pipe? Most people don't really follow forums. The current Twitter account last tweeted about Sublime Text in March 2019, I think -- exactly 2 years ago.
I guess the blog could also work, especially if it auto-publishes to social media, but of late that too, like the Twitter feed, has been mostly about Sublime Merge -- whereas I care a lot more about Sublime Text.
I think Sublime is really good and has lots of value even in a world with VS Code, but it's important to ensure people inclined to giving it a go sense that the project is ticking along well.
I know you have your reasons and I won't question your capacity or vision, but I'd definitely be more interested in an active 'Sublime Text' that is maintained on an ongoing basis than the current major release model you have.
Back when ST started to get popular, you were up against Notepad++, TextEdit2, Visual Studio perhaps, and others. Now there's Atom and VSCode that are actively maintained and have active communities. I doubt I'll use ST4, but I wish you all the best, but I do think the model is wrong.
The “active” version of Sublime Text are our development builds.
We’ve just been releasing those discreetly during this current dev cycle since we’ve got a huge user base and wanted a smaller group to test some of our bigger changes on.
For our future dev cycles, our dev builds will be returning to our site.
Instead of taking 2 years to close 600 issues, why not ship a release each month with just a handful addressed? I think plugin developers are more likely to keep their plugins maintained if it looks like Sublime Text is alive.
I'd much rather pay $50 a year for ~monthly releases than $70 every 2-3 years for one release and a few bug fixes.
Part of our development pace is that we are a small team (six engineers), bootstrapped, maintaining multiple products, and looking to do things in a way that fits with our vision for the products. We want to build products that are around for the long haul – Sublime Text has been around for 15 years. We'd rather focus on quality and performance than adding lots of features.
We are doing a big release because our current licensing scheme requires a "major version" release for paid updates. If we did a release once a month, they would all be trivial features, and wouldn't justify a major version bump.
For license holders, we've actually been shipping new dev builds every one to two weeks. However, since this is a major release, it has some very significant changes that need testing, refining and polishing. I don't think anyone in their right mind would ship a half-finished product and call it a major release, so we've been doing the work that shows it is a major release. The downside of bigger releases is that sometimes they end up dragging on a little longer than you want, and we'd rather uphold our vision for the product than have a release done a few months earlier.
As I mentioned in my post above, we've got some changes coming that will help address the "major version" issue and allow us to take on a faster release cycle. That said, I'm not sure I agree that new releases once a month are a good fit for the majority of users. We do, however, provide dev builds for users who do like seeing changes quickly.
We've got a super active group of some of the more prolific plugin developers that we interact with on a daily basis on our public Discord server. They definitely provide a lot of feedback and we make a point of listening to what the have to say.
The reality of it is that most open source developers wax and wane in their development work. The ones who stick with projects for years and years tend to either do open source work related to their day job, or are at least partially employed to work on the open source work. Others will get an itch, scratch it, share it, improve it and then be satisfied.
I’m saying this because I like Sublime Text and want you to succeed:
As an end user: that model doesn’t work for me at all. Most other apps I use get regular feature and bugfix updates and I admit that I’m spoiled by those regular updates. That ST2 went so very long between releases made it feel like a dead project. Even if behind the scenes it was still active and healthy, I didn’t see that and couldn’t tell the difference between “actively developed, thriving project that just doesn’t release often” and “developer woke up one month and thought ‘hey, I should close a feature request or two this quarter’”.
Again, I’m definitely not arguing that you’re not hard at work on it. I mean this in the spirit of feedback: as an end user who wasn’t active in the plugin developer forums, I didn’t realize anyone was still working on it full-time. And because of that, I stopped using ST because it felt like it was a dead end and I wanted to put my mental resources toward learning and using something still alive and thriving.
By “feels” I meant “as far as I can tell without investing a ton of research”. Dead projects don’t get bugfixes, or builds for new versions of the OS. They’re ticking time bombs. I would not voluntarily use an abandoned product, and would much prefer investing my time getting good at a maintained one.
Turns out ST wasn’t actually a dead project, although it seemed like it. The ST team probably lost more users than just me from not communicating.
It is a text editor. A really good one. It could edit files really well last year, and continues to do so really well now. Which possible bugs can be surfaced day to day, or week to week that need fixes?
I am glad to pay for software that doesn't keep me on the run like a treadmill. It is possible for software as simple as a text editor to be "finished".
Plugin developers do care, there are so many active maintained plugins now dead, for me the 2 Go official plugins had been abandoned for years, they didn’t even bother to merge bugfixes.
+1, I've used ST for ~6 years now and never had any issues. To me it just feels solid to not get updates every damn week but instead every couple of months where I browse through the changelog and then go back to using an awesome editor.
Really excited about ST4, looks like a major upgrade!
I like VSCode, and I use it for a lot of IDE-like stuff. But for normal reading and writing code? I use Sublime Text. Sublime Text is so much faster and more fluid, and able to handle much larger files, and has a better set of text editing tricks in my opinion. And that is worth enough to me that I wouldn't trade it for being able to do everything in one editor.
Sublime + plugins has "enough" features that I only switch when I really need to. And while I can't put my finger on exactly why I feel this way, text just seems to look more pleasant than on other editors, even when using the same fonts and similar color schemes.
I didn’t mention VSCode in that comment, and I don’t think it’s really relevant to what I was saying. I switched from ST to a different editor (and not directly to VSCode) because I was under the impression that ST was no longer being actively developed. I don’t have anything bad to say about ST other than I didn’t like how it didn’t handle Python project environments well, and if I had believed it was still being actively worked on, I might have stuck with it.
> For license holders, we've actually been shipping new dev builds every one to two weeks.
I'm a licence holder and I haven't seen an update since October 2019. Despite reading most of this thread I haven't managed to figure out where any more recent releases are. Can you point me towards them?
Respectfully, ST devs, I think you might need to have a hard look at how you do customer communication. I stopped using ST essentially because of stagnation that hadn't actually happened!
> Respectfully, ST devs, I think you might need to have a hard look at how you do customer communication
You have really odd expectations of a small team making a targeted tool and for which you have expounded at length about how it doesn't work for you. Cool beans, my dude.
I love Sublime. The devs have earned a good portion of my trust to keep on rocking; they'll get my license fee whenever they ask for it (the benefit of trust).
I just find it odd that they'd lose customers over lack of communication. I'm not the only person in this thread who didn't realise it was under active development.
I'm all for small dev teams doing things that let them stay small, but we're not talking about substantial changes here, we're talking about a sentence on their website saying "ST4 is in active development, you can follow progress on the forums", or other small changes like that.
> You have really odd expectations of a small team making a targeted tool and for which you have expounded at length about how it doesn't work for you
I actually agree with the parent.
I've been a long time ST, and I've found significant limitations and bugs; since they haven't been fixed/improved for a while, and there were no news, I switched, and I'm not going back again.
While the parent's post may have been better phrased, I think that it's correct that with a better communication, they could have retained more customers.
You need to join their Discord to find the Sublime Text 4 dev channel. It's not marketed anywhere, you just have to have searched their forum for it. https://discord.gg/D43Pecu
Sublime Text 3, as you say, has gone without dev updates since 2019 with no announcements about why or pointers to the new version.
Yes, they're very bad at some of these communications issues. :D
We intentionally decided to have the dev builds for ST4 go to a smaller group of people, paired with a low-friction communication medium.
Clearly you disagree with that decision, but we do communicate with our users pretty much every day. We simply decided trying to communicate and gather feedback from tens of thousands of users was less productive for a team of six than hundreds of engaged power users.
My only disagreement with your chosen course was the lack of update on the ST3 dev builds page. As-is, it gives the impression to users like the ones I replied to that there's no progress being made.
Sticking a note at the top of the ST3 dev build page akin to the one on the ST2 dev builds page, even without a link to the discord or new builds, would have changed their perception of things.
Or even just a post on your news blog that you're moving active development to an upcoming version? A pinned post on your forum? There really was no communication to users who're not actively involved in the community, that I could find.
While posting new builds in a not easily discoverable location is technically compatible with the statement of:
> For license holders, we've actually been shipping new dev builds every one to two weeks.
In practice the result is that (by stated design) the majority of sublime text license holders will not be aware of new builds for several years at a time until they are announced in the easily discoverable public location again.
I think it's good for them to pursue whatever development and community engagement model feels most sustainable, but it is disingenuous to claim that both users have access to the current dev builds while also trying to hide those builds from most users.
Am I in the minority that I don't want to see updates monthly for a desktop application? It seems like every time I launch paint.net, for example, it wants to update. I don't want to update! I want to edit an image.
If I used paint.net 8 hours a day on daily basis as I do with VSCode, yeah I'd would probably want to keep it updated as much as possible. Also I rarely "launch" VSCode, it's always open. Which means the updates are downloaded in background and it just shows a small icon at the bottom right when it's ready to be restarted. It's almost invisible and doesn't bother me at all, and I can wait as much as I want before restarting it.
BTW paint.net has the best integrated auto updater I've ever used. It notifies at startup but has "Install When I Exit" button on update notification dialog. Of course auto update by package manager is still better. (paint.net also available on Windows Store)
Since there were a lot of people clamoring for more updates, subscription licensing, etc. I just wanted to add some volume to the opposing viewpoint.
I registered my copy of sublime text maybe 8 years ago. Before that I had used Notepad++ for years as well. I love that sublime is a thing that I paid for once and I can trust that it will always fundamentally work without problems for my basic use cases. I never have to think about "oh well I'm not doing so much text editing at the moment, maybe I'll turn it off for now..." like I do with some other subscriptions. I'm not worried it won't work or will degrade because it seems stable as a rock. I primarily used Windows when I bought it, and I've been Mac only for 4 years, and it's still with me.
Sublime text is special and I love what you guys have done! And I appreciate that for my $80 or whatever it was, I can use this thing the way I use it right now and never worry about it again.
Honestly, I think people are being reactionary from how common abandonware is in the open source community (obviously sublime is closed source, but people who use sublime use a lot of open source), as well as the long delay between ST2 and ST3. I remember plugins with docs that said "I have abandoned this project because Sublime Text is dead" when ST3 was still in beta. It is... probably not great that when I check the About window on my copy of SublimeText, it says Copyright 2019 and the changelog on your website says October 2019. It is useful for a customer facing product to not look dead, but this is completely possible without being forced to ship updates or features on a regular basis. Just be mindful of customer perceptions and what the touch points are and be patient and consistent within your bandwidth.
I've wanted to buy Sublime Text for a long time, but I couldn't justify it due to:
> A license is valid for Sublime Text 3 [...]. Future major versions, such as Sublime Text 4, will be a paid upgrade.
> [...] an upgrade fee will be required for Sublime Text 4.
I'd feel pretty bad if I bought ST3 and the next day you'd decide to release ST4 and now I'd have to pay for an upgrade. Why not just stick to the terms on the buy page:
> Personal licenses are a once off purchase, and come with 3 years of updates. After 3 years, an upgrade will be required to receive further updates.
Why not:
> [...] come with 3 years of updates *regardless of version*.
Then I wouldn't have to worry about a new release being right around the corner.
As it's now I can only feel comfortable buying ST when a new major version comes out, which sucks. I could have bought it years ago.
I understand that providing release dates of future major versions can be hard but could you at least show the cost of the upgrade?
Sublime is great btw, I'll definitely make a purchase once ST4 comes out <3
Do you have any options for a reduced cost license? Ideally I get enough value from the tool that I'd like to contribute financially but the current cost is (for me) too high. Perhaps I should just continue with the occasional nag popup.
I really enjoy using Sublime Text for some parts my daily workflow yet that equates for me using like 5% of the actual functionality. I don't actively write code within ST but use it for stuff surrounding my coding workflow.
Nonetheless, thanks for the product. I really enjoy it.
edit: lol downvotes because I'm trying to give someone money
I bought the product in 2015. I don't remember the cost but let's assume it was $80. (EDIT, I just looked and it was $70 at the time) That's $16 a year. If you use even 5% of the functionality, isn't it worth that? I don't know what country you are from and there my be economic differences but sublime text has been one of the best software purchases I've made. It's worth every cent.
If you don't feel it's worth $80, you can use Visual Studio Code for free.
I don’t understand this whole threads obsession with updates. ST has always seemed like a finished product to me. Always does what I expect and is stable. I’m happy for paying the price I did for the features I got at that time.
I didn't pay $80 for an editor that doesn't provide updates. I paid $70 for 5 years use of an editor that has updated a major version and a few minor versions and that I've installed on many workstations and VMs through the years. I use it every day so I'm glad I paid.
The parent commentor said they are already using it and will continue to do so without paying. Neither of you need to pay for the editor if you don't like it. Just use a different one.
No, the downvotes are because you aren't willing to pay a very fair price for the product and have admitted you depend on it and use it without paying and will continue to do so.
Absolutely. If a developer can only cash in on a big-number new version, that incentivizes holding back features to sell the new version. It just does.
I understand the frustration with subscription pricing, but it's a business model that actually aligns my incentives with the developer's. I want an up-to-date product and they want ongoing revenue for their ongoing work.
God no. Subscription has the opposite problem that the publisher is incentivised to keep changing the damn software underneath me. It means I can't decide "this version works fine for me, I'll just keep using this for the next decade", which is something I totally can do with Sublime.
This was how the majority of software development was done before Hamster Wheel Development became popular. There are a lot of people who prefer their software to just do each day the same things it did the previous day and not require a lot of attention beyond that.
Yup. Twice now I think "I guess the dev is probably just sitting on all the money they made/are making now, there probably wont' be any more dev" -- to be surprised by a major release.
Wonder what's going on there.
Oh wait, will we need to pay to upgrade to ST4? That would explain it -- but unclear, ST3 was offered as a free upgrade to ST2 licenees I think.
At this point, if you had to pay to upgrade to ST4, I wonder how many people will be lost to VS Code instead. I hate learning/setting up new tools, but if i have to pay to upgrade to ST4, I'm gonna consider trying to switch to VS Code instead, which I hear good things about, seems very similar to ST, seems actively maintained, and is free. There is nothing I am aware of that is in ST but missing from VS Code, I've just been using ST since before VS Code existed.
I down own a sublime license myself as I prefer intelli-j, but I never understand the aversion of developers to pay for tools especially what is easily the most important tool they use.
I've had colleagues marvel at the capabilities of my editor, then ask if it is free, then grumble and go back to wasting hours at a task I just showed them how to do in seconds.
These are developers making closer to 200k than 150k, and they will just not buy software!
> Personal licenses are a once off purchase, and come with 3 years of updates. After 3 years, an upgrade will be required to receive further updates. One license key is all you need for all your computers and operating systems.
> Any license bought after Sept 2019 warrants three years of updates, including "major" ones, analogous to the Sublime Merge licensing model. A road for upgrading a previously purchased license (potentially recently) has not been decided on yet.
Development for v4 has been going on semi-publicly on Discord for 2 years now. For Sublime Text 3 the dev builds were on the website, and im both cases the dev builds can be used as daily driver.
Regarding plugins, Language Server Protocol really helps against defragmention and dead projects. There's an actively developed LSP plugin that theoretically works with any server.
I really like(d) Sublime and used it till somewhat recently. If there was semi-public development going on, it wasn't very discoverable.
Just tried the LSP plugin before reading your comment. Wanted to use it for Go development, but it can't even do basic autocomplete or suggestions. Actually, I can't even tell if it's running. The VSCode PLS gets stuck sometimes, but 99+% of the time it works great.
Even so, damn, Sublime Text is fast. I really do wish they catch up in other aspects.
If you don't have autocompletion and suggestions working with LSP and Go it's almost certainly not setup correctly. I use it every day and it's great, the goto method def and preview popups are super slick too.
As a previous customer, who is very interested in being a customer again in the future, I can find no mention of Discord on the website, no development activity since Oct 2019.
Even if I could find it, distributing releases via a chat room feels a bit 90s. I'd expect to just get auto-updates through the auto-update mechanism in Sublime Text.
> I switched to another editor and it's slower, but fast enough.
I never understand the desire to switch. An editor is a tool, and I keep multiple tools. I use VSCode, Sublime and various JetBrains products and often have all 3 going at the same time. They all have strengths and weaknesses.
Never tried sublime before but I use Notepad++ for large files. Sublime does look sublime. Does it have a keyboard oriented workflow or is it for the mousey workflows only?
It has keybindings for everything, which is one reason I feel a bit stuck in MacOS as the keybindings are slightly different on Linux. Since I use them for pretty much everything I'd have to retrain my muscle memory quite a bit after switching to Linux.
I've never really had a keyboard-oriented workflow, so I can't really speak to it, but I know there are various tools available like vim-bindings, etc.
Agreed. VSCode became my daily driver for 99% of things, and ST only comes out for very specifics scenarios it does better - which for me means multi-cursor and rectangle select scenarios, since even though some of them are possible in VSCode, they're keyboard-only and nowhere near as simple or intuitive as they are in Sublime.
.....although apparently at some point VSCode finally added Shift+Alt+drag, so now I have no idea what reasons I'd have for opening Sublime.
To be fair, ST isn't an IDE. Handling virtualenvs and configs can be automated outside your text editor. I just use batch files and automate the sh*t out of setup including starting the project on ST.
We should do more simple automations rather than expect an already souped up, beefed up text editor to do everything and bake the cake.
I love it. There's not enough praise I can give it for reducing friction and making me more productive. Part of that comes from making it very easy to write plugins, so I can quickly make small plugins.
Was about to describe them but turns out to be quite long to do so didn't. :)
Edit: mostly write C, js/python, makefiles and similar things. Going to buy this again, perhaps twice just because they are def worth it.
"...followed then by years of silence even though there are still issues... until there's a major version bump and the cycle starts again"
Sounds like a band that releases a great album, does a bit of touring, and then breaks up because they hate each other.... and reunite a few years later and repeat the cycle. I've heard the comparison between musicians and developers made over the years, but this is a different spin on it!
We actually went from a singer/songwriter to a duo and then a full six-piece band between 2016 to 2019! We've been putting out albums and EPs quite a bit, just been quiet in the public sphere since late 2019 since we've been working on a double-album. ;-)
I agree, the plugin ecosystem is far from VSCode. I usually use Sublime/VSCode as a lightweight editor to learn new languages and technologies and VSCode plugins for Haskell/Clojure/etc are far ahead of Sublime. I don't care much about editor speed, but I do care about getting unfamiliar environments up and running as fast as possible.
from the release of version 3 to the upcoming version 4, they actually release a lot of beta enhancement, new features, bug fixes. the beta link is in their Discord forum, and can only be accessed if you have the license.
even though they dub the frequent releases as "beta", I never feel them as beta software because they are stable, very low occurrence of bug, and many major improvements.
Maybe it looks that way if you don't go out of your way to use or follow the Dev build but development has been consistent over the last couple of years
Opened Sublime text – no updates since Oct 2019. Went to the website – everything about ST3 from Oct 20190. Went to Download – Build 3211 from Oct 2019. "For _bleeding edge_ releases, see the dev builds" – last build September 2019, older than the stable one.
I'm all for using "bleeding edge" (although I don't with VSCode because I don't need to in order to have a working dev environment), but I've had a really good look in all the places I'd expect to see this and am thoroughly convinced that I'm using the very latest version of ST and that it is therefore out of development.
I understand that this thread saying something different, but if I've had a good look _knowing there is a later version_ and can't find it, then how would a customer know? A sufficiently hidden development process is indistinguishable from a project being dead.
Edit: really keen to use a later version if one is available, can anyone point me towards a download link? I own a licence for ST3.
I agree it’s not straightforward to know it exists but that’s probably the point. Once you do know I literally just googled ‘Sublime Text Discord’ and it was the first result. Look in the #announcement channel there. Been using v4 builds for months. Love it so much I’m recording a course on it!
> Once you do know I literally just googled ‘Sublime Text Discord’ and it was the first result
This is kinda my point. I don't know or even want to know about their Discord, I want a text editor that is updated more regularly than once a year.
It reminds me of that scene from Hitchhiker's Guide To The Galaxy:
“But Mr Dent, the plans have been available in the local planning office for the last nine months.”
“Oh yes, well as soon as I heard I went straight round to see them, yesterday afternoon. You hadn’t exactly gone out of your way to call attention to them, had you? I mean, like actually telling anybody or anything.”
“But the plans were on display …”
“On display? I eventually had to go down to the cellar to find them.”
“That’s the display department.”
“With a flashlight.”
“Ah, well the lights had probably gone.”
“So had the stairs.”
“But look, you found the notice didn’t you?”
“Yes,” said Arthur, “yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard’.”
It does big-bang releases with lots of features, followed by frequent bug fix releases that quickly resolve issues, followed then by years of silence even though there are still issues... until there's a major version bump and the cycle starts again.
This then means that the plugin ecosystem is fairly under developed and inactive because there's little incentive to actively develop plugins for software that appears to be dead.
I used Sublime for many years and it was hard to let it go, the speed was great and the SublimeGit plugin was the best Git client I've used, but multi-project development was a pain because the Python/JS/etc plugins didn't have good support for virtualenvs/per-project config/etc, and it was clear that they were out of active development.
I switched to another editor and it's slower, but fast enough. It's not quite as nice in many ways but it's nice enough. Critically though it's got a great plugin for most things.