41–50 of 106 posts
It's great. SB3 beta has been completely stable for me the past year, so looking forward to testing the new builds.
The plugin system dies for me regularly. I wish I didn't have to quit ST3 to fix that.
I don't really see much point in Sublime Text now that GitHub's Atom is a pretty much a one->one replica but free, open-source and has a rather nice package manager for plugins.
Earlier quoted context omitted.
I tried Atom for a week. The little half-second delays start to bite after a few days, and after a week you want to throw your computer out the window. Think about it. It's 2015. My PC has 8 cores running at unimaginable speeds. It has 16 GB of memory. And my text editor couldn't open files over 2097152 bytes. Am I living on a different planet from everyone else? How can people accept this as a normal situation?
I agree completely with this. In my job, I need to open up a lot of CSV files ranging from several MB to hundreds. Sublime Text, whilst not perfect is far better than anything else out there. It doesn't struggle with these files either.
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.
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.
Earlier quoted context omitted.
I agree completely with this. In my job, I need to open up a lot of CSV files ranging from several MB to hundreds. Sublime Text, whilst not perfect is far better than anything else out there. It doesn't struggle with these files either.
vim would open multi-hundred megabyte files in seconds, if only you can invest in learning its modal editing mechanism (which, to be fair, is fairly arcane, and is proven to be a worse UI than free form editing).
Earlier quoted context omitted.
I don't really like Atom because of the webkit usage, but I strongly agree that using a closed source text editor is a terrible idea for a programmer... when that editor stops being maintained all the time investment learning all it's time saving tricks is lost. Luckily I've been burned really early in my programming career by TextMate to know better: all my tools must be OSS and cross-platform.
I don't understand this line of thinking. For me a closed-source text editor such as Sublime Text makes me much more productive than it's open-source equivelent. The accumulated productivity gains far outweigh the timecost to learn a new tool, if Sublime Text disappeared (a couple of days at most?).
OTOH I will be able to use vim (or a fork of it) 20-30 years from now and become more and more productive with it during the timeframe.
I don't really see much point in Sublime Text now that GitHub's Atom is a pretty much a one->one replica but free, open-source and has a rather nice package manager for plugins.
Atom ist not free as in freedom, just free as in beer.
Earlier quoted context omitted.
> I've never heard why it's too slow. Because it uses Webkit and Javascript rather than being implemented natively.
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 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 orders of magnitude.
While I'm not bothered by Atom being slowish, I think there is some basis for dissatisfaction here. Of course, nobody is obligated to use Atom.
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.
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?
Earlier quoted context omitted.
The plugin system dies for me regularly. I wish I didn't have to quit ST3 to fix that.
That sounds like a bum package, or a corrupted install. If you are using Package Control you can copy the Packages/User/ folder to a fresh install and install Package Control to try fixing it. PC will do a fresh reinstall of missing packages.