Sublime Text 3 marked as recommended build • Hacker News Board

Re: Sublime Text 3 marked as recommended build

#41

Post by jsmeaton » Tue, May 31, 2016, 6:39 AM UTC

hantusk wrote: post #39

ashworth wrote: post #30

Earlier quoted context omitted.

Genuine question: What do Atom and Visual Studio Code offer that Sublime Text doesn't? I have tried both within the last year and wasn't able to find any significant advantages (except for VS Code's excellent TypeScript experience), but they both ran slower and used more memory. Perhaps I should have used Nuclide? (Not asking about Webstorm because I've used the IntelliJ family of IDEs and understand their advantages…

I use Atom over Sublime Text solely for the Hydrogen plugin ( https://github.com/nteract/hydrogen ). That plugins are written in javascript (larger developer base) and allows more customization of Atom (more open plugin api) also yields more niche plugins.

In these threads I see "larger developer base" when referring to javascript developers over python. I wonder if that's true, and by what margin.

For what it's worth I would imagine more javascript devs would write plugins for Atom than python developers would write plugins for Sublime Text.

Re: Sublime Text 3 marked as recommended build

#42

Post by dvcrn » Tue, May 31, 2016, 6:39 AM UTC

ST3 has been stable for a long long time. It's great that they finally flipped the switch and replace ST2 with it. This also forces developers to finally adapt the new API and Python3.

Just too bad this came too late. I got frustrated with the plugin API long ago and no-brainer features like multiple elements in the gutter (which is needed for example for relative line numbers) have still not been implemented.

When ST3 development seemed to have frozen completely, a lot of plugin developers have moved on to other platforms like atom or vscode. Even with this release, ST3 needs something bigger to bring people and plugin devs back to the platform.

Once my ST2 license stops working for ST3 I will open the editor a lot less than I currently do but will monitor the changelog for long wanted features.

Re: Sublime Text 3 marked as recommended build

#43

Post by bjz_ » Tue, May 31, 2016, 6:42 AM UTC

shurcooL wrote: post #33

ashworth wrote: post #30

Earlier quoted context omitted.

Genuine question: What do Atom and Visual Studio Code offer that Sublime Text doesn't? I have tried both within the last year and wasn't able to find any significant advantages (except for VS Code's excellent TypeScript experience), but they both ran slower and used more memory. Perhaps I should have used Nuclide? (Not asking about Webstorm because I've used the IntelliJ family of IDEs and understand their advantages…

As a ST3 user, both Atom and VSC have superior git integration built in, no plugins needed. That's really the only/main thing I miss.

It's a small thing, but I really love how Atom highlights the files that have changed in the tree view out of the box. Haven't figured out how to do that in Atom...

Re: Sublime Text 3 marked as recommended build

#44

Post by ff10 » Tue, May 31, 2016, 6:43 AM UTC

To add to the confusion: it seems that build 3114, released on May 12th, labeled beta originally, is now designated as the ST3 stable release.

Re: Sublime Text 3 marked as recommended build

#45

Post by spoiler » Tue, May 31, 2016, 6:43 AM UTC

gedy wrote: post #35

DigitalSea wrote: post #22

I think ST3 really missed the boat. I used to love using Sublime Text 2 (occasionally I still do because it is fast), but I moved on when development stagnated and Jon seemingly disappeared off of the face of the planet, stopped responding to support requests and the like. There is no disputing ST is a great editor, but it has fallen behind in the face of Atom, Webstorm and Visual Studio Code (two of which are free).

Atom does not handle large files well at all compared to ST. I like Atom, but get very serious hangs with it on large files.

How large are you talking? I had similar issues early on with Atom, but I don't have them anymore (same project). Also, it would only hang for about a second when initially opening the file, later on it would work smoothly.

Re: Sublime Text 3 marked as recommended build

#46

Post by bjz_ » Tue, May 31, 2016, 6:44 AM UTC

mastazi wrote: post #29

DigitalSea wrote: post #22

I think ST3 really missed the boat. I used to love using Sublime Text 2 (occasionally I still do because it is fast), but I moved on when development stagnated and Jon seemingly disappeared off of the face of the planet, stopped responding to support requests and the like. There is no disputing ST is a great editor, but it has fallen behind in the face of Atom, Webstorm and Visual Studio Code (two of which are free).

VS Code is great, Atom too but I wish it was less buggy. Regarding ST, I used to feel the same but lately I have seen more releases and it seems that development is now moving again. Also, I'm really struggling to find any aspect where ST "lags behind", I pretty much seem to get all the same goodies that I get in Atom and VS Code.

VS Code seems much snappier than Atom, as someone who uses both. And the Rust extension is much better. Switching between the different key-bindings is a pain though - I wish VS Code used ST bindings, but I'm guessing they went for consistency with VS?

Re: Sublime Text 3 marked as recommended build

#47

Post by bjz_ » Tue, May 31, 2016, 6:47 AM UTC

rattray wrote: post #11

Scarbutt wrote: post #6

Is sublimetext as hackable(extensible) as emacs or atom?

It's not open-source, so generally, no. Packages are in python, and most of those are open-source (and thus available as examples) so extending through packages is probably easy.

With Atom addons can also do a great deal of UI customization too, due to the fact that it is built on the web stack. You pay for it in performance though...

Re: Sublime Text 3 marked as recommended build

#48

Post by provemewrong » Tue, May 31, 2016, 6:48 AM UTC

Scarbutt wrote: post #31

wcummings wrote: post #16

Earlier quoted context omitted.

Atom? Maybe. Emacs? Nope.

Well, in Atom you can replace any of the javascript Atom comes with with your own customizations, same in Emacs with elisp, where does the difference lie? (I'm a emacs/evil user).

I'm just guessing, but perhaps in the Elisp macro capabilities, that arise from the language's homoiconicity?

Re: Sublime Text 3 marked as recommended build

#49

Post by tomsmeding » Tue, May 31, 2016, 6:51 AM UTC

bjz_ wrote: post #43

shurcooL wrote: post #33

Earlier quoted context omitted.

As a ST3 user, both Atom and VSC have superior git integration built in, no plugins needed. That's really the only/main thing I miss.

It's a small thing, but I really love how Atom highlights the files that have changed in the tree view out of the box. Haven't figured out how to do that in Atom...

In Atom or in Atom?

Re: Sublime Text 3 marked as recommended build

#50

Post by tomsmeding » Tue, May 31, 2016, 6:52 AM UTC

spoiler wrote: post #45

gedy wrote: post #35

Earlier quoted context omitted.

Atom does not handle large files well at all compared to ST. I like Atom, but get very serious hangs with it on large files.

How large are you talking? I had similar issues early on with Atom, but I don't have them anymore (same project). Also, it would only hang for about a second when initially opening the file, later on it would work smoothly.

Many-megabyte, probably; think an assembly dump of your browser, for instance.