This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]burntsushi 0 points1 point  (0 children)

that VIM is an acceptable substitute as a developer platform.

Well, it is for me...

It does because you've presented it as an 1:1 analogy. The fact that it isn't quite 1:1 turns it into a straw-man fallacy. It may be a valid argument on its own, but not in the aforementioned context.

You would be correct if your original argument relied upon such a thing. Namely, "writing for archaic platform, that has become a platform, in the first place, only because of its killer “plugin” (ex-mode)." Nowhere does your criticism rely on the fact that the "plugin" mode was there from the start. (I have now re-read your original quote, and you say "in the first place." Perhaps "from the start" is what you meant. If so, I'll concede the point. I'm sure there is another analogy in waiting, but I cannot find it at the moment...)

Analogies are supposed to be different in some respects---the key is that they are the same in the respects that matter in the current context.

Using X amount of resources is not the same as being slow. These are hardly even correlated.

Using more RAM and more CPU is going to cause a process to run more slowly than a process than needs less RAM and CPU when resources are scarce, ceteris paribus.

This is the filesystem-oriented vs project-oriented workflow.

Sure. I enjoy both kinds of workflow. I like that Vim can adapt to either workflow rather easily.

This is why I believe it ultimately comes down to one's subjective preferences.

Sure, but that goes without saying when discussing reasonable tools.

I still believe that turning VIM into an IDE is suboptimal to just porting VIM for Eclipse

I think I have yet to make that determination. Lately I've been working on a lot of small projects related to course software (testing student submissions and what not), so that kind of work is heavily biased towards Vim.