Live data from Hacker News

Vico Editor (Mac text editor)

vicoapp.com

21–30 of 141 posts

Re: Vico Editor (Mac text editor)

#21
Am I the only person who thinks that tabs don't scale in editors used for programming? I tend to have a lot of files opened at the same time (currently at 143 in Emacs) and I can quickly switch to any of these with a couple of keystrokes. Most of the Textmate users I've seen don't even care about the tabs in the editor, they just press Cmd-T and type the name of the file.

Is people doing something else with tabs that I'm missing here?

Re: Vico Editor (Mac text editor)

#22

If Textmate 2 isn't released soon it may be in trouble. This looks awesome.

TextMate 2's troubles aren't competitors, but rather that the author is apparently out there thrashing in the weeds. If it does get reeled in and actually released, I bet it will be good enough to consider.

Re: Vico Editor (Mac text editor)

#23

Am I the only person who thinks that tabs don't scale in editors used for programming? I tend to have a lot of files opened at the same time (currently at 143 in Emacs) and I can quickly switch to any of these with a couple of keystrokes. Most of the Textmate users I've seen don't even care about the tabs in the editor, they just press Cmd-T and type the name of the file. Is people doing something else with tabs that…

Tabs are nice if you are programming just a couple files, or several files from different locations. Any more than that, and I agree that they're far too unwieldy. Vico also has an open files dropdown, and, of course, a folder explorer, as well as Cmd-T.

Re: Vico Editor (Mac text editor)

#25

Am I the only person who thinks that tabs don't scale in editors used for programming? I tend to have a lot of files opened at the same time (currently at 143 in Emacs) and I can quickly switch to any of these with a couple of keystrokes. Most of the Textmate users I've seen don't even care about the tabs in the editor, they just press Cmd-T and type the name of the file. Is people doing something else with tabs that…

Why do you have 143 files open at the same time?

Personally I use some (2-7?) buffers in vim and cycle through them. When I don't anticipate editing a file for a while I close that buffer.

Re: Vico Editor (Mac text editor)

#26
post #19
post #14

Earlier quoted context omitted.

Yes, but what happens when development on this closed source editor dries up? It looks like a great app, but I'm still leery of basing something as important as my editor on a closed code base again. There are also some great alternatives out there, notably Redcar, which is both open and full of Textmate like features.

If you are capable of switching editors, what does it matter if it's closed source or not? This adversity to switching editors is a common trait in programmers I can't quite understand. We programmers learn new things all the time, it's part of what makes us excel in our profession. And yet, adopting a new editor is apparently extremely hard.

Yes, but I'm extremely lazy :) The less time I spend learning a new editor is more time I can spend learning a new technology.

Re: Vico Editor (Mac text editor)

#27
post #25

Am I the only person who thinks that tabs don't scale in editors used for programming? I tend to have a lot of files opened at the same time (currently at 143 in Emacs) and I can quickly switch to any of these with a couple of keystrokes. Most of the Textmate users I've seen don't even care about the tabs in the editor, they just press Cmd-T and type the name of the file. Is people doing something else with tabs that…

Why do you have 143 files open at the same time? Personally I use some (2-7?) buffers in vim and cycle through them. When I don't anticipate editing a file for a while I close that buffer.

My editor has been opened for 2-3 weeks now so I just keep piling the files from all the different projects. I prefer typing 'C-x b [strat]' to opening '~/dev/projects/something_else/lib/strategy.rb' but it might just be the way I'm used to working.

Re: Vico Editor (Mac text editor)

#28
post #20
post #3

This could be very good, I am still trying to find my perfect editor Vim's learning curve & interface means occasionally I just open up sublimeText2/TextMate. Great to see split views are there from the start.

I don't want to take anything away from Vico (because so far it is pretty rad), but if you stick with MacVim you eventually start using TextMate less and less until you just stop altogether. For me, it took a good 3 months or so. The last holdout was using TextMate for formatting JSON output, but I found a Chrome plugin for that.

I love MacVim too, and have dropped Textmate completely. The only thing that I don't like about MacVim is that scrolling through text (vertically and especially horizontally) feels choppy compared to Textmate. When I see someone else scrolling through code in Textmate, it looks unbelievably smooth and fluid compared to what I'm used to in MacVim.

Re: Vico Editor (Mac text editor)

#29
post #20
post #3

This could be very good, I am still trying to find my perfect editor Vim's learning curve & interface means occasionally I just open up sublimeText2/TextMate. Great to see split views are there from the start.

I don't want to take anything away from Vico (because so far it is pretty rad), but if you stick with MacVim you eventually start using TextMate less and less until you just stop altogether. For me, it took a good 3 months or so. The last holdout was using TextMate for formatting JSON output, but I found a Chrome plugin for that.

your right and I have seen my percentage time on vim get higher an higher over the months, but thats from persistance. Its slow progress because I mainly work in eclipse and the vim plugins aren't 100% great for me.

Vim is just hard work getting going, e.g. in HTML I like to have the closing tag automatically done for me which im sure vim can do but i've just not had chance to look into. There are 100 other small things like this which I solve one at a time but often I just go 'cock it' and open it up in another editor. But then I want to split the window and open vim again....

Re: Vico Editor (Mac text editor)

#30
post #19
post #14

Earlier quoted context omitted.

Yes, but what happens when development on this closed source editor dries up? It looks like a great app, but I'm still leery of basing something as important as my editor on a closed code base again. There are also some great alternatives out there, notably Redcar, which is both open and full of Textmate like features.

If you are capable of switching editors, what does it matter if it's closed source or not? This adversity to switching editors is a common trait in programmers I can't quite understand. We programmers learn new things all the time, it's part of what makes us excel in our profession. And yet, adopting a new editor is apparently extremely hard.

Perhaps it feels extremely hard because a preferred programming environment is so deeply tied to muscle memory via key bindings (which, admittedly, Vico is trying to address for vi users), whereas learning other new things engages other more flexible parts of the brain.
Post reply on HN