Note that this is a very contentious view put forth by the author of cdrecord.
Joerg Schilling, the cdrecord author, claims that because there is significant overlap between ATAPI and SCSI, that ATAPI is in fact SCSI. This is patently untrue. SCSI is one thing, and ATAPI is another. They have different specifications, different standards bodies, and varied differences which make them incompatable. It may be that they are similar enough that some code can be retargetted from one to another without much change, but that does not make them the same.
It is this position that cdrecord has taken that has given rise to all linux distributions patching cdrecord to remove its need to think of IDE cd devices as SCSI. cdrecord underlines the falsity of this position by insisting on identifying the IDE device by the BUS:ID:LUN tuple from the SCSI world which does not actually exist in the IDE/ATAPI world. The need to feed invented nonsense numbers into cdrecord in order for it to bother to access the IDE/ATAPI device is the reason that this software has been patched to allow specification of/dev/hdc like a normal unix utility.
I strongly believe that this is the case where listening to your users results in inferior software. Users disliked spatial because it is not what they are used to, not because it's actually worse. Spatial has significant advantages over the necessary clutter that "browser" file managers must acrrue to offer the same kinds of functionality that spatial file managers offer by default.
However, the user base has calcified around the windows way of accessing their files, and is uninterested in returning to the superior macintosh paradigm. The Gnome developers caved, and as in so many other areas of their UI, have defaulted to apeing Microsoft.
They may end up with more users, but whether Gnome will be better off for it in the long run only time will tell.
This is pretty foolish. If you're going to run x86, there are a lot of cheaper machines that work just fine and will give similar performance. Running x86 on amd64 is basically throwing 40% of your performance out the window, as well as memory advantages, and running a needlessly power-hungry (read expensive to power) machine.
Well it seems true that currently opteron chips are not well set up for medium scale parallel processing in the style of starfires etc. They'll probably get there, however.
I've actually _tried_ all those distributions on a Sun 20z, and while Gentoo and SuSE both worked fine, FreeBSD and Debian aren't even ready for x86_64. Red Hat was notably unworkable, sadly. Maybe we only sacrificed enough goats for two distritubions.
The rule for suicide applies in japanese rules (americans generally play under slightly modified japanese rules, AGA rules), but not Ing or Chinese rules. Suiciding a single stone would never be a good idea (you give away a point and a turn), but suiciding a group can be advantageous. It's always struck me as dumb to disallow this.
The SuperKo rule I believe is incorporated into Ing rules? But most broadly used rulesets do not have this rule. A game which enters into a stalemate via 3 simultaneous equally valuable kos is considered differently in different game rules sets. In american go it is considered a draw, and so a winning player should allow it to end. In a japanese game it is considered a null game, is stricken from the record, and the game is started again. I've found this practice very strange as well.
So, for correct computer play, it is necessary to describe the rule of Ko in a more complex fashion. A player is not allowed to place down a stone if, after the rule of capture has been applied, the resulting Board position is the same as that two positions prior (on the previous last turn of the opposing player).
Komi are the extra points given to white (who plays second) in an even, 19 by 19 full game.
In smaller games, there is no official komi valuation, because it is not really the full game of go, just an amusing diversion, learning exercise, or what have you. In learning and handicap games, komi is not usually worried about, and the game is often scored "as-is", thus making ties possible. However, as these types of games are not often close, and as the victor is genearlly less important than the learning, it is not worried about.
If you think it's okay to have "serious reservations" about your fellow citizens simply for the way they are, perhaps you should be willing to justify them in any way.
You write this post in an attempt to categorize "homophobia" as name-calling only, but your post itself is empty of any content. You posture yourself as one exposing this name-calling but make no effort to substantiate your own questionable view.
"Homophobia" is not an empty phrase. It is used as a name to cast at people at times, but there exists real irrational dislike and sometimes fear and even hatred of homosexuals, homosexual behavior, and related ideas. Often, this fear is directed inwards, but it sometimes results in hatred and lashing out at others. This is not a made-up thing. The term is overbroadly applied, but it is the source of more dislike of homosexuals than you might be willing to accept.
I think the point is not really that software raid is bad, but that software raid is pointless since Linux already does that just fine thankyouverymuch.
Programming is not management. IT professionals are not predisposed towards management, and only a small percentage of them will be successful at this very different type of occupation.
What if N developers migrate to N management positions and 3*N offshored developers?
Yes, clearly this is the scenario the author is suggesting will happen. However, I have to raise a contention with the idea of these management positions being "IT" positions. Mangement is really management, no matter what you're managing. Things like system administration, programming, and systems analysis are the actual IT.
What is being proposed here is moving various aspects of the IT industry while retaining the management in the US.
What I ask is: what is it about management that Indian companies cannot do? Management is not a "core competency", and is in fact an area of business that has proved very hard to do well for all modern societies, but seems especially poor in the US. This whole "net gain of jobs in the IT industry" seems like a very unstable temporary situation, if all the real technical work is moved offshore.
Not that I suggest this is "evil" or "wrong", and it may be economic inevitability, but this placation argument doesn't really hold any water for me.
If you look these up you will find that their defintitions are not the same.
Note that the Kohan port was trumpeted during a time that Loki was still selling the product. Insiders may have known Loki was not long for this world, but it was not announced in any way. It seems to me Transgaming was only too hapy to drive a nail into that coffin.
WineX is under an open license, it's true, but the behavior of TransGaming surrounding WineX makes it effectively nonfree. Ie. Don't really use it or we'll take it away.
Whether WineX helps or hurts Linux gaming is certainly debatable. I think you'd have to run the experiment both ways to know.
Giving things back doesn't mean running your own control-freak CVS with semi-open project. This is more like not preventing others from taking them back.
And anyway I'm not pleased by your staraw man about "making them evil" which I explicitly did _not_ state. I did state they are not community oriented and substantiated it.
Because it hasn't got word? I can't see what's missing here, or mabey I'm just completely out of touch with the kids around here...
Well, around here which is Oakland, CA, an elementary school east of chinatown was outfitted with Linux systems, one per classroom. They use email, make webpages, and so on, none on "class" time, but all on extra time. I have watched second graders handling it just fine personally.
Feel free to check it out yourself if you're in the area.
Slashdot Mirror
Wow, this troll was old in 2003.
http://tinyurl.com/4vxlf
Note that this is a very contentious view put forth by the author of cdrecord.
/dev/hdc like a normal unix utility.
Joerg Schilling, the cdrecord author, claims that because there is significant overlap between ATAPI and SCSI, that ATAPI is in fact SCSI. This is patently untrue. SCSI is one thing, and ATAPI is another. They have different specifications, different standards bodies, and varied differences which make them incompatable. It may be that they are similar enough that some code can be retargetted from one to another without much change, but that does not make them the same.
It is this position that cdrecord has taken that has given rise to all linux distributions patching cdrecord to remove its need to think of IDE cd devices as SCSI. cdrecord underlines the falsity of this position by insisting on identifying the IDE device by the BUS:ID:LUN tuple from the SCSI world which does not actually exist in the IDE/ATAPI world. The need to feed invented nonsense numbers into cdrecord in order for it to bother to access the IDE/ATAPI device is the reason that this software has been patched to allow specification of
I strongly believe that this is the case where listening to your users results in inferior software. Users disliked spatial because it is not what they are used to, not because it's actually worse. Spatial has significant advantages over the necessary clutter that "browser" file managers must acrrue to offer the same kinds of functionality that spatial file managers offer by default.
However, the user base has calcified around the windows way of accessing their files, and is uninterested in returning to the superior macintosh paradigm. The Gnome developers caved, and as in so many other areas of their UI, have defaulted to apeing Microsoft.
They may end up with more users, but whether Gnome will be better off for it in the long run only time will tell.
Good job failing to grasp the definition of proprietary.
But the superko rule doesn't actually describe real go. It's a simplification that's inaccurate.
Furthermore, it suggests that the "board state" is merely the stones on the board, when in actuality it is also the last stone played.
This is pretty foolish. If you're going to run x86, there are a lot of cheaper machines that work just fine and will give similar performance. Running x86 on amd64 is basically throwing 40% of your performance out the window, as well as memory advantages, and running a needlessly power-hungry (read expensive to power) machine.
Well it seems true that currently opteron chips are not well set up for medium scale parallel processing in the style of starfires etc. They'll probably get there, however.
Strange.
I've actually _tried_ all those distributions on a Sun 20z, and while Gentoo and SuSE both worked fine, FreeBSD and Debian aren't even ready for x86_64. Red Hat was notably unworkable, sadly. Maybe we only sacrificed enough goats for two distritubions.
Some comments:
The rule for suicide applies in japanese rules (americans generally play under slightly modified japanese rules, AGA rules), but not Ing or Chinese rules. Suiciding a single stone would never be a good idea (you give away a point and a turn), but suiciding a group can be advantageous. It's always struck me as dumb to disallow this.
The SuperKo rule I believe is incorporated into Ing rules? But most broadly used rulesets do not have this rule. A game which enters into a stalemate via 3 simultaneous equally valuable kos is considered differently in different game rules sets. In american go it is considered a draw, and so a winning player should allow it to end. In a japanese game it is considered a null game, is stricken from the record, and the game is started again. I've found this practice very strange as well.
So, for correct computer play, it is necessary to describe the rule of Ko in a more complex fashion. A player is not allowed to place down a stone if, after the rule of capture has been applied, the resulting Board position is the same as that two positions prior (on the previous last turn of the opposing player).
That is correct, if komi is included.
Komi are the extra points given to white (who plays second) in an even, 19 by 19 full game.
In smaller games, there is no official komi valuation, because it is not really the full game of go, just an amusing diversion, learning exercise, or what have you. In learning and handicap games, komi is not usually worried about, and the game is often scored "as-is", thus making ties possible. However, as these types of games are not often close, and as the victor is genearlly less important than the learning, it is not worried about.
Well, the specific information as to who it is better would be in the SECOND half of the post.
Interesting. Under BeOS 4.x my sound would sometimes drop out permanently and never recover. No message and no sound.
I have never had this problem on Linux save when I briefly flirted with commercial drivers for the Terratec 64. "Open Sound System" was always a joke.
They may not be in the street, but they're often avilable for viewing in some fashion.
If you think it's okay to have "serious reservations" about your fellow citizens simply for the way they are, perhaps you should be willing to justify them in any way.
You write this post in an attempt to categorize "homophobia" as name-calling only, but your post itself is empty of any content. You posture yourself as one exposing this name-calling but make no effort to substantiate your own questionable view.
"Homophobia" is not an empty phrase. It is used as a name to cast at people at times, but there exists real irrational dislike and sometimes fear and even hatred of homosexuals, homosexual behavior, and related ideas. Often, this fear is directed inwards, but it sometimes results in hatred and lashing out at others. This is not a made-up thing. The term is overbroadly applied, but it is the source of more dislike of homosexuals than you might be willing to accept.
I'd say HR protects HR at level 0, but otherwise it jives with my experiences.
I think the point is not really that software raid is bad, but that software raid is pointless since Linux already does that just fine thankyouverymuch.
So, there's no problem with C++ so long as we assume all the tools and users are perfect.
That's what you said, right?
Yes, OOP works beautifully, all you have to do is predict the future.
Nope, it's still broken. I see posts by michael all the time which I've requested filtered out for many years.
Oh, and I forgot my second point, which is:
Programming is not management. IT professionals are not predisposed towards management, and only a small percentage of them will be successful at this very different type of occupation.
Yes, clearly this is the scenario the author is suggesting will happen. However, I have to raise a contention with the idea of these management positions being "IT" positions. Mangement is really management, no matter what you're managing. Things like system administration, programming, and systems analysis are the actual IT.
What is being proposed here is moving various aspects of the IT industry while retaining the management in the US.
What I ask is: what is it about management that Indian companies cannot do? Management is not a "core competency", and is in fact an area of business that has proved very hard to do well for all modern societies, but seems especially poor in the US. This whole "net gain of jobs in the IT industry" seems like a very unstable temporary situation, if all the real technical work is moved offshore.
Not that I suggest this is "evil" or "wrong", and it may be economic inevitability, but this placation argument doesn't really hold any water for me.
Sorry, I meant ReWind is under an open license.
Available. Open.
If you look these up you will find that their defintitions are not the same.
Note that the Kohan port was trumpeted during a time that Loki was still selling the product. Insiders may have known Loki was not long for this world, but it was not announced in any way. It seems to me Transgaming was only too hapy to drive a nail into that coffin.
WineX is under an open license, it's true, but the behavior of TransGaming surrounding WineX makes it effectively nonfree. Ie. Don't really use it or we'll take it away.
Whether WineX helps or hurts Linux gaming is certainly debatable. I think you'd have to run the experiment both ways to know.
Giving things back doesn't mean running your own control-freak CVS with semi-open project. This is more like not preventing others from taking them back.
And anyway I'm not pleased by your staraw man about "making them evil" which I explicitly did _not_ state. I did state they are not community oriented and substantiated it.
Well, around here which is Oakland, CA, an elementary school east of chinatown was outfitted with Linux systems, one per classroom. They use email, make webpages, and so on, none on "class" time, but all on extra time. I have watched second graders handling it just fine personally.
Feel free to check it out yourself if you're in the area.