Live data from Hacker News

Sublime Text 3 Beta

sublimetext.com

141–150 of 374 posts

Re: Sublime Text 3 Beta

#141

Earlier quoted context omitted.

I bought it when Sublime Text 2 came out of Beta, which wasn't all that long ago, was it? As somebody that very rarely buys tools, it's hard not to feel a little incensed.

It's $30. What sort of development are you doing that isn't worth $30 for the single tool that allows you to do it? I can't imagine carpenters are incensed when Ryobi brings out a new $300 drill. You either buy the new drill, or you keep the old one. Nobody expects new hardware for free, why software?

If you have an old drill and buy a new one, you own an old drill and a new drill. If you have old software and update it, you only have the new software.

In the first case, the value of your goods and of their use to you is more than just one drill.

In the second case, you end up paying more than the price of the newest software, for just the newest software.

From this, one could make the argument that the most fair upgrade price would be $11 - the difference between the old and new software.

Re: Sublime Text 3 Beta

#142
post #97

Earlier quoted context omitted.

As someone who only used IDE debuggers all his (short) programming career, I was wondering, how do you debug without a visual debugger? I've seen how GDB works, and debugging this way seems much less productive. You don't see your whole source code, and you don't constantly see the values of watched or local variables, etc... Is there a different debugger you use for this task when developing using only a text editor…

> As someone who only used IDE debuggers all his (short) programming career, I was wondering, how do you debug without a visual debugger? I'd ask the reverse of you. Why do you spend time in a debugger at all? For 99% of the bugs logical thinking and a few printfs work faster and better ran blindly running around setting breakpoints and examining values.

Hmm ... a few cases i could think of.

Memory stomp bugs. Race conditions.

And some Entrprise OO problems - inspecting 260 layer stacktrace and exploring very complicated structures.

Re: Sublime Text 3 Beta

#143

I tried using Sublime text and it's a great editor, extensible and moldable, but I just keep coming back to emacs since that is always available wherever I am, logged in via ssh. A ssh/text-only version of sublime text would be interesting ;)

> A ssh/text-only version of sublime text would be interesting ;) That's "vi". All kidding aside, I've no idea how someone would pull this off. A lot of the best features in Sublime wouldn't translate well to a terminal. The minimap, for example.

One could perhaps do something with opening two terminal windows that connect to the same ST session, but put the font size of one of them to tiny.

Re: Sublime Text 3 Beta

#144
"Sublime Text has always had speed as a feature, but version 3 addresses some weak points. Startup time is now virtually immediate, and plugins no longer have the opportunity to bring this down. Replace All performance is also significantly faster"

couldn't care less about startup time while the speed problem on windows lies in loading/editing files greater than a couple of mb. I start ST only once a day but I load files like a hundred times and I'm not the only one with that workflow :] so to me the last one seems like a higher priority?

Re: Sublime Text 3 Beta

#145
post #97

Earlier quoted context omitted.

As someone who only used IDE debuggers all his (short) programming career, I was wondering, how do you debug without a visual debugger? I've seen how GDB works, and debugging this way seems much less productive. You don't see your whole source code, and you don't constantly see the values of watched or local variables, etc... Is there a different debugger you use for this task when developing using only a text editor…

> As someone who only used IDE debuggers all his (short) programming career, I was wondering, how do you debug without a visual debugger? I'd ask the reverse of you. Why do you spend time in a debugger at all? For 99% of the bugs logical thinking and a few printfs work faster and better ran blindly running around setting breakpoints and examining values.

Debuggers are handy for the last 1% of bugs. And anyway there is nothing about debuggers that precludes logical thinking or requires "blindly" placing breakpoints.

Re: Sublime Text 3 Beta

#146
post #51

On a related note, check out the top 10 sublime text plugins: http://www.henriquebarroso.com/my-top-10sublime-2-plugins/ Some of my favorites are there! If you haven't done so, check it out too!

Yeah but this is Python 3, so not many will work with ST3.

Moving to 3 from 2 is a no-brainer most of the time. http://docs.python.org/dev/library/2to3.html

Re: Sublime Text 3 Beta

#147

Coming from someone who has never used or tried Sublime Text, how does this compare to Vim in general? It's taken quite a while to grow familiar with Vim, is it worth the learning curve to ditch it now and try Sublime? Are the two really that different? A lot of what I'm seeing looks like things that can be done in Vim, but I might be missing something.

You can use a vim emulation mode in sublime so all your hard work wasn't for nothing but I believe some of the more advanced vim features don't work in sublime. The advantage of sublime is that it works well out of the box and with package control it is very easy to install any package you may need. If you decide to give it a try, try sublime 2 with package control (I believe the trial is still free for sublime 2).

It's not just the advanced features. Even basic features are completely broken. Pressing undo several times can occasionally break out of undoing and start editing your document on your behalf - spewing a slew of "uuuuuu" into your document, which - guess what - ruins any hope you have of reverting back to the original document state.

Re: Sublime Text 3 Beta

#148
post #62

Are these changes really worth the "3.0" tag? Goto to symbol is great, but all other bullet points taste like what I expected 2 to have once it left beta (basically, speed and not letting plugins crash my session). Isn't this a clever way to make users buy into a paid upgrade for a stable version of an editor they already bought?

Even if it is, I am more than happy to put down another $30 for it. I get that much value from it daily.

Yep, my thoughts exactly. Sublime is one of the few pieces of software that I rely on that has not only never let me down (so far!), but has really pleasantly surprised me on several occasions, saving my ass when I thought I'd just lost a lot of work.

Re: Sublime Text 3 Beta

#149
I'm not near a computer at the moment, can any body tell me how the performance is with very large files (>20mb) compared to the previous releases?

If there was one thing that disappointed me about ST2 it was that it wasn't very competent with massive log files and the like. ATM I use an ide for Java, ST2 for nearly everything else (other languages, random text) and less / vi / others for logs and other massive files.

Would love to be able to kill off another tool.

Re: Sublime Text 3 Beta

#150
post #119
post #20

Is it just me or Package Control doesn't work on it?

Not yet. I started prepping for the port to Python 3 a bit ago at https://github.com/wbond/sublime_package_control/tree/split_... , but the actual Python 3 changes are still in progress and not pushed (for the sake of not spoiling Jon's surprise).

Has there been any talk about merging Package Control into the app out of the box for v3?

When I tell people how much I love ST2, Package Control is definitely responsible for some of that love.

Post reply on HN