Related:
http://tasvideos.org/forum/viewtopic.php?p=356544#356544
From IRC discussion though, adelikat hated the idea back then :D
klmz is back!!!
EDIT: now, my actual thoughts.
Before I touched bizhawk code (last summer), I was under general impression that .net/C# is something not so good, especially having not-so-amazing cross-platform compatibility (that would rule the world if it was there, just like Qt is conquering it, but Qt is for C++, and has no C# bindings). Well, the Mono branch works on Mac, but no one yet succeeded compiling it on Linux, and we're not even talking about
microwaves android. However, that would be fixable if there was a dedicated Linux dev, and Linux devs hate C#.
Then I saw OOP for the first time, while debugging it. That first impression was terrible. Then I actually started committing. And you know what? I love it. A huge part of it is that IDE bends over backwards to make your work comfortable. Especially resources managment, especially after winapi (most emulators I saw, and tasers used, are winapi). I also got hooked by overall language simplicity, unlike in some advanced C++ (well I'm not touching complicated matters, but what I do touch feels very nice). And there's a freaking ton of .net classes for all cases.
About bugs. I opened tastudio for a few times during its first years of existence, and... I didn't believe in it. Then adelikat made some amazing progress, based on old legacy of fceux, and on my current notion, then SuuperW joined, and those 2 got the business perk! So when I moved in, it was already a workable tool, but with tons of bugs. So what did I do? I started hunting them down. After half a year, I only know of a couple bugs in tastudio that I just haven't gotten around to fix. That's it! A couple of bugs man. It's fully workable now!
It means, it just takes a person who knows what he's doing to come and trace those bugs, they exist because someone haven't yet had time (or interest) for checking all the possible situations. We have tasers for that in a way: they try all possible situations daily. So it only takes a coder interested in getting the tool working.
Finally, there's insane interaction between tools, so you won't make it any easier, if each tool goes in a separate dll. And if they go all in one, it will be just as complicated as bizhawk, to say the least. Bizhawk is so huge and complex because the logic it accounts for is that huge and complex. (Generic) you can make it simpler, but without knowing what you're doing it will definitely break something else. So I entrust rerecording to people who've been on the rr-scene for a decade, and also contribute things that I am fully confident in.
