The G5 doesn't have that option- it's Big or not at all. Microsoft's going to have to deal with endian-ness and so are vendors who are targeting Windows and X-Box2.
It can be the keys to the kingdom. In the case of WiFi cards, there's less discrete hardware and a hell of a lot more software in the form of DSP code. Most of the modern WiFi cards happen to be software radios and you can exceed power limitations, recode the thing to broadcast on bands that aren't allowed, etc. In the case of DSL chips, it's the same story.
The code's typically written to an API with an abstraction layer in most well written games- come up with a different abstraction layer and you have the game running on a different API. How in the hell do you think the MacOS and Linux games that DO get ported happen? It's not as you say, no matter what you might think.
DirectX compatibility is only needed if you're simply recompiling for a new target. Most games abstract out the DirectX layer for their engine so they're not dealing with it directly (You'd be stupid to do anything else, really...) therefore it's only a small effort to provide a comparable OpenGL specific layer. Once you've done that, that's one less thing. Typically, most games are using FMOD, Miles, or SDL/OpenAL for their sound. That means the sound is taken care of. It's a minimal effort to make a version of user input code for SDL (your Linux and MacOS X choice...) to replace your DirectInput code. There's several cross-platform choices for network support and while it's an effort to make something work as a replacement for DirectPlay code, it's been done (I know, I've done it myself and helped produce a minimal wrapper layer to allow several pieces of code simply recompile for Linux.) What you speak of simply isn't really much of an impediment for anything except the smallest development studios producing valueware as they're coding strictly to DirectX because it costs them nothing at all.
The biggest impediment for most studios, typically, for going to PPC is that most games make assumptions about the order of bytes, etc. that are far, far removed from best practices. Assumptions that make for difficult migration of code. The same goes for going from 32 to 64 bits- many developers do things like assume pointers are the same size as ints and proceed to interchange them liberally.
If you're making a game for PPC64, those impediments go bye-bye for making a MacOSX game- and since MS is going to probably be suggesting that the games be made available for XP on x86, the code's probably going to be endian neutral as well.
First off, games written for an X=Box or an X=Box2 will NOT be written to bare metal, it'll be written to a variant of XP embedded. That takes your current assumptions of the complexity of dealing with a PCI bus controller, GPU, or DSP and throws it out the window from the top of the Empire State Building.
Unless the game is written an X-Box only game, this means that they're most likely going to be using some abstraction code (and even then...) to make life easier and allow them to target PS2/3 and whatever Nintendo's planning to field. This means you can do the same sorts of things to target Linux/MacOSX- and since it's going to be Endian neutral (it'd have to be, unless MS is going to do something stupid and make the PPC run in little-endian mode (which works, but it's not it's native world...)) it's going to have one of the biggest issues for porting between MacOS X and other OS targets already killed off.
I might suggest some contemplation of your understanding of things and improving upon it considerably before posting on the subject again.
If you go through the motions of doing a Linux port, and you've done it right, you end up with a MacOS X port anyway- just recompile against it and that's pretty much it.
Now, having said this, it's not so much the differences between OSes that's the problem with porting games. Many of the houses are using cross-platform libraries or off-the-shelf engines which support Linux/MacOS X out of the box. It's more of a problem of all the "enhancements" that the studios do the engines and the short-cuts they take in the code that make it a pain. There's quite a few nasty, far from best practices things that VC++ lets you do that causes no end to pain trying to port games over to another platform.
Sadly, most, if not all, of the companies that provide outsourcing services in India and elsewhere tend produce substandard code. Yeah, they code like banshees- but the results are far from optimal. This is from personal experience, working as a contractor within a large multinational corporation.
No, but they could look forward to being tortured in prison for the slightest thing or gassed to death with Mustard, Tabun, Sarin, or VX. He did all of those things- it's on record for him as such.
Get the notion that they were better off without the intervention out of your head. Saddam and his cronies were a sadistic bloodthirsty lot themselves, not really any better than the current set of lunatics causing problems over there.
What difference was it that Saddam was in charge (realize that he gassed the religious extemists...) and now it's not Saddam that is in charge- the extremists aren't in charge now either.
So, the parent's post really isn't accurate or insightful no matter HOW you paint it. Neither is yours.
He was not in compliance in any way shape or form with the cease-fire treaty with Gulf War I. The UN acknowleged this. It's part of why they did very little about us doing the Gulf War II incursions.
Oh, and by the way, they DID find that while he didn't have WMDs, he was equipping up to have them within only a couple of months of the lifting of sanctions, etc. He had people burying hot reactor parts in their yards, etc.- they've just began to scratch the surface with this mess. It's not all like you've been led to believe it was, either way.
The radical Islamics are the ones killing off the Iraqi National Guard troops in the name of Allah- they just butchered 50 some-odd people in the name of Allah just this last week.
Grow up and find out what is REALLY going on in the world- and it's not all lilly-white pure on our side, but they're not innocents over there that we "oppressed".
When you think about it, "something in place" is not a good excuse for voting for something that is patently in violation of their Oaths of Office (i.e. They swore to uphold the Constitution- voting on something that is concretely in violation of the same is NOT upholding it!). If it was flawed, they should have fixed the damn thing or tabled it permanantly.
What you're doing when you add anti-freeze to a watercooling rig is trying to offset corrosion effects (it's water after all- it's going to have anodic effects on the waterblocks, radiator, etc..) and to prevent mildew and algae buildup in the thing.
This would depend entirely on whether you exceed the heat-pumping capacity of the refrigerator. If you don't exceed the amount being pumped out of the space, it will cool down, the rate being dependent on the rate of thermal transfer above and beyond the heat source's generation of heat.
I've seen active refrigeration systems coupled with water cooling that were based off of mini-fridges (There was one that won a case-mod prize at QuakeCon 2003...). The CPU was cooled down below ambient and he was able to keep Bawls and Cokes cold in the thing.
In actuality, water's a superior refrigerant so long as you're not trying to cool down below freezing and can come up with a compressor with the right volumetric capacity under vacuum. When water boils, it pulls roughly 2700 BTUs out of the surounding environment per liter boiled. At 6 bar, water will readily boil at somewhere around 40deg F, dragging that much heat out of the environment as quickly it can be absorbed by the water under those conditions. The big issue is that it's volumetric rate (how much volume you have to pump out of the low-side of the system...) is roughly double any other possible refrigerants out there. There's currently not that many vacuum pumps that can actually DO this sort of thing and the ones that do are typically rather expensive- so we don't currently use water as a refrigerant.
Now, as to why water's used instead of refrigerants is that it's cheap (An R-134a system would set you back a solid 500 or so, a watercooling rig will set you back only $150-250 and does a better than adequate job (especially if you're looking for normal operation with less noise and less CPU heat...), and it has a heat capacity that makes for a very nice thermal transfer medium. It's why you water cool cars and trucks.
Look on the shelves. There's this little white pill that everybody and his dog made (and still makes)- it's called ASPRIN.
No patents, yet everyone still makes the damn stuff and makes loads of money on it (or else nobody would bother with it...).
Discard your cherished notions of what will/won't be done with or without "IP"- the current notions about it are really, really recent in history. The thinking you espouse is a very nasty double-edged sword. With all this IP "protection", there's no benefit for anyone except the biggest players to make ANYTHING since it's already "Patented", "Copyrighted", or "Trademarked". The biggest players really, really don't have much incentive to make new stuff because it'd take money away from the stuff currently making money and it could temporarily cut off a cash cow (in spite of it maybe making a hell of a lot more money in the long term...).
There was the, "Don't make me turn this car around" feature in the car as well as the "Parent's backhand of death" feature in the car. It more than often was installed in the car by default, even...
You place a call request to one presence server that has a given URI for the person you're wanting to call, including their ID on the server. From there your SIP endpoint software does the rest, including calling landline endpoints.
An example would be:
sip:foo@mysipserver.net
Another would be:
sip:18005551212@mysipserver.net
In the first case, you're calling directly to another SIP endpoint. In the second, you could be calling a SIP endpoint or a PSTN terminated endpoint- the URI wouldn't matter.
MacOS X's core is already available as an x86 version. All they'd need to really do, since a very sizeable portion of the Aqua interface system is written in Objective C, would be to account for endianness and call it done. It'd take all of a 6-12 month project, I'd suspect, to put it into an alpha class release stage.
Microsoft, on the other hand, would probably have a nightmare on their hands as I suspect they've not taken any consideration for endianness, 64 bits (No, they still don't have it out in the hands of the public- it's been months now and they knew about amd64, etc. for some time now...)- it's probably all nasty, crufty x86-32 code and using some aborted NT 3.51 code wouldn't help out much...
Excuse me? If a government group is losing it's relevancy, then the group should be DISBANDED, not branched out into new areas.
That's one of the more salient posts I've seen.
on
The Jobs Crunch
·
· Score: 1
However, you should note that the Democrats aren't much different. No, I'm not a Libertarian, but the Dems are pretty much the flip side of the coin to the Reps these days- you almost can't tell who really is who in Washington these days. If you honestly think that the Democrats pandering to corporate interests is really any different from the current batch of Republicans in charge, well, you're fooling yourself.
And, for myself? I've been trying to take what is mine back again for YEARS now.
I knew this was going to happen- whether or not it's true or not matters little, it's going to happen like this or worse at the rate things are going. Time to let the Congresscritters know that if they voted this atrocity in, especially if they didn't read the damn thing and understand what they were voting for, that they're OUT. They knowingly violated their oath of office enacting this law that blatantly violates the Fourth Ammendment.
Slashdot Mirror
The G5 doesn't have that option- it's Big or not at all. Microsoft's going to have to deal with endian-ness and so are vendors who are targeting Windows and X-Box2.
It can be the keys to the kingdom. In the case of WiFi cards, there's less discrete hardware and a hell of a lot more software in the form of DSP code. Most of the modern WiFi cards happen to be software radios and you can exceed power limitations, recode the thing to broadcast on bands that aren't allowed, etc.
In the case of DSL chips, it's the same story.
Endianness and nasty, crufty 32-bit code that makes all kinds of assumptions is the impediment.
If you're using PPC or PPC-64 for the architecture for your console, it's not difficult to migrate the code over
As for API's, I do this sort of thing all the time- you really, really don't know what you're talking about, so you should keep quiet about it.
The code's typically written to an API with an abstraction layer in most well written games- come up with a different abstraction layer and you have the game running on a different API. How in the hell do you think the MacOS and Linux games that DO get ported happen? It's not as you say, no matter what you might think.
Stop and think for a long moment...
DirectX compatibility is only needed if you're simply recompiling for a new target. Most games abstract out the DirectX layer for their engine so they're not dealing with it directly (You'd be stupid to do anything else, really...) therefore it's only a small effort to provide a comparable OpenGL specific layer. Once you've done that, that's one less thing. Typically, most games are using FMOD, Miles, or SDL/OpenAL for their sound. That means the sound is taken care of. It's a minimal effort to make a version of user input code for SDL (your Linux and MacOS X choice...) to replace your DirectInput code. There's several cross-platform choices for network support and while it's an effort to make something work as a replacement for DirectPlay code, it's been done (I know, I've done it myself and helped produce a minimal wrapper layer to allow several pieces of code simply recompile for Linux.) What you speak of simply isn't really much of an impediment for anything except the smallest development studios producing valueware as they're coding strictly to DirectX because it costs them nothing at all.
The biggest impediment for most studios, typically, for going to PPC is that most games make assumptions about the order of bytes, etc. that are far, far removed from best practices. Assumptions that make for difficult migration of code. The same goes for going from 32 to 64 bits- many developers do things like assume pointers are the same size as ints and proceed to interchange them liberally.
If you're making a game for PPC64, those impediments go bye-bye for making a MacOSX game- and since MS is going to probably be suggesting that the games be made available for XP on x86, the code's probably going to be endian neutral as well.
First off, games written for an X=Box or an X=Box2 will NOT be written to bare metal, it'll be written to a variant of XP embedded. That takes your current assumptions of the complexity of dealing with a PCI bus controller, GPU, or DSP and throws it out the window from the top of the Empire State Building.
Unless the game is written an X-Box only game, this means that they're most likely going to be using some abstraction code (and even then...) to make life easier and allow them to target PS2/3 and whatever Nintendo's planning to field. This means you can do the same sorts of things to target Linux/MacOSX- and since it's going to be Endian neutral (it'd have to be, unless MS is going to do something stupid and make the PPC run in little-endian mode (which works, but it's not it's native world...)) it's going to have one of the biggest issues for porting between MacOS X and other OS targets already killed off.
I might suggest some contemplation of your understanding of things and improving upon it considerably before posting on the subject again.
If you go through the motions of doing a Linux port, and you've done it right, you end up with a MacOS X port anyway- just recompile against it and that's pretty much it.
Now, having said this, it's not so much the differences between OSes that's the problem with porting games. Many of the houses are using cross-platform libraries or off-the-shelf engines which support Linux/MacOS X out of the box. It's more of a problem of all the "enhancements" that the studios do the engines and the short-cuts they take in the code that make it a pain. There's quite a few nasty, far from best practices things that VC++ lets you do that causes no end to pain trying to port games over to another platform.
Sadly, most, if not all, of the companies that provide outsourcing services in India and elsewhere tend produce substandard code. Yeah, they code like banshees- but the results are far from optimal. This is from personal experience, working as a contractor within a large multinational corporation.
When the parent's labeled "Insightful"- I was addressing the comment in question.
Moderation's on crack, as usual...
Just because you don't agree with the sentiments, doesn't mean you should moderate "offtopic"- it's a wrong thing to do.
No, but they could look forward to being tortured in prison for the slightest thing or gassed to death with Mustard, Tabun, Sarin, or VX. He did all of those things- it's on record for him as such.
Get the notion that they were better off without the intervention out of your head. Saddam and his cronies were a sadistic bloodthirsty lot themselves, not really any better than the current set of lunatics causing problems over there.
What difference was it that Saddam was in charge (realize that he gassed the religious extemists...) and now it's not Saddam that is in charge- the extremists aren't in charge now either.
So, the parent's post really isn't accurate or insightful no matter HOW you paint it. Neither is yours.
He was not in compliance in any way shape or form with the cease-fire treaty with Gulf War I. The UN acknowleged this. It's part of why they did very little about us doing the Gulf War II incursions.
Oh, and by the way, they DID find that while he didn't have WMDs, he was equipping up to have them within only a couple of months of the lifting of sanctions, etc. He had people burying hot reactor parts in their yards, etc.- they've just began to scratch the surface with this mess. It's not all like you've been led to believe it was, either way.
What the hell is this?
The radical Islamics are the ones killing off the Iraqi National Guard troops in the name of Allah- they just butchered 50 some-odd people in the name of Allah just this last week.
Grow up and find out what is REALLY going on in the world- and it's not all lilly-white pure on our side, but they're not innocents over there that we "oppressed".
When you think about it, "something in place" is not a good excuse for voting for something that is patently in violation of their Oaths of Office (i.e. They swore to uphold the Constitution- voting on something that is concretely in violation of the same is NOT upholding it!). If it was flawed, they should have fixed the damn thing or tabled it permanantly.
I do not accept his rationale on this issue.
What you're doing when you add anti-freeze to a watercooling rig is trying to offset corrosion effects (it's water after all- it's going to have anodic effects on the waterblocks, radiator, etc..) and to prevent mildew and algae buildup in the thing.
This would depend entirely on whether you exceed the heat-pumping capacity of the refrigerator. If you don't exceed the amount being pumped out of the space, it will cool down, the rate being dependent on the rate of thermal transfer above and beyond the heat source's generation of heat.
I've seen active refrigeration systems coupled with water cooling that were based off of mini-fridges (There was one that won a case-mod prize at QuakeCon 2003...). The CPU was cooled down below ambient and he was able to keep Bawls and Cokes cold in the thing.
In actuality, water's a superior refrigerant so long as you're not trying to cool down below freezing and can come up with a compressor with the right volumetric capacity under vacuum. When water boils, it pulls roughly 2700 BTUs out of the surounding environment per liter boiled. At 6 bar, water will readily boil at somewhere around 40deg F, dragging that much heat out of the environment as quickly it can be absorbed by the water under those conditions. The big issue is that it's volumetric rate (how much volume you have to pump out of the low-side of the system...) is roughly double any other possible refrigerants out there. There's currently not that many vacuum pumps that can actually DO this sort of thing and the ones that do are typically rather expensive- so we don't currently use water as a refrigerant.
Now, as to why water's used instead of refrigerants is that it's cheap (An R-134a system would set you back a solid 500 or so, a watercooling rig will set you back only $150-250 and does a better than adequate job (especially if you're looking for normal operation with less noise and less CPU heat...), and it has a heat capacity that makes for a very nice thermal transfer medium. It's why you water cool cars and trucks.
Look on the shelves. There's this little white pill that everybody and his dog made (and still makes)- it's called ASPRIN.
No patents, yet everyone still makes the damn stuff and makes loads of money on it (or else nobody would bother with it...).
Discard your cherished notions of what will/won't be done with or without "IP"- the current notions about it are really, really recent in history. The thinking you espouse is a very nasty double-edged sword. With all this IP "protection", there's no benefit for anyone except the biggest players to make ANYTHING since it's already "Patented", "Copyrighted", or "Trademarked". The biggest players really, really don't have much incentive to make new stuff because it'd take money away from the stuff currently making money and it could temporarily cut off a cash cow (in spite of it maybe making a hell of a lot more money in the long term...).
There was the, "Don't make me turn this car around" feature in the car as well as the "Parent's backhand of death" feature in the car. It more than often was installed in the car by default, even...
:-)
Worked pretty damn well, if you ask me.
You place a call request to one presence server that has a given URI for the person you're wanting to call, including their ID on the server. From there your SIP endpoint software does the rest, including calling landline endpoints.
An example would be:
sip:foo@mysipserver.net
Another would be:
sip:18005551212@mysipserver.net
In the first case, you're calling directly to another SIP endpoint. In the second, you could be calling a SIP endpoint or a PSTN terminated endpoint- the URI wouldn't matter.
Which is something worse than something with fangs.
I'd take something with fangs over that any day...
MacOS X's core is already available as an x86 version. All they'd need to really do, since a very sizeable portion of the Aqua interface system is written in Objective C, would be to account for endianness and call it done. It'd take all of a 6-12 month project, I'd suspect, to put it into an alpha class release stage.
Microsoft, on the other hand, would probably have a nightmare on their hands as I suspect they've not taken any consideration for endianness, 64 bits (No, they still don't have it out in the hands of the public- it's been months now and they knew about amd64, etc. for some time now...)- it's probably all nasty, crufty x86-32 code and using some aborted NT 3.51 code wouldn't help out much...
That's the one I used with my sales revenue from off of eBay...
Excuse me? If a government group is losing it's relevancy, then the group should be DISBANDED , not branched out into new areas.
However, you should note that the Democrats aren't much different. No, I'm not a Libertarian, but the Dems are pretty much the flip side of the coin to the Reps these days- you almost can't tell who really is who in Washington these days. If you honestly think that the Democrats pandering to corporate interests is really any different from the current batch of Republicans in charge, well, you're fooling yourself.
And, for myself? I've been trying to take what is mine back again for YEARS now.
I knew this was going to happen- whether or not it's true or not matters little, it's going to happen like this or worse at the rate things are going. Time to let the Congresscritters know that if they voted this atrocity in, especially if they didn't read the damn thing and understand what they were voting for, that they're OUT. They knowingly violated their oath of office enacting this law that blatantly violates the Fourth Ammendment.