Live data from Hacker News

Sublime Text 3 Beta

sublimetext.com

101–110 of 374 posts

Re: Sublime Text 3 Beta

#102

> OSX: 10.7 or later is required Looks like I might have to bite the upgrade bullet this year.

I feel you man. I've been stubbornly sticking to Snow Leopard myself, it works great with my late 2008 MBP.

The initial version of ML was terrible on my 2008 MBP but they made performance enhancements and now 10.8.2 works fine. Spending $50 for gb/RAM didn't hurt of course (best investment of my life btw).

Re: Sublime Text 3 Beta

#103
post #57

I am disappointed to see that Vintage mode hasn't really been touched at all for this edition. It's what is holding myself (and likely others) back from switching away from Vim. Unfortunately, development of Vintage mode seems to have stopped (the repository hasn't changed for about six months).

What's noticeably missing from Vintage for you?

I'm also Vim user who has considered jumping to Sublime several times, but never quite managed to achieve escape velocity. (Though I hadn't realised until now that the Vintage package is an open repository)

Re: Sublime Text 3 Beta

#104
post #101

THE SO-CALLED “VISUAL” EDITORS HAVE BEEN PLACED HERE BY ED TO TEMPT THE FAITHLESS. DO NOT GIVE IN!!! THE MIGHTY ED HAS SPOKEN!!! http://www.gnu.org/fun/jokes/ed-msg.html

Sheesh okay I'm sorry! I thought it was funny, never do it again, etc...

Re: Sublime Text 3 Beta

#106
post #55

Earlier quoted context omitted.

So that people feel less screwed about the fact that they are paying for the same product repeatedly.

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?

Re: Sublime Text 3 Beta

#107
And still no option to print? I've been a happy ST2 licensee for quite some time, and the inability to print is probably my biggest complaint (though, admittedly, I don't need to print things very often).

Re: Sublime Text 3 Beta

#108
post #100

Earlier quoted context omitted.

I am certainly concerned that they might give it the official arse. The only thing that gives me hope is that the Pro fits a small but important niche in the overall ecosystem: a system better suited for the developers of iOS applications than the iMac is.

What does the Mac Pro offer for iOS developers that the iMac does not?

More. Of everything.

More cores, more RAM, more GPU grunt to drive more screens.

Re: Sublime Text 3 Beta

#109
post #75

Earlier quoted context omitted.

he will go back to it soon, I think

That's great news - do you have a source (maybe a forum post) for that?

not really, but the man spent all his time on S3 development, I think it's the reason that we haven't seen any progress in vintage mode. With S3 beta released, I guess he doesn't need to stick to it every second any more.

Re: Sublime Text 3 Beta

#110
post #97
post #57

I am disappointed to see that Vintage mode hasn't really been touched at all for this edition. It's what is holding myself (and likely others) back from switching away from Vim. Unfortunately, development of Vintage mode seems to have stopped (the repository hasn't changed for about six months).

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.

Post reply on HN