Earlier quoted context omitted.
That's true. Sublime 3 never felt like "beta" software. But as somebody said below, I am afraid of people quitting and leaving it to die slowly (like TextMate died) and that's the reason why I was hesitate to buy it for so long. Nobody guarantees if the developers drop the ball for some hypothetic reason thing will go open source, even that is not guaranteeing anything (again TextMate's case).
If you like it, and you're afraid that it will be abandoned then don't hesitate to pay. I'm sure money is an incentive to keep working on it. I paid for S2 and S3 and I'm happy to have done so.
Sublime Text 3 dev build 3128 released
111–120 of 241 posts
Re: Sublime Text 3 dev build 3128 released
#112Re: Sublime Text 3 dev build 3128 released
#113Re: Sublime Text 3 dev build 3128 released
#114Earlier quoted context omitted.
Well price-vs-feature ratio is debatable. The thing is that VSC has many IDE-like features, that I don't want in text editor. So everything comes down to a personal preference. And I don't know if somebody will finance piece of software for you, I mean they can, again depending on situation, but I don't turn off the possibility of me personally paying for piece of software that I like.
How so? VSC is approaching 1:1 feature parity with ST at a $70 price reduction. Some features you need extensions for in ST are included with VSC OOTB.
Speed is a major feature.
And battery/memory efficiency is too.
And, on principle, I'd pay to NOT have to use an Electron app.
That said, I've used VSCode from time to time.
Re: Sublime Text 3 dev build 3128 released
#115Windows font rendering defaults to DirectWrite unless using Consolas or Courier New Anyone knows what this means in practice? What rendering is used instead and does this mean Consolas/Courier have a disadvantage or an advantage?
Re: Sublime Text 3 dev build 3128 released
#116Earlier quoted context omitted.
4 months is a "long time" nowadays?
In this day and age, I think 4 months is pretty long, yeah. But that's just my personal opinion. I think Chrome and Firefox has the right idea, with updates every 6 weeks.
Most commercial desktop software, and even web services like Gmail, go on for years on end without an update.
Browsers are always adding crap (like Firefox's nth cosmetic update), they should be stabler too. Once every 6 months or so at worst.
Re: Sublime Text 3 dev build 3128 released
#117If Sublime only had definite release! It's wonderful GUI editor! I stopped using it years ago when I switched to Vim and Emacs, but if it gets released I will buy it for sure, at least to have it on my work machine. I like editing text in it, everything is so smooth and well looking, and it doesn't feel bloated. And I just hate all those Electron based editors, no matter how much incrementally they get better from mo…
On the contrary, I still miss the speed of ST but the price-vs-feature ratio on VSC is too high for me to ignore anymore. No way the boss will shell out $70 per license if/when ST3 is ever released (now that half our team has dropped it anyway). Guess what you said about not relying on "public opinion" includes your own.
Re: Sublime Text 3 dev build 3128 released
#118Re: Sublime Text 3 dev build 3128 released
#119Re: Sublime Text 3 dev build 3128 released
#120Earlier quoted context omitted.
Well price-vs-feature ratio is debatable. The thing is that VSC has many IDE-like features, that I don't want in text editor. So everything comes down to a personal preference. And I don't know if somebody will finance piece of software for you, I mean they can, again depending on situation, but I don't turn off the possibility of me personally paying for piece of software that I like.
How so? VSC is approaching 1:1 feature parity with ST at a $70 price reduction. Some features you need extensions for in ST are included with VSC OOTB.
I don't want Sublime to be IDE, I have programable environment called Emacs for that. Integrating everything into editor is cool, to the point where you ask yourself "why am I doing all this?" and erase everything and just start writing code, not code for the editor. Again, this is my _personal_ experience, so take everything with grain of salt. I know your case is different, but I think you can see the reasoning behind my words.