61–70 of 106 posts
As someone who finally shelled out the money for it and a few paid plugins, I'm really glad to hear this!
I know that in the past the builds have been fast and furious, but, honestly, I don't see any reason to have a new build more than every couple of months. More than that and it wastes my time; I suspect the ST developer has learned that more frequent builds waste his time as well.
Sublime Text is fast, powerful, intuitive, and--the killer feature for me--cross-platform. It's well worth the money to me now, regardless of its long-term future (in the long run, we're all dead). While development has been sporadic, at least it seems like the developer has not succumbed to the Moby Dick/Second System effect, so that's a plus. It would be great in the long run (i.e., when the developer tires of full-time work) if it were open source, but it's nigh-impossible to support oneself with open source applications, so it seems healthier now for it to be a proprietary app.
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.
> 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?
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.
Too late for me. Atom replaces sublime in my workflow.
Too late for me. Atom replaces sublime in my workflow.
Just tried opening a file larger than 2MB....nope. End of Atom tryout.
(I'm kidding, I understand the slowness is due to the webkit rendering...)
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.
> 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?
I'm a co-owner of a small software business, so in a very similar situation to the Sublime Text developer (with the exception that my product is much less successful). I went and looked at the linked-to list of builds. There's a bit of a gap from December 2013 to May 2014. But then there's a release every couple of months. I know that in the past the builds have been fast and furious, but, honestly, I don't see any r…
I am totally fine if he does not release something new for half a year, but at least he could've written a short blog post that he will take some time off. Even a short "Hey guys, I am still working on it but things are very slow right now" every 8 weeks would've been totally fine.
Earlier quoted context omitted.
I didn't mean technical reasons but what works slowly. Like: I enter a key and the letter shows up with perceivable delay (which in my experience, even with 100.000 lines isn't the case). One thing I found extremely slow for instance was copy and pasting of large chunks of text, but that's something I only experienced while testing Atom's performance. For my common text manipulation, I've never experienced the slowne…
- Text editors have been around for a very long time. - Text editors are not that complex (even with plugin systems they are not doing HPC work). - Text editors were not perceived as slow many years ago. - Our computers have only got faster (10000x range). - It is 2015 and a text editor is slow (sub-second delays in GUI, large file limits, etc). - There are text editors not written in JS/Webkit that are not slow by o…
I've been a long time ST user, but when I out of curiosity started playing with Vim and slowly get used to it, I now prefer it over ST most of the time. But I'm glad that Sublime Text is alive again.