Earlier quoted context omitted.
Personally, I tend to think that an overly dogmatic commitment to backwards compatibility does more harm than the benefit produced by supporting a tiny minority of users with five year old hardware. Backward compatibility is the enemy of elegance. Just look at C++ or the x86 instruction set to see examples of that.
I do agree to some extent. On the other hand, I've been using Apple hardware off-and-on again since the MC68030; I already went through this with the 68k->PPC transition, then again with the introduction of the PPC750 series processors, then again with the PPC->Intel transition. At this point, I fully expect that if I were to buy an Intel series Apple system in the next couple of years, shortly afterward Apple would…
Vico Editor (Mac text editor)
51–60 of 141 posts
Re: Vico Editor (Mac text editor)
#52Earlier quoted context omitted.
Personally, I tend to think that an overly dogmatic commitment to backwards compatibility does more harm than the benefit produced by supporting a tiny minority of users with five year old hardware. Backward compatibility is the enemy of elegance. Just look at C++ or the x86 instruction set to see examples of that.
I do agree to some extent. On the other hand, I've been using Apple hardware off-and-on again since the MC68030; I already went through this with the 68k->PPC transition, then again with the introduction of the PPC750 series processors, then again with the PPC->Intel transition. At this point, I fully expect that if I were to buy an Intel series Apple system in the next couple of years, shortly afterward Apple would…
Re: Vico Editor (Mac text editor)
#53Am 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…
1) Look at docs in one pane and code in another
2) Look at some combination of the model/view/controller triad at the same time
3) Look at a header file and the implementation file
4) Work on a rake (for example) task while seeing the code it will run
5) Look at two different spots in the same file
edit 6) work on a javascript file next to the HTML page it's used in
7) look at a class and its superclass at the same time
8) look at a class and the code that's calling it at the same time
Re: Vico Editor (Mac text editor)
#54Earlier quoted context omitted.
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.
I think it's a similar phenomenon to people closing windows to free up space on the taskbar (for GUIs that have such a thing like Gnome and Windows). If you remove the list of "open" things people are free to just do what they want and let the OS worry about paging if memory fills up and all that sort of thing. It's a pleasant experience if the abstraction doesn't leak, e.g. Win98 crashing if you opened "too many" pr…
A couple of years ago I used to keep 100s of tabs open in FF. Then I went mobile and started caring about watts. Not the same situation, but I think it influenced my few-files-open habits.
Re: Vico Editor (Mac text editor)
#55I really want to try out vim and tiling wm setup. Is this a good place to get my feet wet? I was going to just set up VM of ArchLinux.
Re: Vico Editor (Mac text editor)
#56So sad that this is closed source. It looks very nice but I feel very uncomfortable knowing that if there are any issues which bug or annoy me or things I would like to have but which do not exist yet, I can do nothing about it.
Re: Vico Editor (Mac text editor)
#57Another screenshot: http://ydeck.com/vico.png
Re: Vico Editor (Mac text editor)
#58There's definitely some neat stuff in there, though.
Re: Vico Editor (Mac text editor)
#59Earlier quoted context omitted.
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 thi…
It's beautiful because you can just write (or paste) text, then easily add the markup afterwards.
Re: Vico Editor (Mac text editor)
#60Nice start, looks like a nice bridge to Vim for textmate users. It's missing a few of the basic vim movement commands (which I have on a wallpaper I put together http://naleid.com/blog/2010/10/04/vim-movement-shortcuts-wal... ), but has most of the big ones. The ones I use quite a bit that don't seem implemented are: C-d - half page down C-u - half page up ge/gE - go to the end of the previous word (you do have e/E f…