Mercurial > mplayer.hg
comparison DOCS/xml/en/users-vs-dev.xml @ 11278:ff78d7ceecaa
Dead links updated or removed, Joe Barr section rewritten taking into
account his latest article.
author | diego |
---|---|
date | Sun, 26 Oct 2003 23:08:16 +0000 |
parents | 49b1a67e7381 |
children | 82f9b6d890ea |
comparison
equal
deleted
inserted
replaced
11277:fffd200d81a7 | 11278:ff78d7ceecaa |
---|---|
29 The GCC team disclaimed any link with GCC 2.96 and issued an | 29 The GCC team disclaimed any link with GCC 2.96 and issued an |
30 <ulink url="http://gcc.gnu.org/gcc-2.96.html">official response</ulink> | 30 <ulink url="http://gcc.gnu.org/gcc-2.96.html">official response</ulink> |
31 to GCC 2.96. Many developers around the world began having problems with | 31 to GCC 2.96. Many developers around the world began having problems with |
32 GCC 2.96, and started recommending other compilers. Examples are | 32 GCC 2.96, and started recommending other compilers. Examples are |
33 <ulink url="http://www.mysql.com/downloads/mysql-3.23.html">MySQL</ulink>, | 33 <ulink url="http://www.mysql.com/downloads/mysql-3.23.html">MySQL</ulink>, |
34 <ulink url="http://avifile.sourceforge.net/news-old1.htm">avifile</ulink> | |
35 and | 34 and |
36 <ulink url="http://www.winehq.com/news/?view=92#RH 7.1 gcc fixes compiler bug">Wine</ulink>. | 35 <ulink url="http://avifile.sourceforge.net/news-old1.htm">avifile</ulink>. |
37 Other interesting links are | 36 Other interesting links are |
38 <ulink url="http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html"> | 37 <ulink url="http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html"> |
39 Linux kernel news flash about kernel 2.4.17</ulink> | 38 Linux kernel news flash about kernel 2.4.17</ulink> |
40 and | 39 and |
41 <ulink url="http://www.voy.com/3516/572.html">Voy Forum</ulink>. | 40 <ulink url="http://www.voy.com/3516/572.html">Voy Forum</ulink>. |
46 may imply a performance penalty. | 45 may imply a performance penalty. |
47 </para> | 46 </para> |
48 </formalpara> | 47 </formalpara> |
49 | 48 |
50 <para> | 49 <para> |
51 You can read about the other side of the story | |
52 <ulink url="http://www.bero.org/gcc296.html">at this site</ulink>. | |
53 GCC 2.96 does not allow <literal>|</literal> (pipe) characters in assembler | 50 GCC 2.96 does not allow <literal>|</literal> (pipe) characters in assembler |
54 comments because it supports Intel as well as AT&T Syntax and the | 51 comments because it supports Intel as well as AT&T Syntax and the |
55 <literal>|</literal> character is a symbol in the Intel variant. The | 52 <literal>|</literal> character is a symbol in the Intel variant. The |
56 problem is that it <emphasis>silently</emphasis> ignores the whole | 53 problem is that it <emphasis>silently</emphasis> ignores the whole |
57 assembler block. This is supposedly fixed now, GCC prints a warning instead | 54 assembler block. This is supposedly fixed now, GCC prints a warning instead |
75 | 72 |
76 <para> | 73 <para> |
77 If you have problems with GCC 2.96, you can get 2.96-85 packages from the | 74 If you have problems with GCC 2.96, you can get 2.96-85 packages from the |
78 Red Hat <ulink url="ftp://updates.redhat.com">ftp server</ulink>, or just | 75 Red Hat <ulink url="ftp://updates.redhat.com">ftp server</ulink>, or just |
79 go for the 3.0.4 packages offered for version 7.2 and later. You can also | 76 go for the 3.0.4 packages offered for version 7.2 and later. You can also |
80 get <ulink url="ftp://people.redhat.com/jakub/gcc/3.2-10/">gcc-3.2-10 packages</ulink> | 77 get <ulink url="ftp://people.redhat.com/jakub/gcc/3.2.3-11/">gcc-3.2.3-11 packages</ulink> |
81 (unofficial, but working fine) | 78 (unofficial, but working fine) |
82 and you can install them along the gcc-2.96 you already have. MPlayer will | 79 and you can install them along the gcc-2.96 you already have. MPlayer will |
83 detect it and use 3.2 instead of 2.96. If you do not want to or cannot use | 80 detect it and use 3.2 instead of 2.96. If you do not want to or cannot use |
84 the binary packages, here is how you can compile GCC 3 from source: | 81 the binary packages, here is how you can compile GCC 3 from source: |
85 </para> | 82 </para> |
136 </para> | 133 </para> |
137 | 134 |
138 <para> | 135 <para> |
139 Another impediment to binary redistribution was compiletime optimizations | 136 Another impediment to binary redistribution was compiletime optimizations |
140 for CPU architecture. <application>MPlayer</application> now supports | 137 for CPU architecture. <application>MPlayer</application> now supports |
141 runtime CPU detection (specify the | 138 runtime CPU detection (pass the |
142 <option>--enable-runtime-cpudetection</option> option when compiling). It | 139 <option>--enable-runtime-cpudetection</option> to <command>configure</command>). |
143 is disabled by default because it implies a small speed sacrifice, it is | 140 It is disabled by default because it implies a small speed sacrifice, but it is |
144 now possible to create binaries that run on different members of the Intel | 141 now possible to create binaries that run on different members of the Intel |
145 CPU family. | 142 CPU family. |
146 </para> | 143 </para> |
147 </sect1> | 144 </sect1> |
148 | 145 |
155 only provides binary drivers (for use with XFree86), which are often buggy. | 152 only provides binary drivers (for use with XFree86), which are often buggy. |
156 We have had many reports on | 153 We have had many reports on |
157 <ulink url="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</ulink> | 154 <ulink url="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</ulink> |
158 about problems related to these closed-source drivers | 155 about problems related to these closed-source drivers |
159 and their poor quality, instability and poor user and expert support. | 156 and their poor quality, instability and poor user and expert support. |
160 Here is an example from the | |
161 <ulink url="http://www.nvnews.net/forum/showthread.php?s=fda5725bc2151e29453b2da3bd5d2930&threadid=14306">nVidia Linux Forum</ulink>. | |
162 Many of these problems/issues keep appearing repeatedly. | 157 Many of these problems/issues keep appearing repeatedly. |
163 We have been contacted by nVidia lately, and they said these bugs do not | 158 We have been contacted by nVidia lately, and they said these bugs do not |
164 exist, instability is caused by bad AGP chips, and they received no reports | 159 exist, instability is caused by bad AGP chips, and they received no reports |
165 of driver bugs (like the purple line). So if you have a problem with your | 160 of driver bugs (like the purple line). So if you have a problem with your |
166 nVidia card, you are advised to update the nVidia driver and/or buy a new | 161 nVidia card, you are advised to update the nVidia driver and/or buy a new |
174 | 169 |
175 <sect1 id="joe-barr"> | 170 <sect1 id="joe-barr"> |
176 <title>Joe Barr</title> | 171 <title>Joe Barr</title> |
177 | 172 |
178 <para> | 173 <para> |
179 Joe Barr became infamous by writing a less than favorable | 174 Joe Barr became infamous in december 2001 by writing a less than favorable |
180 <ulink url="http://www.linuxworld.com/site-stories/2001/1214.mplayer.html"> | 175 <application>MPlayer</application> review called |
181 <application>MPlayer</application> review</ulink>. | 176 <ulink url="http://www.linuxworld.com/story/32880.htm">MPlayer: The project from hell</ulink>. |
182 He found <application>MPlayer</application> hard to install, but then | 177 He found <application>MPlayer</application> hard to install, and concluded |
183 again he is not very fond of | 178 that the developers were unfriendly and the documentation |
184 <ulink | 179 incomplete and insulting. You be the judge of that. |
185 url="http://www.linuxworld.com/linuxworld/lw-2000-06/lw-06-exam.html">reading documentation</ulink>. | 180 He went on to mention Arpi negatively in his |
186 He also concluded that the developers were unfriendly and the documentation | 181 <ulink url="http://www.linuxworld.com/story/32887.htm">10 Linux predictions for 2002</ulink>. |
187 incomplete and insulting. You be the judge. | 182 In a followup review of xine called |
188 He went on to mention <application>MPlayer</application> negatively in his | 183 <ulink url="http://www.linuxworld.com/story/32716.htm">A streaming media player for the rest of us</ulink> |
189 <ulink url="http://www.linuxworld.com/site-stories/2001/1227.predictions.html">10 Linux predictions for 2002</ulink>. | |
190 In a followup | |
191 <ulink url="http://www.linuxworld.com/site-stories/2002/0125.xine.html">review of xine</ulink> | |
192 he continued stirring up controversy. Ironically at the end of that article | 184 he continued stirring up controversy. Ironically at the end of that article |
193 he quotes his exchange with Günter Bartsch, the original author of <application>xine</application>, | 185 he quotes his exchange with Günter Bartsch, the original author of <application>xine</application>, |
194 that perfectly summarizes the whole situation: | 186 that perfectly summarizes the whole situation: |
195 | 187 |
196 <blockquote><para> | 188 <blockquote><para> |
197 However, he also went on to say that he was "surprised" by my column about | 189 However, he also went on to say that he was "surprised" by my column about |
198 <application>MPlayer</application> and thought it was unfair, reminding me that it is | 190 <application>MPlayer</application> and thought it was unfair, reminding me that it is |
199 a free software project. "If you don't like it," Bartsch said, "you're free not to use it." | 191 a free software project. "If you don't like it," Bartsch said, "you're free not to use it." |
200 </para></blockquote> | 192 </para></blockquote> |
201 </para> | 193 |
202 | 194 Almost two years later in october 2003 he wrote another review called |
203 <para> | 195 <ulink url="http://www.newsforge.com/article.pl?sid=03/10/02/0343200">Mplayer revisited</ulink>. |
204 He does not reply to our mails. His editor does not reply to our mails. | 196 In it he came to the following conclusion: |
205 Here are some quotes from different people about Joe Barr, so you can form | 197 He had the following to say about MPlayer: |
206 your own opinion: | |
207 </para> | |
208 | |
209 <para> | |
210 Marc Rassbach has | |
211 <ulink url="http://daily.daemonnews.org/view_story.php3?story_id=2102">something to say</ulink> | |
212 about the man. | |
213 | 198 |
214 <blockquote><para> | 199 <blockquote><para> |
215 You may all remember the LinuxWorld 2000, when he claimed that Linus T said | 200 I would have to say that there have been improvements in the number of |
216 that 'FreeBSD is just a handful of programmers'. Linus said NOTHING of the | 201 features, in performance, and in documentation. It's still not the |
217 sort. When Joe was called on this, his reaction was to call BSD supporters | 202 easiest install in the world, especially for newbies, but it's a |
218 assholes and jerks. | 203 little better than it used to be. |
219 </para></blockquote> | 204 </para></blockquote> |
220 </para> | 205 |
221 | 206 and |
222 <para> | 207 |
223 A <ulink url="http://www.mplayerhq.hu/pipermail/mplayer-users/2001-December/009118.html">quote</ulink> | 208 <blockquote><para> |
224 from Robert Munro on the | 209 But more importantly, I didn't notice any recent comments about user |
225 <ulink url="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</ulink> | 210 abuse. I think I deserve some of the credit for that, even if I do say |
226 mailing list: | 211 so myself. Arpi and the rest of the project team must feel that way |
227 | 212 too, because they have taken care to remember me in a special section |
228 <blockquote> | 213 of the documentation included in the tarball. Like I said at the |
229 <para> | 214 start, some things haven't changed at all. |
230 He's interesting, but not good at avoiding, um... controversy. Joe Barr | 215 </para></blockquote> |
231 used to be one of the regulars on Will Zachmann's Canopus forum on | 216 |
232 Compuserve, years ago. He was an OS/2 advocate then (I was an OS/2 fan | 217 We could not have summarized our feelings towards Joe Barr better: |
233 too). | 218 "It's still not the fairest or best researched article in the world, |
234 </para> | 219 but it's better than it used to be." Hopefully the next time around |
235 | 220 we will meet each other's expectations. However, the credit for maturity |
236 <para> | 221 goes to our increasing age only, and maybe to being weary of flame wars. |
237 He used to go over-the-top, flaming people, and I suspect he had some hard | |
238 times, then. He's mellowed some, judging by his columns recently. | |
239 Moderately subtle humor was not his mode in those earlier days, not at all. | |
240 </para> | |
241 </blockquote> | |
242 </para> | 222 </para> |
243 | 223 |
244 </sect1> | 224 </sect1> |
245 </appendix> | 225 </appendix> |