Is sublimetext as hackable(extensible) as emacs or atom?
Atom? Maybe. Emacs? Nope.
Sublime Text 3 marked as recommended build
31–40 of 135 posts
Re: Sublime Text 3 marked as recommended build
#32Re: Sublime Text 3 marked as recommended build
#33I 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).
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…
That's really the only/main thing I miss.
Re: Sublime Text 3 marked as recommended build
#34I 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).
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…
It would greatly suprise me if either Atom of VSCode shut up tomorrow. They couldn't entirely shut up, as they are both entirely open source projects.
The Sublime Text website could just close tomorrow if one person got badly hurt / lost interest, and then the executable could not work on Mac OS X 10.11.6 for some reason, and it is done.
I've had too many pieces of software go that way to get another one which is so fundamentally important to me (text editor).
Re: Sublime Text 3 marked as recommended build
#35I 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).
Re: Sublime Text 3 marked as recommended build
#36I 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).
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 love Sublime but there is also a https://en.wikipedia.org/wiki/Bus_factor
Also if you have tried Atom at some point, try it again, they made it much better and faster. Only thing I miss is how incredibly fast Sublime Text is.
Re: Sublime Text 3 marked as recommended build
#37Re: Sublime Text 3 marked as recommended build
#38No, still beta "Sublime Text 3 is currently in beta. The latest build is 3114."
Just searched for the word "beta" in home page and got 0 results... where does the quoted sentence come from?
Re: Sublime Text 3 marked as recommended build
#39I 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).
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…
That plugins are written in javascript (larger developer base) and allows more customization of Atom (more open plugin api) also yields more niche plugins.