On 3/28/06, <b class="gmail_sendername">Kuba Ober</b> <<a href="mailto:kuba@mareimbrium.org">kuba@mareimbrium.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Python!!?! i almost did a C | N > K (that would be cola, pepsi rather,<br>> through nose to keyboard)<br>><br>> ok ok ok ok although i almos-t ruined a perfectly free and good<br>> keyboard, i don't like python cause i don't know it, and the learning
<br>> curve has been... dreadful.<br>><br>> Can't we do this in C?<br><br>I hope you meant C++, unless you think it's productive to do a poorly<br>documented and bug-ridden reimplementation of half of C++ standard library*
<br>everytime you want to do something other than a hello world application.<br><br>Actually, for tools like wine doors it'd be more concise to do the logic in<br>Lisp, rather than Python or C++. The problem is that wine-hackers-wise, I
<br>would bet we have way more people skilled in C++ than people skilled in<br>Python than people skilled in Lisp, so methinks that C++ is the right way to<br>go, just because of the sheer number of developers available<br>
<br>C++ (and Python) gives you an advantage of being able to directly** leverage<br>Qt to have wine doors that can either work as a regular unix application, or<br>a windows application under wine itself. Heck, it'd work just fine on Intel
<br>Mac boxen, and on PPC Mac boxen whenever wine will utilize some emulator<br>platform.<br><br>Cheers, Kuba<br>* yes, it's a slightly modified quote from somewhere else ;)<br>** as opposed to say doing only the GUI in C++ and logic in Lisp
<br><br><br></blockquote></div><br>Java, anyone? lol oh wait wait I got one better.. Fortran... or no, how about................... COBOL!! LMFAO gimme a break..<br><br>Seriously though, why not break winedoors up into different components, and then have different submaintainers, and each component can be written in the language that that submaintainer is most comfortable with? Obviously each piece of code would go thru the project maintainer, and so if someone started writing another "door" in bash, then that door could quickly be closed (pun intended).
<br><br><br>As for the GUI, make it C or C++, only because that is the most widely used language in linux..<br><br>Tom<br>