On Thursday, January 16, 2014 9:14:31 AM UTC-6, MarcWeber wrote: > > > One of the main issues is: > > - documenting source does not add value >
I'd argue that documenting the source DOES add value. It makes the code easier to maintain and develop. It's just not a fun job. Documenting why the code is the way it already is, is less fun than fixing bugs or adding features. I'd certainly recommend anybody making a patch to add comments explaining the code they had to figure out in order to make the patch though. It should help somebody down the road in figuring out the same code. > - patching Vim would, but which is the best upstream for Vim? > > Do we want to keep using C (I don't think so, because even Bram sayd > > that coding higher level stuff in C is tough) > > > > I personally would like to find ways to share code with other editors, > > too. I very sure that C is the wrong tool to do so. Maybe it does not > > exist. > > C may be the wrong tool, if you wanted to start a brand-new editor from scratch. But re-implementing Vim from the ground up would be a terrible idea. Literally decades of work has gone into Vim. That is decades of bug fixes and feature additions which would take forever to re-write. We'd have tons of regressions for corner cases we don't remember happening on weird system configurations, we'd have tons of new issues introduced, and it would take years at a minimum for Vim to become stable enough to use again, if that ever happened. Some thoughts on complete rewrites, where it is called the "single worst strategic mistake" you can make in developing software: http://www.joelonsoftware.com/articles/fog0000000069.html I'd be all for refactoring or rewriting large portions of Vim. But we need to do it one piece at a time. Doing something like abandoning C and trying to port all functionality to C++ would be a gigantic waste of time that will only hurt Vim in the end. > > > I even think about 'what would happen splitting runtime from Vim, and > > upload it to bitbucket / github' ? > > I like this idea and it's been discussed in the past. If I recall, Bram was not interested in pulling updates from a separate repository for runtime. So the idea kind of died before it really started. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
