Earlier quoted context omitted.
> In this day and age, I think 4 months is pretty long, yeah. 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.
>>Most commercial desktop software, and even web services like Gmail, go on for years on end without an update. Yes, and I'm saying that's too long. I don't like waiting months or years for fixes or new features. I also stated that this is my personal opinion. Not sure why people are downvoting.
Sublime Text 3 dev build 3128 released
221–230 of 241 posts
Re: Sublime Text 3 dev build 3128 released
#222Earlier quoted context omitted.
> In this day and age, I think 4 months is pretty long, yeah. 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.
>>Most commercial desktop software, and even web services like Gmail, go on for years on end without an update. Yes, and I'm saying that's too long. I don't like waiting months or years for fixes or new features. I also stated that this is my personal opinion. Not sure why people are downvoting.
Sublime seems to have a well-defined aim and to be resistant to feature creep. It's doing a good job of meeting that aim, so I'm happy with it only changing as needed to keep up with like, high DPI monitor support or other things that would actually make it unusable.
Re: Sublime Text 3 dev build 3128 released
#22370$ is nothing for a good tool.
... and then some people wonder why a company can not afford to make marketing etc ...
Re: Sublime Text 3 dev build 3128 released
#224Excited to hear news from Sublime team! I tried the new beta: it kinda breaks fonts in old themes (I use spacegray) but the new Adaptive theme looks pretty (I wish I could reduce tab bar height, though). Also enjoyed switching UI and syntax themes via palette. Overall looks great but for now I'll stick to ST3 stable release. My #1 feature request is Sidebar API, you know, for version control integration.
To clarify, this is not a beta, this is a dev build. The Beta channel is 3126, which has been a rock for me (paid user).
Re: Sublime Text 3 dev build 3128 released
#225Earlier quoted context omitted.
I've been very active on the forum, Discord, IRC and the Packages repo on GitHub. I don't think the stereotype of Sublime HQ being radio silent holds true any longer. We don't, however, make blog posts or tweets saying "we're still working on the next build." However, whenever anyone asks on the forum (twitter, etc) I'll be happy to tell you we are still working on the next build! :-)
Thanks for the reply! I'm sure you're right about the stereotype not holding true, I haven't really been following things closely. I also understand that time spent convincing people all over the internet that you're still working on the next build may be better spent... well, working on the next build :)! What I had in mind was more along the lines of "what's happening to Sublime Text in the long term", though that…
Re: Sublime Text 3 dev build 3128 released
#226The creator of Sublime Text tends to go silent for long periods between stretches of activity, which always makes me wonder about the future of the project. It's a shame, since ST is a well-thought-out editor with great attention to detail, and of course the speed argument (compared to Atom and VS Code), while beaten to death, still holds true. Of course, it's up to the author himself to choose how he communicates, m…
That is exactly the reason why I haven't bought a license yet. I consider the license an investment in Sublime's future. Since I don't have to pay, buying a license is more of a donation in order to show support. But the communication seems a bit too sparse/erratic for me to have much trust in this project. The time spans between updates, blog posts, or even tweets are simply way too long. I also consider the existen…
There's an official docs site as well now that's actually pretty good. I haven't referenced the unofficial docs in some time.
Re: Sublime Text 3 dev build 3128 released
#227Earlier quoted context omitted.
That is exactly the reason why I haven't bought a license yet. I consider the license an investment in Sublime's future. Since I don't have to pay, buying a license is more of a donation in order to show support. But the communication seems a bit too sparse/erratic for me to have much trust in this project. The time spans between updates, blog posts, or even tweets are simply way too long. I also consider the existen…
> I consider the license an investment in Sublime's future. I'm exactly the opposite. I consider the license as compensation for work already done, I operate under the assumption that the vendor will have made enough to not care to work on it further.
Also packages are well separated from the Sublime releases so even in the case that there isn't another update, the ecosystem is still active. That said, I do wish the internal Python for plugins would receive a version bump though.
Re: Sublime Text 3 dev build 3128 released
#228Earlier quoted context omitted.
I actually switched to VS Code vs Sublime for most tasks just recently. It has a few quirks (looking at you, files that just close for no reason) and isn't quite as quick, but the language/debugging packages and support are just leagues better.
> ... files that just close for no reason) Do you mean if you select (preview) a file from the tree browser on the left, the file appears, but if you select another one, it goes away ? Use this setting/preferrence: "workbench.editor.enablePreviewFromQuickOpen": false,
Re: Sublime Text 3 dev build 3128 released
#229Earlier quoted context omitted.
> files that just close for no reason I never experienced this, which type of files ?
I actually looked into it a bit more. This may have been the fault of the default "workbench.editor.enablePreviewFromQuickOpen": true, as quick open is literally the only file opening mechanism I use (I assume, if that's cmd+p). Weird default. I turned it to false, maybe that will fix the closing-files issue. Now if only I can get it to stop automatically closing quotes during comments and ruining my english contract…
Re: Sublime Text 3 dev build 3128 released
#230I love Sublime Text. I really dislike heavy IDEs, so for me, it's almost the perfect editor. But... am I the only person who wants a minimal editor like Sublime, plus an inline debugger? Debugging where you edit code is one of those super-features that I really don't understand why people prefer not to have it. Ideally it would be something generic and lightweight, with the ability to extend via plugins. The debuggin…