7 ms·
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 qu
by danpalmer 6y ago
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.
- slifin 6y agoMaybe 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
- danpalmer 6y agoOpened 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.
- benfrain 6y agoHere’s the discord server https://discord.gg/D43Pecu https://discord.gg/D43Pecu 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!
- danpalmer 6y ago> 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’.”
- whywhywhywhy 6y agoThis 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.
- apozem 6y agoAbsolutely. 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.
- ric2b 6y agoI agree, but with the option to keep whatever version you had when you stop paying the subscription. Maybe applying only after a N consecutive months with an active subscription, to prevent paying for a single month behaving as a lifetime purchase.
- aembleton 6y agoThis is what JetBrains does. They give you a perpetual fall back licence to where you were 12 months ago. More info: https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-perpetual-fallback-license- https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
- azornathogron 6y agoGod 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.
- wbond 6y agoJust 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!
- Narretz 6y agoDevelopment 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.
- dangelov 6y agoI 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.
- kamranjon 6y agoIf 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.
- jonnytran 6y agoWhich plugins do you use exactly? The last time I tried to set this up, there were multiple options, and I ended up never really figuring it out.
- danpalmer 6y agoAs 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.
- donatj 6y ago> 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.
- tehbeard 6y agoI think the implication here is a switch of which tool is your "daily driver", the one you lean on for most common tasks.
- bdcravens 6y agoI keep Sublime around for opening giant files, which it is the best by far, but like many, switched to VS Code for development.
- tartoran 6y agoNever 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?
- bdcravens 6y agoI'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.
- spurgu 6y agoIt 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.
- Arainach 6y agoAgreed. 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.
- kamranjon 6y agoI 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.
- danpalmer 6y agoI 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.
- kamranjon 6y agoHmm 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).
- kstrauser 6y agoThat’s the one reason above all others why I stopped using ST. I just couldn’t get it to work at all.
- retSava 6y agoI 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.
- thaumaturgy 6y agoThis 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.
- jrochkind1 6y agoYup. 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.
- signal11 6y ago> Oh wait, will we need to pay to upgrade to ST4? Maybe not. Depends how/when you bought it, I think. From https://www.sublimehq.com/store/text https://www.sublimehq.com/store/text: > 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. Edit: the site seems to be a bit inconsistent about pricing info. https://www.sublimetext.com/sales_faq https://www.sublimetext.com/sales_faq says: > Licenses purchased for Sublime Text 3 do not expire, however an upgrade fee will be required for Sublime Text 4. Can anyone please clarify what the correct answer is?
- fprog 6y agoFrom the FAQ on the Sublime Discord: > 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.
- ggregoire 6y agoI've switched from ST to VSCode 5 years ago and never looked back.
- 6y ago
- mikece 6y ago"...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!
- wbond 6y agoWe 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. ;-)
- vagrantJin 6y ago> virtualenvs/per-project config/etc 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. But I do hear your point.
- ybbond 6y agoabout the release cycle: 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.
- achikin 6y agoI 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.