<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>If you are making it extremely easy for users to run with native dlls</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
and hacky workarounds, then you are hurting Wine. Wine is still beta,</blockquote><div><br>That's true... and people technically should only be using wine for the pure sake of testing and helping fix usage. LEt's be honest, very few use it for that, they just want it to work, they use wine for the use the Devs want out of
1.0. Saying to someone that because it doesn't work by default, we're not going to let you use it, or in general make it hard for them defeats the goal of the *actual program*, Joe XYZ wants to play Oblivion, He Finds it doesn't work! He looks around and sees that if he does a lot of various things it will work *okay*, Joe XYZ does them. Joe XYZ had no intention of ever submitting bugs at all, is this bad? Hell yes it is. We should educate at how important it is for a program like Wine to have nice detailed Bug Tracking, but at the same time, can you blame him for just wanting it to work, easily? As long as the user, at some point, realized, hey this doesn't work out of the box, the job is done to some degree.
<br><br>To summarize, If a user never was going to report things, that's bad, he should be educated, but at the same time, if he still wouldn't, shouldn't it be our job as the community to make it easy for him?
<br><br>This goes back to the WineTools thing... that was bad though, even though at face it seems the same... in reality people were starting to just say Install Wine, then you *need* to install winetools and run the base install thing, without ever actually saying "HEY! Newbs! This wont work so you should install zyx to make it work as a temporary solution until such a time as it's fixed in the wine tree." OR something similar.
<br><br>I guess my point is two fold:<br>-The user needs to know about bug reporting.<br>-The user needs to know what it means for something to not work 'out-of-the-box', and what exactly a 'dirty little hack' or the like is.
<br><br>end rant<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">and we need as much testing and bug reporting as possible. You take
<br>away users that help the development process, and attach them to your<br>project so that when they have a problem with app xyz, they file a<br>report with your project, not Wine, and you add the necessary hack to<br>make it work for them. In short, you leech off the hard work of all
<br>the Wine developers and give nothing back in return (quite the<br>opposite in fact). If you have any reason to believe that you are<br>helping Wine, I'd sure love to hear it.<br><br>--<br>James Hawkins<br><br><br>
</blockquote></div><br><br clear="all"><br>-- <br>Cheers,<br>Bryan