[ I'm branching off from here and not from later posts on purpose ... ] On Wed, 22 Aug 2007, Linus Torvalds wrote: > "git reset" is a command, not a scripting language. We can still script > git as much as we want, but the fewer dependencies we have on anything > external, the better off we are. > > I don't understand why people consider scripting languages (whether shell, > perl, or anything else) "better" than C if there is an alternative. Once > the C work has been done (and if you require C _anyway_ for other reasons, > like git does), doing it in C is simply superior. Absolutely no argument with that. Considering that "git reset" is a command, the language used to implement it is just that: an _implementation_ "detail". Especially if the C conversion has already been done. > We ended up writing our own versions (or merging other peoples code) for > things like appying patches, generating diffs, three-way merging etc, > because not having external dependencies is *so* much more maintainable > and portable that it's not even funny. Indeed. And this is the very same reason why Git should _also_ acquire a script interpreter of its own if we want to continue bragging about Git's easy scriptability. > I'd love for every single shell-script in git core to be written in C, so > that we can drop the dependency on shell *entirely*. What about the test suite? > I also dispute your "easy to do". Quite often, shell (or any scripting > language) is actually much *more* complicated than C. Yes, the C code may > be more lines (in this case, the shell script is 106 lines, and the C code > was 216 lines), but from a maintenance standpoint, C has had *much* fewer > problems than the shell script stuff has ever had! Let's not talk strictly about this very case. Like we agreed above, the C conversion has been done so there is no downside really not to move on with the C version. Same for other core commands if/when they get converted. That would still be nice, though, if we could have a unified scripting language for Git, that didn't have any nasty external dependency either. If only so Git could be self sufficient on any platform it is ported to for its test suite, and also for extra functionality that users would end up sharing across the whole user base and not only on platform where bash comes installed by default. And there might be some cases where using that same scripting language for permanently implementing actual command could simply make sense once it can be safely depended upon. > So scripting languages are often good for *prototyping*, and a lot of > people like scripting languages for that reason. But once something is > already prototyped, and if somebody then rewrites it in C, all the > advantages of a scripting language have already disappeared! > > So yes, we could just make the shell/etc from busybox _be_ the scripting > language, but the fact is, that is *more* C code than just making the > commands C code in the first place, and while a lot of the effort is > already done for us, "busybox under windows" is actually likely to be more > of a maintenance problem than "native git commands under windows" are. Possibly. Again that depends how much we need from it. We don't need _that_ much from a shell and the bad portability issues can certainly be avoided altogether simply by ripping out problematic functionality. Such shell doesn't even have to be POSIX compliant or whatever. > So if we have the choice, and somebody has written a git command in native > C code, I think we should *always* take it. Just because it means that > _eventually_ we can drop shell entirely, even if it would be a git > internal busybox shell. It could be taken the other way around too: If we have the choice, and somebody has ported a subset of busybox to Windows tailored for Git plumbing usage, then we _could_ stop worrying so much about shell portability right there and redirect our efforts toward other things. Nicolas - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
