4 ms·

I've used ST in the past, but due to slow release cycle, I switched to Vim. What really bugs me in ST is the fact that the guy doesn't have time to work, but st

I've used ST in the past, but due to slow release cycle, I switched to Vim. What really bugs me in ST is the fact that the guy doesn't have time to work, but still, it's not open source for the community to work together to achieve a decent release cycle.

yAnonymous 12y ago
ST in its current form is better than most other editors, so why would it need a faster release cycle?
- Kaligule 12y ago
  The Plugin System could do with some polish, for example. Whenever one of my plugins broke it was a complete mess to remove the bad file.
  - wbond 12y ago
    Are you using Windows? That sounds like a Windows filesystem locking issue. It is a constant pain in my side and the source of lots of extra code in Package Control.
dmacvicar 12y ago
This. It is not that the editor is in bad shape. The periods of of inactivity made me feel like the editor could be abandoned or discontinued. I went back to Emacs.
- avinassh 12y ago
  How inactivity affected it's performace? It was same. Did you started encountering many bugs? Or badly looking for some feature?
tragic 12y ago
It seems to me that ST would really benefit from being open-sourced, but I guess it depends on how much cash he's getting out of it, and whether he can afford to give that up. I stick with ST because the plugin ecosystem is vibrant, it's hackable in a language I'd actually want to write, there's as much time-saving juice as Vim without me having to learn non-standard keyboard commands for the very basics (sorry, I like my arrow keys and Ctrl+x/c/v, and - god help me - my mouse), and it's not a sluggish, half-complete rip off of itself (cough Atom). I know enough Vim to get around a log or config file, but for serious work, Sublime and my brain are partners for life. (Unless Atom improves dramatically, anyway.) I don't suffer from the slow development cycle, but I'm sure others do, depending on what it is they need.
- toxican 12y ago
  Yeah it's great for me because the development cycle doesn't really faze me. I'm not really itching for anything new or for any bugs to be fixed. And if I do itch for something new, odds are there's a plugin for it.
- integraton 12y ago
  You can use arrow keys, Ctrl/Cmd+x/c/v, and your mouse in gvim and macvim just like any other editor.
reubenmorais 12y ago
> due to slow release cycle, I switched to I've read this argument multiple times and I just don't get it. Is it because you were waiting for a feature that hasn't been implemented? What's a decent release cycle? How does a indecent release cycle affect your daily usage of the text editor?
- redacted 12y ago
  My thinking is that some editors tend to be fashionable. I don't mean that negatively, just that their mindshare is transient until proven otherwise. They have a subset of users that are not massively invested in the platform, and will move to something that looks more interesting or more secure/active/etc. If that subset is large enough such a migration can harm the ecosystem: less users, less developer mindshare in bugfixing or plugin development and so on. It can then work like a run on the banks where people get out before the problem gets worse, making the problem worse. Interestingly, vim is often one of those editors: when TextMate was originally dying (pre open-sourcing) there seemed to be a new "why I'm switching to vim" or "how to set up rails dev in vim" post every day. I'd wager that a lot of people moved to vim as a result, then bounced off again.
- tutuca 12y ago
  Because there are many annoying small bugs that prevent the editor from being completely useful.
  - coldtea 12y ago
    Like what? Haven't found any in the 2+ years I'm using it for Python, PHP, JS and Go.
jameshart 12y ago
Sublime Text last released on July 8 2013; Vim's last release was on August 10 2013. So.... I guess I can see your point? As for open sourcing it: if you have barely enough time to work on a codebase yourself, it seems unlikely that becoming the co-ordinator of an open source project is a reduction in the amount of effort you have to make. And poorly-run open source projects don't generally have a fast release cycle.
coldtea 12y ago
>I've used ST in the past, but due to slow release cycle, I switched to Vim. You do know that there can be like decades between major Vim releases, right?

yAnonymous 12y ago

ST in its current form is better than most other editors, so why would it need a faster release cycle?

Kaligule 12y ago
The Plugin System could do with some polish, for example. Whenever one of my plugins broke it was a complete mess to remove the bad file.
- wbond 12y ago
  Are you using Windows? That sounds like a Windows filesystem locking issue. It is a constant pain in my side and the source of lots of extra code in Package Control.

dmacvicar 12y ago

This. It is not that the editor is in bad shape. The periods of of inactivity made me feel like the editor could be abandoned or discontinued. I went back to Emacs.

avinassh 12y ago
How inactivity affected it's performace? It was same. Did you started encountering many bugs? Or badly looking for some feature?

tragic 12y ago

It seems to me that ST would really benefit from being open-sourced, but I guess it depends on how much cash he's getting out of it, and whether he can afford to give that up. I stick with ST because the plugin ecosystem is vibrant, it's hackable in a language I'd actually want to write, there's as much time-saving juice as Vim without me having to learn non-standard keyboard commands for the very basics (sorry, I like my arrow keys and Ctrl+x/c/v, and - god help me - my mouse), and it's not a sluggish, half-complete rip off of itself (cough Atom). I know enough Vim to get around a log or config file, but for serious work, Sublime and my brain are partners for life. (Unless Atom improves dramatically, anyway.) I don't suffer from the slow development cycle, but I'm sure others do, depending on what it is they need.

toxican 12y ago
Yeah it's great for me because the development cycle doesn't really faze me. I'm not really itching for anything new or for any bugs to be fixed. And if I do itch for something new, odds are there's a plugin for it.
integraton 12y ago
You can use arrow keys, Ctrl/Cmd+x/c/v, and your mouse in gvim and macvim just like any other editor.

reubenmorais 12y ago

> due to slow release cycle, I switched to I've read this argument multiple times and I just don't get it. Is it because you were waiting for a feature that hasn't been implemented? What's a decent release cycle? How does a indecent release cycle affect your daily usage of the text editor?

redacted 12y ago
My thinking is that some editors tend to be fashionable. I don't mean that negatively, just that their mindshare is transient until proven otherwise. They have a subset of users that are not massively invested in the platform, and will move to something that looks more interesting or more secure/active/etc. If that subset is large enough such a migration can harm the ecosystem: less users, less developer mindshare in bugfixing or plugin development and so on. It can then work like a run on the banks where people get out before the problem gets worse, making the problem worse. Interestingly, vim is often one of those editors: when TextMate was originally dying (pre open-sourcing) there seemed to be a new "why I'm switching to vim" or "how to set up rails dev in vim" post every day. I'd wager that a lot of people moved to vim as a result, then bounced off again.
tutuca 12y ago
Because there are many annoying small bugs that prevent the editor from being completely useful.
- coldtea 12y ago
  Like what? Haven't found any in the 2+ years I'm using it for Python, PHP, JS and Go.

jameshart 12y ago

Sublime Text last released on July 8 2013; Vim's last release was on August 10 2013. So.... I guess I can see your point? As for open sourcing it: if you have barely enough time to work on a codebase yourself, it seems unlikely that becoming the co-ordinator of an open source project is a reduction in the amount of effort you have to make. And poorly-run open source projects don't generally have a fast release cycle.

coldtea 12y ago

>I've used ST in the past, but due to slow release cycle, I switched to Vim. You do know that there can be like decades between major Vim releases, right?