Live data from Hacker News

Sublime Text 3 dev build 3128 released

sublimetext.com

151–160 of 241 posts

Re: Sublime Text 3 dev build 3128 released

#151
post #6

The 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 existence of http://docs.sublimetext.info a bad sign. The way I perceive this: At some point, an enthusiastic user was so fed up with the sub-par documentation that they decided to take matters into their own hands, and create a better documentation. But instead of working with the community, the Sublime project people/person just... did nothing? Was there any communication? I don't know. Why not provide the documentation on github and accept PRs? The Sublime project should push for docs.sublimetext.info to be merged into the official documentation.

Same with https://github.com/SublimeTextIssues/Core/issues. Why is the bug tracker "community run"? What does that even mean, considering the "community" can't fix any bugs? I absolutely cannot understand why the author of the software doesn't seem to participate at all in the bug tracker. Here's a quote from https://github.com/SublimeTextIssues/Core/issues/594 (from 2014, so I don't know whether it is still true) > Unfortunately, the only thing I can say is it'll get fixed if Jon Skinner sees it as a big enough priority. Our intent in creating this unofficial Issues page was to have a curated place where known issues can be collected together and triaged, and he can use it as he sees fit to fix bugs in upcoming releases. Without a more direct feedback mechanism, this is the best we can do, at the moment.

What I'd also like to see is a road map for the future with regular (2-4 weeks) status updates.

Re: Sublime Text 3 dev build 3128 released

#152

Earlier 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 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 contractions:

// it' => // it''

Any way around that? :(

Re: Sublime Text 3 dev build 3128 released

#153
post #53

Earlier quoted context omitted.

It's not that we don't want to pay for software, and I don't think that's what OP meant when he used the word "nonfree". It's just that we need the four freedoms in case the software takes a sudden turn in a direction we don't like. Now you're going to ask: How is it possible to support the four freedoms and still charge for the software? And my answer is: I have no idea, and I don't care. It's not my job to come up…

I see. Perhaps I commented too fast. I don't think it's that big of a deal for a text editor, though. One thing is if you're a designer and all your files are PSDs and you're locked in with Photoshop, but if Sublime Text dies you still have lots of other editors that will open your plain text files: Atom, Eclipse, etc.

Once you have trained your muscle memory on a given editor, switching becomes a very big deal.

Re: Sublime Text 3 dev build 3128 released

#155
post #92

For vim users, there's also the ActualVim[1] plugin, which uses neovim's headless mode for processing. I've always been somewhat disappointed by vintage mode / vintageous in ST, and while ActualVim still has some issues, it's definitely promising. (It even works on Windows now! Though I couldn't quite get my plugins running yet) [1]: https://github.com/lunixbochs/ActualVim

Shameless advertising: since the developer of Vintageous stopped maintaining it, @gerardroche and I have started a fork that we will review PRs for and occasionally work on. We've already merged a bunch of outstanding PRs, added some new features and fixed some bugs. https://github.com/NeoVintageous/NeoVintageous

Awesome! Vintageous is nice, but there are outstanding bugs that are annoying and it has had that "it doesn't matter if you write a nice PR I'm going to ignore it" feel about it for some time.

Re: Sublime Text 3 dev build 3128 released

#156

Earlier quoted context omitted.

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.

> 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.

Are you sure Gmail isn't updated often? I feel that they do update it regularly but they don't feel the need to advertise anymore.

Re: Sublime Text 3 dev build 3128 released

#157
post #3

I'm just hoping that ST3 will be marked as final soon, so that Skinner may collect the upgrade fees before VSC has completed its take over of the world (of free editors). As a long time fan, I do get - and admire - the perfectionism, but hopefully there's room for dot releases after the 3.0 final.

I'm really curious why it hasn't been labelled final yet. Do we know what the dev(s) is/are waiting on?

Re: Sublime Text 3 dev build 3128 released

#158
post #151
post #6

The 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…

> The time spans between updates, blog posts, or even tweets are simply way too long.

Is there a lot that you think ST still needs? As long as bugs are fixed, I'm happy with the functionality of the software today. The software feels done to me.

Re: Sublime Text 3 dev build 3128 released

#159

I 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…

> if I can't click on a line number

If clicking isn't a hard requirement, I think there is something to be said for command line debuggers with well done interfaces.

I spend a lot of my time in Python at the moment which doesn't usually require a debugger because of its restricted control flow, but every so often I find myself in need and I always gravitate to PUDB (http://heather.cs.ucdavis.edu/~matloff/pudb.html). And I haven't found it wanting -- yet.

Re: Sublime Text 3 dev build 3128 released

#160

Earlier quoted context omitted.

I feel the issue isn't the $70 which isn't a big deal (or shouldn't be) but more the point that other editors like VSCode are available now and have the backing of a big company like Microsoft. The biggest criticism of Sublime is that it often feels like it has been abandoned. It goes 6+ months without a peep from the developer. This can make people uneasy. I prefer Sublime over VSCode, Atom, etc. but at the end of t…

It goes 6+ months without a peep from the developer. There was a time when that was the case, but for quite a while now we've been seeing frequent releases.

The last update before the one today was in September 2016.
Post reply on HN