1. 35

Major feature additions are:

  • git integration
  • incremental diff
  1.  

  2. 10

    And they seem to have switched from gtk2 to gtk3, which is nice since it now works natively on wayland.

    1. 9

      This is a message for SublimeHQ: Build a terminal emulator and I’ll be yours forever.

      1. 1

        Yes!!!!! Oh yes!

        1. 1

          What are you missing in existing terminal emulators?

          1. 3
            • Cross platform
            • Works with PowerShell and Cygwin/Bash/WSL on Windows
            • Lightweight
            • Opens fast
            • Being able to operate a terminal emulator (opening new sessions, tabs…) by commands and not only by GUI or shortcuts, just like Sublime Text/Merge does.
            • Beautiful color schema by default.

            Cmder, ConEmu etc in Windows works nice, but slow, and there are some perks. Git Bash works fast but have more perks. Hyper, Terminus and every other Electron-based solution is just out of the board by default because memory footprint and terrible performance.

            I know there are things in Windows that are broken and aren’t the terminal emulator’s fault, but it could help on mitigation sometimes.

            1. 2

              Alacritty?

              1. 2

                I’ve been trying it out, seems promising, but in Windows there are many issues yet (which reminds me, maybe should open an issue in their Github), and isn’t the fastest opening up right now.

        2. 8

          My favorite text editor. I started learning to code with it and I’m still using it almost seven years later. Native Git support is nice - no need for the GitGutter third-party package.

          1. 5

            Uninstalling GitGutter was one of the first things I did after this update - nice to see they’re taking what they’ve learned from Sublime Merge and applying it to Sublime Text.

            Also, looking forward to the variable support in themes. Might make it easier to make a sublime-text set of base16 themes based on the new builder. :)

            1. 3

              Nice to see. I am all in on VS code though now.

              1. 4

                Noice!!! No electron/atom crap.

                1. 1

                  I went from vim to sublime to vim around 6/7 years ago. This was back at sublime V2 though I think where it was a crapshoot what you were going to get when you installed a plugin, if you managed to filter through the 30 odd ones for what you wanted. I still have v3 installed but only use it sporadically to edit plaintext or copy text. I used IntelliJ for a while, but once my main project got bigger, the typing lag started to drive me completely insane and I went back to vim. I tried vscode, but it just felt like baby IntelliJ and I don’t want to go down that road again. IntelliJ starts to force you into a situation where your project could easily be a bad time for another developer joining that doesn’t have IntelliJ and vscode felt like that in its infancy.

                  I do try these things. Sometimes for extended periods of time, but I always end up back at vim just because it’s ubiquitous for me and the typing lag though not nonexistent, is still pretty minimal at the worst of times. I can work around everything else I need like debuggers and build systems, but if the editor typing lags it’s like fingernails on a chalkboard for me.

                  1. 2

                    i’m a fairly decent vim user. My problem with becoming a “power” vim user has always been about the explosion of options once you step out of “a few configs in .vimrc” range.

                    1. 1

                      Yeah I completely understand where you’re coming from. It’s gotten better over the years though, it used to be in order to support different languages, plugins and stuff you had to put a metric ton of effort into your .vimrc file. Nowadays I take a “less is more” approach to things, I think my .vimrc file is only about 200 lines and I use ~10 plugins through Vundle with minimal configuration changes. I’m pretty brutal about cutting out a plugin if it’s problematic or doesn’t do what it says on the tin, or it’s something I can just do on the command-line or in a Makefile/sh file.

                      I use iterm2 instead of tmux as I can’t seem to keep all the keymappings in my head so I can use the mouse to split views, resize them, etc…

                      To be honest, IntelliJ and Sublime both have vim emulation layers you can install/enable. But at the end of the day (for me) it literally boils down to the typing lag. I’ll go with whatever lets me write my code the fastest without frustrating me and it just seems to be nvim at the moment that has that in spades, though I may look at Sublime again and try the vim emulation layer with it, but no one ever has an ergonomic keymapping to go from the editor to the file tree and navigate that with vim keystrokes that I’ve seen.

                  2. 0

                    Did they make it good yet? Like, does the windowing API for plugins still segfault if you send it the wrong thing? 😛