1. 41
  1.  

  2. 7

    This would benefit from a clearer title and more exploration of the issue. There are definitely cases where products on a slower development pace suit my needs better. At other times, I need the pace of development because the product is immature. This equation has changed as I’ve gotten older.

    The question is also the question of how much the experience is compromised with change. My favourite editor on Windows is EmEditor. They have managed to jam in an Excel-like interface for dealing with very large, delimited text files, yet the performance of the core feature set is not diminished. I get the feeling that they won’t compromise in the same way as more bloated products when changes are made.

    The control over each compromise is greater in smaller teams. I would expect that the VS Code developers spend some degree of effort policing and trying to reign in bad plug-ins, or doing extra review on the first contributions from outsiders, that they wouldn’t do if they controlled every single detail.

    1. 5

      Sublime Text is fast with just enough functionality for me to keep it open constantly. I use it as my go to scratch pad - notes, code snippets, etc. I don’t use it for coding much, but I appreciate that power. If I need to quickly format a chunk of json, or pop open some random source file, ST is my first choice. I hate to lean on an over used expression like “Swiss army knife”, but when I consider how much time the sensible regular expression support alone has saved me when I need to wrangle text and source, Swiss Army knife fits. I’m also a huge fan of the way it saves document state without prompting.

      VSCode, on the other hand, seems like the defacto editor today for substantial JavaScript code bases or code bases that need (or want) additional tooling. I haven’t run into the plugin issues the author mentions, but I try to stay out of it if I can, so I’m not a heavy user.

      However, I’ve spent more time than I’m willing to admit trying to get niceties like decent LSP support, or node debugging, or similar working in (spac)emacs and vim. 90% of what you want is there, but getting that last 10% is a time-sink. VSCode just works. It’s fast and impressive for what it is but I still find it still slow compared to … well … basically everything except IntelliJ or eclipse. One day I’ll probably get around to seeing how neovim integration works, but until then I’ll just hold my nose and pop open VSCode when I find myself spelunking in messy js projects.

      1. 4

        I still can’t get myself to like VS Code. I know everything works on VSCode, but so does everything in my sublime and my bash terminal and a few other tools. Part of what bothers me about VS Code is that it wants to do everything for me, but it can’t. It will gladly give me a terminal. Even many terminals. But the terminal is not just as full-featured as, say, Terminator (or iTerm2 if you’re on a mac). VS Code is fast, with completion, with compiling, checks. But it’s not just as fast as sublime or IntelliJ. VS Code wants to do my Azure/AWS deployments for me. But it can’t do everything that I need from it. So by trying to do everything for me, it doesn’t give me the one thing that I needed from it perfectly. Maybe I’d find a great workflow if I used it for a month or longer. But I just can’t.

        At work I use IntelliJ. I like parts of it, it packs a bunch of features that I find useful. But it’s a little slow sometimes, and sometimes wants to do too much. All in all, for the types of projects I’m working with, it does a good job.

        But I always have a ST instance or 3 open on the side. My scratchpad. Simple demos/POCs that I just started and don’t yet want to fully commit to.

        It is very fast and very nice.

      2. 5

        To me, the main argument of this article is a solid argument in favor of open source software.

        You can use ViM, Xfce and Zsh and have an environment where very litte changes, for decades. Who knows what happens to Sublime (perhaps on yet to be invented CPU architectures) if the company goes bankrupt or is sold.

        Open source remains. As long as there is a minimum of interest in keeping it alive, it is maintained.

        1. 4

          The lack of change was a problem for me when the linter started to highlight my Python 3.6+ syntax as errors. In fact, it was the final drop that made me switch to VSCode and its very up-to-date Python extensions. :(

          1. 18

            Um. The linter is a plugin, there are plenty of other options there. Not really fair to blame the editor itself for that. I’ve been using “Python Improved” and never had any issue.

            1. 1

              Sounds to more like python changes are what broke things.

            2. 3

              While I agree with the premise here I also feel like this applies to pretty much all text editors like sublime. I can use a 20 year version of vim and not know the difference either.

              1. 10

                That’s kind of the funny part. I assumed it was a sly reference to Bram Moolenaar’s brag about Vim:

                What Vim provides is the promise that the things you learned will keep on working. Other programs bring out a “new and improved” version where functionality has moved around, and it takes a while before you can work effectively again. Vim, and Vi before it, has set a standard. And you can trust it to keep working on all your computers.

                But if the author is genuinely unaware of this interview, that’s even funnier.

              2. 3

                The features are just right. If they could just get their memory leaks under control.

                1. 5

                  I’m not aware of any leaks in the core, although we do cache some things, so we won’t release the memory since it would just require re-calculating again the next time it is needed. Plugins definitely could be leaking. Probably https://forum.sublimetext.com would be a good place to debug/diagnose.

                  1. 1

                    Removed all packages except for Package Control (v3.4.0). Still leaks.

                2. 3

                  I think that this hits on an important point that applies more broadly in computing beyond just text editors, or even programming tools.

                  Programs which frequently change their UI are fundamentally disrespectful to the user, because they ignore the time the user has already put into learning the UI for version $n-1.

                  If you put lots of time into learning how to use, for example, MS Office $CURRENT_YEAR, but the UI changes considerably in $CURRENT_YEAR+1, the time you put into learning the previous version has now been wasted. This is something I see non-technical friends and family complain about all the time – the constant churn of features/UI in nearly every popular software package.

                  I think us technical folk are isolated from this to a certain extent. If you use vim, sublime, or some other editor like that in a UNIX environment, you could have learned a workflow 20 years ago and still use the exact same workflow today. New features aren’t added that often, and when they are, it’s usually done in a way that doesn’t break/change existing workflows. Releasing a new version of Bash that has $HOT_NEW_FEATURE, but can’t run existing scripts correctly would never fly; no distro would adopt it, and a dozen forks would be made within hours.

                  Of course there is a balance to be struck. Obviously it’s absurd to argue that no UI should ever change or improve ever. However I think many modern software packages have gone too far towards constant change and could stand to slow down a little. I won’t speak to VSCode though, since I don’t use it.

                  1. 3

                    I recently got super frustrated with Atom and it’s constantly evolving electron cancer. A code editor shouldn’t be eating up half my cores and 4GB of ram.

                    I went back to Sublime3 and dear god, the speed! Fast, native loading times are super nice. The only thing I don’t like .. it’s commercial.

                    I really love open source, but the FOSS community has nothing comparable to sublime, that isn’t horrible electron cancer. I feel like I should try to contribute to Lime, but it looks like development there has stalled for a while.

                    I may reinstall kdevelop and try it again. The current state of FOSS code editors/IDEs isn’t that great.

                    1. 1

                      Depending on your requirements, Geany might be a nice fit.

                    2. 1

                      The current version, ST 3, is the same version that I used a year, two years, five years ago. And ST 2, released twelve years ago, is very very close to what I am using today. ST 4 is currently in alpha, and I honestly can’t tell the difference.

                      I’m not sure the developers of Sublime Text would be too happy with this endorsement.