![]() ![]() That ST2 went so very long between releases made it feel like a dead project. Most other apps I use get regular feature and bugfix updates and I admit that I’m spoiled by those regular updates. I’m saying this because I like Sublime Text and want you to succeed:Īs an end user: that model doesn’t work for me at all. Others will get an itch, scratch it, share it, improve it and then be satisfied. 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. The reality of it is that most open source developers wax and wane in their development work. They definitely provide a lot of feedback and we make a point of listening to what the have to say. 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. We do, however, provide dev builds for users who do like seeing changes quickly. That said, I'm not sure I agree that new releases once a month are a good fit for the majority of users. 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.Īs 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. 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. However, since this is a major release, it has some very significant changes that need testing, refining and polishing. If we did a release once a month, they would all be trivial features, and wouldn't justify a major version bump.įor license holders, we've actually been shipping new dev builds every one to two weeks. We are doing a big release because our current licensing scheme requires a "major version" release for paid updates. We'd rather focus on quality and performance than adding lots of features. We want to build products that are around for the long haul – Sublime Text has been around for 15 years. 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. 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. black formatting plugin using pyproject.toml instead of the sublime black formatter configuration). Getting plugins to use config from a project directory rather than their own config was often impossible (e.g. ![]() 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. ![]() 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 VSCode you can launch the editor from a Terminal session with your virtualenv activated and it "Just Works". Most of the community and tooling has centralised on them at this point. It's fairly fundamental to multi-project workflows to be able to use virtualenvs. I had many issues with the Python ecosystem. Critically though it's got a great plugin for most things. It's not quite as nice in many ways but it's nice enough. I switched to another editor and it's slower, but fast enough. 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. 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. until there's a major version bump and the cycle starts again. 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. ![]() Sublime Text has the strangest development cycle I can think of. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |