Originally posted by Eleksir
C'mon, no one happy using this buggy-and-bloat wxWidgets, especially people with such a big and fat distros like Mandriva, Fedora, Debian, SuSE and (users of ports of)FreeBSD - in their repositories lay obsolete versions of wxWidgets and ofcourse aMule
We're happy using it. And we're happy contributing back to it to make it better. Actually, one of the most important team members here is coding for them, and a contributor and friend is one of the wx developers. Debian has the latest wxWidgets stable release. I don't care about the others, and if they don't, it's their fault, not wxWidgets fault.
By the way, I didn't mean drop this wxCrap immediatly after I suggest to drop it -
You're really constructive. Wow,
wxCrap[/b]. That is a REALLY MATURE position on the issue.
I understand that it's like a drug - the whole thing of aMule addicted to wxWidgets, and it's not too easy to drop this additional layer, and potential source of bugs
..like any layer. And I must say that in the 3 years I have been working with it, I found very few serious bugs. And those I found are fixed quite fast.Sometimes by me.
; but little by little you can refuse of using it by replacing first of all networking code and make, as a first step, wx-free amuled (daemon part), gui can wait for it's time, just try minimize usage of wxWidgets especialy in network-related code, because wx has a weak place here (not enough robustness, lack of support epoll and kqueue).
Really SMART move on the network one. Because, you know, I'm more or less the mantainer of wxWidgets network classes now, and I'm rewriting lots of it for Google's Summer Of Code program, and get paid for it. Yay!.
I would love to know how are you planning to support epoll and kqueue on anything non-linux or BSD. It's a really, really interesting question.
About C - nice language, you know, not overbloat with such a nice and handy stuff as C++ but binaries generated from c-sources are less in size and faster than binaries generated from cpp-sources, c is less sophisticated language, so you 'll make less design defects (aka bugs) while programming, and more easily catch them during debug sessions (why do you think linux kernel is written in pure C?).
This part I will mark it as bullshit and guess you just have no real idea what you're talking about.I specially like the "c is less sophisticated language, so you 'll make less design defects" part. The other parts are just biased opinions against C++ (and false ones, btw), but that one... it's not even logical.
The kernel comment is really, really comedy gold.
And one more thing, Kry, you should be more constructive and positive, no one here, in forum, _orders_ you (and anyone of aMule team) what to do and how to do - it's just a thoughts and suggestions, forum has created only for those purposes, right?
I am constructive and possitive. I'm constructive TOWARDS wxWidgets and possitive TOWARDS wxWidgets, which you see as being negative towards YOU.
Of course it's thoughts and suggestions. But you came here insulting and flaming the multiplatform, native-widgets framework we have been using for years, and without it, mind you, aMule would never exist, as lmule wouldn't have been created in the first place by Tiku.
