1. 46
  1.  

  2. 8

    I have a license for Sublime Text 2.0. Used the 3.0 beta/nightly builds and have to say I like where they are taking the editor. Would gladly upgrade to the new release but that will not happen until they provide BSD binaries - just can’t justify purchasing software that I can’t use on my main platform.

    1. 2

      I tried to resist, but I can’t help it: What do you use on BSD?

      1. 2

        recently mostly nvim but I stopped caring and being religious about a text editor. Just using what’s at hand (mg, vi, nvim, emacs) depending on the mood.

    2. 5

      Nice to see a release! I remember an earlier discussion where there was worry the project was dead.

      1. 1

        I thought that rumor was just someone’s misguided attempt to “motivate” Sublime developers to work faster.

        1. 1

          This discussion centers on it. The link to the actual story seems to be dead, so I think you’re right.

      2. [Comment removed by author]

        1. 10

          You’re saying that ST was great 4-5 years ago, but apart from the langserver, which one of your points didn’t apply back then as much as it does now? You say that “today there are better editors”, but surely vim is much older than 4-5 years and basically didn’t change.

          1. [Comment removed by author]

            1. 8

              The primary reason I stick with Sublime Text is that Atom and VSCode have unacceptably worse performance for very mundane editing tasks.

              I’ve tried to switch to both vim and Spacemacs (I’d love to use an open source editor), but it’s non-trivial to configure them to replicate functionality that I’ve become attached to in Sublime.

              1. 1

                I thought VSCode was supposed to be very quick. Haven’t experimented with it much myself, what mundane editing tasks make it grind to a halt? I am well aware Atom has performance issues.

                1. 1

                  Neither Atom nor VSCode grind to a halt for me, but I can just tell the difference in how quicky text renders and how quickly input is handled.

                  I’m not usually one of those people who obsesses about app performance, but editors are an exception because I spend large chunks of my life using them.

                2. 1

                  I’ve tried to switch to both vim and Spacemacs (I’d love to use an open source editor), but it’s non-trivial to configure them to replicate functionality that I’ve become attached to in Sublime

                  This is the reason who I stay with vim, unable to replicate vim functionality in other editors.

                  1. 1

                    Yeah, fortunately NeoVintageous for Sublime does everything I need for vim-style movement and editing.

            2. 3

              I think the really ground-breaking feature that ST introduced was multi-cursor editing. Now most editors have some version of that. Once you get used to it, it’s very convenient, and the cognitive overhead is low.

              As for the mini-map, I suppose it’s a matter of taste, but I found it very helpful for scanning quickly through big files looking for structure. Visual pattern recognition is something human brains are ‘effortlessly’ good at, so why not put it to use? Of course, I was using bright syntax hilighting, which makes code patterns much more visible in miniature. Less benefit for the hilight-averse.

              I’ve been using ST3 beta for a few years as my primary editor. I tried using Atom and (more recently) VS Code, but didn’t like them as much: the performance gap was quite noticeable at start-up and for oversized data files. The plug-in ecosystems might make the difference for some folks, but all I really used was git-gutter and some pretty standard linters. For spare-time fun projects I still enjoy Light Table, but it’s more of a novelty. I’m gradually moving away from the Mac and want a light-weight open-source editor that will run on any OS.

              So now, as part of my effort to simplify and get better at unix tools, I’m using vis. I’m enjoying the climb up the learning curve, but I think that if I stick with it long enough, I’ll probably end up writing a mouse-mode plugin. And maybe git-gutter. Interactive structural regexps and multi-cursor editing seem like a winning combination, though.

              1. 3

                You might enjoy exploring kakoune as well. http://kakoune.org | https://github.com/mawww/kakoune

                1. 2

                  I’m an Emacs guy myself and I honestly think that multi-cursor editing is just eye-candy for good ol’ editor macros, and both both vim and Emacs include them since… forever?

                  1. 3

                    I’ve never used Sublime Text, but I’ve used multiple-cursors in vis and Kakoune, and it beats the heck out of Vim’s macro feature, just because of the interactivity.

                    With Vim, I’d record a macro and bang on the “replay” button a bunch of times only to find that in three of seventeen cases it did the wrong thing and made a mess, so I’d have to undo and (blindly) try again, or go back and fix those three cases manually.

                    With multiple cursors, I can do the first few setup steps, then bang on the “cycle through cursors” button to check everything’s in sync. If there’s any outliers, I can find them before I make changes and keep them in mind as I edit, instead of having my compiler (or whatever) spit out syntax errors afterward.

                    Also, multiple cursors are the most natural user interface for [url=http://doc.cat-v.org/bell_labs/structural_regexps/]structural regular expressions[/url], and being able to slice-and-dice a CSV (or any non-recursive syntax) by defining regexes for fields and delimiters is incredibly powerful.

                    1. 0

                      [url=http://doc.cat-v.org/bell_labs/structural_regexps/]structural regular expressions[/url]

                      This might be the first attempt at BBCode I’ve seen on Lobsters. Thanks for reminding me how much I hate it.

                      1. 1

                        Dangit, you can tell I wrote that reply at like 11PM, can’t you. :(

                    2. 1

                      I agree with you. I use Vim, and was thinking about switching until I realized that a search and repeat (or a macro when it’s more complex) works just as well. Multiple cursors is a cute trick, but never seemed as useful as it first appeared.

                    3. 2

                      I thought multiple cursors was awesome. Then I switched to using Emacs, thanks to Spacemacs. Which introduced to me [0] iedit. I think this is superior to multiple cursors. I am slowly learning Emacs through Spacemacs, I’m still far away from being any type of guru.

                      [0] https://github.com/syl20bnr/spacemacs/blob/master/doc/DOCUMENTATION.org#replacing-text-with-iedit

                    4. 2

                      I’ve started using vim for work, and although I’ve become quite fast, I find myself missing ST’s multiple cursors.

                      I might try switching to a hackable editor like Yi. I’ve really enjoyed using xmonad recently for that reason.

                    5. 3

                      Immediately bought it - I’ve used Sublime 2 for ages without a license and it’s about time I supported such fantastic software.

                      1. 3

                        I used to run the beta, then about 9 months ago switched exclusively to vscode (Atom for me is far to slow to use every day). I didn’t need any of the extra features vscode had, but after using it for the whole of this year, it’s really improved my work flow, plugins just work, great community, easy to switch between languages and have all the features for X language.

                        I had paid for sublime, and used it for some time, but just never found it more than a tool, if I want something lightweight I’ll use vim. But spending over 6 hours a day in an editor for 9 months solid, I can only say good things about Vscode.

                        1. 2

                          Will be interesting to see if this release also means beta 4.0 comes out soon with little to no further updates to 3.0 final. Not complaining, I have a license and been using the 3.0 betas since 2.0 went final, just seems to be the way releases work for ST.