You should only use a development kernel in a production environment if you've already tested it extensively and found it to have no problems with your particular load on your particular hardware with the options you're using. Of course, if you're OSDL, you can actually do this sort of testing, but practically everyone else doesn't have the spare hardware and test suites necessary.
I suspect that this would be really nice for laptops, because the frequencies where you can detect where the sound is coming from come from straight in front of you, not off to the side. Of course, you don't get stereo, but a laptop won't give you sufficient speaker separation to be good anyway. Do the low-frequency stuff from under the keyboard, because it travels well and can't be localized anyway.
OOP is great for some things (and web scripts involve some of them, sometimes), but it's terrible for things organized around the ordered production of output (as well as for new functions on old data types, and a number of other things). Java does well because it's used for cases which aren't the ones where OOP sucks. When Java does web scripts, however, it generally uses JSP, which isn't object-oriented at all (other than calling object-oriented code).
OOP is totally useless for the web script itself, which lacks any logical object to orient your programming around, but it can be nice for the code you're reusing from other scripts, where it involves some data structure (although there are also cases where good procedural discipline, like putting all of the headings and such in procedures that can be replaced easily, is also important). Then you don't have to declare the classes the second time, and you start to save time.
The "Compact Disc" logo doesn't necessarily appear on the back of the jewel case; I generally find it on the upper right (and lower left, upside down) corner of the inside right side (the side with the disc). There's nothing on the back of any of my jewel cases, and there's nothing common among the liner notes.
"enhanced CD" is a method for putting CD-ROM content on the CD along with the CD audio tracks. It only means, in this case, that the encoded songs on the CD-ROM section are stored in the standard way, not that the CD isn't a working audio CD. The RIAA stepped in (a while ago) because Philips didn't have a standard for making something both a CD-ROM and an audio CD. I have a indie "enhanced CD" from 1998 and a Geffen "enhanced CD" from 2002; neither is copy protected (although I've have minor problems with both of them in CD-ROM drives).
Of course, the "enhanced CD" standard may not require that the audio portion comply with the original standard. But the original goal was, in fact, to add other content to compliant audio CDs.
In particular, STSF would have to offer something to application writers in order to justify switching to a new API.
What Sun should be working on is making an implementation of Xft which rendered the text on the server side without requiring any change to applications. This is what STSF should be, and would enable hardware acceleration of font drawing, which is the only advantage (aside from a lot of buzzwords and the letter 'S') that STSF seems to have.
If only there were a function like Xutf8DrawString that would draw a UTF-8 string available if X_HAVE_UTF8_STRING were defined, along with a function like Xutf8TextExtents, and so forth...
Er, right. If only there were a function like XftDrawStringUtf8...
Er, right. Actually, programmers have been working on what you want. The programmers who matter for these purposes haven't been implementing buttons. Of course, the documentation, standardization, and popularization of this work has somewhat lagged, but UTF-8 string rendering has been supported by XFree86 since 4.0.2
If you switch the battery change switch off and on, you'll reboot without clearing the ramdisk, which may or may not be sufficient. Didn't figure this out until I'd hard reset (with the button inside the compartment) several times.
There's something really weird about seeing a machine fscking a ramdisk.
Lots of people have digital cameras with CF storage, which means that the CF slot is, for me, a frequent swap with other people's cards, to get copies of pictures. I actually usually have a wifi card slightly out of the CF slot (to save power when I'm not actually using the network). I think the CF slot works best for swapping things around, whereas the SD card is my more serious storage. On the SD vs MMC front, I'd get MMC if I didn't already have one, because SD requires a close-source driver, which means you can't change the kernel version unless the driver maker happens to produce a new binary for the version you're switching to.
From Sun's side-by-side comparison, it seems like Xft2 is a carefully designed project taking into account the needs of application designers to reach a clearly defined goal, whereas Stsf is has vaguely-defined and excuses its unjustified design with a lot of buzzwords.
Xft2 is slightly inferior in that it doesn't have a way of communicating the data to the server pre-rasterization, so that the server can use hardware acceleration in the rendering process. Of course, there's no particular reason that, once XRENDER is complete, this couldn't be done.
What he said before was that XML processing hasn't been implemented in a way convenient for programmers. He's never had any problem with XML as a standard or data format. His clarification was basically that he only thinks that XML sucks for programming with the current tools, which is what he said before.
I understood most of question 10, but what the heck is "Ubyl pbj!" supposed to mean? It sounds like he was interrupted in the middle of lunch or something.
Reconstructed countries become pacifist. A country has to lose the war, and then feel that it's just as well that they lost.
The US won't learn any more from losing the present war (if it does) than it learned from Korea or Vietnam, both of which it lost at a great cost. If the US were driven back and the UN came in and fixed up the situation, removing Saddam and his regime, and setting up, with arab support and assistance, a state that all the Iraqi peoples could agree on, the US might learn something.
Staying neutral is a fine idea in this war. The US, unfortunately, has never been neutral towards Iraq, and trying to become neutral is a bad idea. It's not like Saddam is likely to attack France or Germany.
It's certainly one way to stop companies from copyrighting their works. I bet if the US Government got royalties on any works whose copyrights expired, they couldn't be induced to extend the terms any more, and Disney wouldn't be so happy about eventually losing the free use of their characters...
Copyright is currently good for corporations. If it were changed to be bad for corporations, that would go a long way toward reforming it, or at least reducing its effect.
Re:ABC cuts gore from injured child's Iraq war pho
on
4l-j4z333ra 0wn3d
·
· Score: 1
War doesn't solve anything; it just changes the problems, sometimes into ones that could be solved. WWII stopped the Nazis, but it started the cold war, which led to Korea and Vietnam, neither of which are entirely sorted out yet, and Saddam, bin Laden, and other US and USSR-installed dictatorships, which brings us to the present conflict.
The only thing that solves problems is people settling their differences and deciding it's not worth fighting. That's not to say that war is useless; some regimes cannot be stopped peacefully (particularly ones bent on defeating the whole world) and the problems war creates may not be as bad or as pressing as the ones they replace. But it's generally the period of reconstruction after the war that solves problems, not the war itself.
"The buttons on the Gameboy are easily accessible in the heat of the moment."
That's a feature that the G3 really needs, although I somehow suspect that this reviewer didn't test it. If he had, the replay value of the G3 might also have gotten a better score...
Hmm... makes you wonder about the dark blue patch in the middle east that doesn't correspond to another patch 180 degrees east like the rest of the patches...
They should probably put warnings all over the builds, if for no other reason than that the testers are probably using a stable version of the same software, and could easily get confused between the version that works and the largely identical version they're testing and have it crash when they were trying to do something with it.
Of course, to have people complain about bugs is why you produce test builds anyway. You just have to direct people to the bug reporting section, rather than the support section (since the obvious support response is, "run a different version").
The text genre hasn't really acquired the technical capabilities that modern computers could support. There are a number of good possiblities for advances which haven't really been done. For example: the parser ought to have some idea of what the text says, rather than only having any idea about the user's input ("Susan walks into the room." "Greet her"); the library should do a lot more in the way of generating text, automatically using pronouns as appropriate, combining messages, and so forth; the game should keep track of player knowledge and provide it on request for players who take a year to finish a game. Sure, you don't need a special text card or anything, but there are things you could do now that you couldn't do in the Infocom days, and these are largely not done.
I mean, it used to be that if you wrote a pornographic text adventure set in classical Rome based on the life of Catullus with all of the text in hendecasyllabic latin verse, nobody would have the processor power to run it. Now, you'd just have to be nuts to actually try it.
Actual Infocom-style text-based single-player games are certainly not dying. They fell out of wide popularity a decade ago, and are actually now more popular than they've been since then. Of course, they're pretty much dead as a commercial prospect, mainly because they have too small an audience to attract commercial interests and advertizing, and the people who do make them aren't interested in making a commercial venture out of it.
If Windows 95 went public, it could be supported by other people, and MicroSoft would have even more trouble getting people to upgrade than they do now. Considering that MicroSoft's biggest competition these days is MicroSoft from the past, it's greatly in their interests to make their old software as dead as possible.
But why would Apple be liable (even from a PR standpoint) for problems with a beta leaked by somebody else? If it's being distributed by somebody else, the problems you have with it could just as easily come from the intermediary rather than Apple. It makes sense for them to limit who they actually give the software directly to, but they shouldn't care who ends up with what purports to be an unreleased version, whether or not it matches an intermediate Apple code base.
So far as I know, the only driver for SD cards is closed-source and only available for 2.4.8; does anyone know if the 5600 supports them, or just the MMC version?
Slashdot Mirror
Fortunately for you, there isn't any legitimate news today, so having this story posted five times isn't holding you back from any.
You should only use a development kernel in a production environment if you've already tested it extensively and found it to have no problems with your particular load on your particular hardware with the options you're using. Of course, if you're OSDL, you can actually do this sort of testing, but practically everyone else doesn't have the spare hardware and test suites necessary.
I suspect that this would be really nice for laptops, because the frequencies where you can detect where the sound is coming from come from straight in front of you, not off to the side. Of course, you don't get stereo, but a laptop won't give you sufficient speaker separation to be good anyway. Do the low-frequency stuff from under the keyboard, because it travels well and can't be localized anyway.
Put the woofer in your chair, so you can get the effect of your whole body shaking without disturbing the neighbors nearly so much...
OOP is great for some things (and web scripts involve some of them, sometimes), but it's terrible for things organized around the ordered production of output (as well as for new functions on old data types, and a number of other things). Java does well because it's used for cases which aren't the ones where OOP sucks. When Java does web scripts, however, it generally uses JSP, which isn't object-oriented at all (other than calling object-oriented code).
OOP is totally useless for the web script itself, which lacks any logical object to orient your programming around, but it can be nice for the code you're reusing from other scripts, where it involves some data structure (although there are also cases where good procedural discipline, like putting all of the headings and such in procedures that can be replaced easily, is also important). Then you don't have to declare the classes the second time, and you start to save time.
The "Compact Disc" logo doesn't necessarily appear on the back of the jewel case; I generally find it on the upper right (and lower left, upside down) corner of the inside right side (the side with the disc). There's nothing on the back of any of my jewel cases, and there's nothing common among the liner notes.
"enhanced CD" is a method for putting CD-ROM content on the CD along with the CD audio tracks. It only means, in this case, that the encoded songs on the CD-ROM section are stored in the standard way, not that the CD isn't a working audio CD. The RIAA stepped in (a while ago) because Philips didn't have a standard for making something both a CD-ROM and an audio CD. I have a indie "enhanced CD" from 1998 and a Geffen "enhanced CD" from 2002; neither is copy protected (although I've have minor problems with both of them in CD-ROM drives).
Of course, the "enhanced CD" standard may not require that the audio portion comply with the original standard. But the original goal was, in fact, to add other content to compliant audio CDs.
In particular, STSF would have to offer something to application writers in order to justify switching to a new API.
What Sun should be working on is making an implementation of Xft which rendered the text on the server side without requiring any change to applications. This is what STSF should be, and would enable hardware acceleration of font drawing, which is the only advantage (aside from a lot of buzzwords and the letter 'S') that STSF seems to have.
If only there were a function like Xutf8DrawString that would draw a UTF-8 string available if X_HAVE_UTF8_STRING were defined, along with a function like Xutf8TextExtents, and so forth...
Er, right. If only there were a function like XftDrawStringUtf8...
Er, right. Actually, programmers have been working on what you want. The programmers who matter for these purposes haven't been implementing buttons. Of course, the documentation, standardization, and popularization of this work has somewhat lagged, but UTF-8 string rendering has been supported by XFree86 since 4.0.2
Dang, this guy is tricky. I have to not only be able to read ROT-13, I have to be able to read plain text?
If you switch the battery change switch off and on, you'll reboot without clearing the ramdisk, which may or may not be sufficient. Didn't figure this out until I'd hard reset (with the button inside the compartment) several times.
There's something really weird about seeing a machine fscking a ramdisk.
Lots of people have digital cameras with CF storage, which means that the CF slot is, for me, a frequent swap with other people's cards, to get copies of pictures. I actually usually have a wifi card slightly out of the CF slot (to save power when I'm not actually using the network). I think the CF slot works best for swapping things around, whereas the SD card is my more serious storage. On the SD vs MMC front, I'd get MMC if I didn't already have one, because SD requires a close-source driver, which means you can't change the kernel version unless the driver maker happens to produce a new binary for the version you're switching to.
From Sun's side-by-side comparison, it seems like Xft2 is a carefully designed project taking into account the needs of application designers to reach a clearly defined goal, whereas Stsf is has vaguely-defined and excuses its unjustified design with a lot of buzzwords.
Xft2 is slightly inferior in that it doesn't have a way of communicating the data to the server pre-rasterization, so that the server can use hardware acceleration in the rendering process. Of course, there's no particular reason that, once XRENDER is complete, this couldn't be done.
What he said before was that XML processing hasn't been implemented in a way convenient for programmers. He's never had any problem with XML as a standard or data format. His clarification was basically that he only thinks that XML sucks for programming with the current tools, which is what he said before.
I understood most of question 10, but what the heck is "Ubyl pbj!" supposed to mean? It sounds like he was interrupted in the middle of lunch or something.
Reconstructed countries become pacifist. A country has to lose the war, and then feel that it's just as well that they lost.
The US won't learn any more from losing the present war (if it does) than it learned from Korea or Vietnam, both of which it lost at a great cost. If the US were driven back and the UN came in and fixed up the situation, removing Saddam and his regime, and setting up, with arab support and assistance, a state that all the Iraqi peoples could agree on, the US might learn something.
Staying neutral is a fine idea in this war. The US, unfortunately, has never been neutral towards Iraq, and trying to become neutral is a bad idea. It's not like Saddam is likely to attack France or Germany.
It's certainly one way to stop companies from copyrighting their works. I bet if the US Government got royalties on any works whose copyrights expired, they couldn't be induced to extend the terms any more, and Disney wouldn't be so happy about eventually losing the free use of their characters...
Copyright is currently good for corporations. If it were changed to be bad for corporations, that would go a long way toward reforming it, or at least reducing its effect.
War doesn't solve anything; it just changes the problems, sometimes into ones that could be solved. WWII stopped the Nazis, but it started the cold war, which led to Korea and Vietnam, neither of which are entirely sorted out yet, and Saddam, bin Laden, and other US and USSR-installed dictatorships, which brings us to the present conflict.
The only thing that solves problems is people settling their differences and deciding it's not worth fighting. That's not to say that war is useless; some regimes cannot be stopped peacefully (particularly ones bent on defeating the whole world) and the problems war creates may not be as bad or as pressing as the ones they replace. But it's generally the period of reconstruction after the war that solves problems, not the war itself.
"The buttons on the Gameboy are easily accessible in the heat of the moment."
That's a feature that the G3 really needs, although I somehow suspect that this reviewer didn't test it. If he had, the replay value of the G3 might also have gotten a better score...
Hmm... makes you wonder about the dark blue patch in the middle east that doesn't correspond to another patch 180 degrees east like the rest of the patches...
They should probably put warnings all over the builds, if for no other reason than that the testers are probably using a stable version of the same software, and could easily get confused between the version that works and the largely identical version they're testing and have it crash when they were trying to do something with it.
Of course, to have people complain about bugs is why you produce test builds anyway. You just have to direct people to the bug reporting section, rather than the support section (since the obvious support response is, "run a different version").
The text genre hasn't really acquired the technical capabilities that modern computers could support. There are a number of good possiblities for advances which haven't really been done. For example: the parser ought to have some idea of what the text says, rather than only having any idea about the user's input ("Susan walks into the room." "Greet her"); the library should do a lot more in the way of generating text, automatically using pronouns as appropriate, combining messages, and so forth; the game should keep track of player knowledge and provide it on request for players who take a year to finish a game. Sure, you don't need a special text card or anything, but there are things you could do now that you couldn't do in the Infocom days, and these are largely not done.
I mean, it used to be that if you wrote a pornographic text adventure set in classical Rome based on the life of Catullus with all of the text in hendecasyllabic latin verse, nobody would have the processor power to run it. Now, you'd just have to be nuts to actually try it.
Actual Infocom-style text-based single-player games are certainly not dying. They fell out of wide popularity a decade ago, and are actually now more popular than they've been since then. Of course, they're pretty much dead as a commercial prospect, mainly because they have too small an audience to attract commercial interests and advertizing, and the people who do make them aren't interested in making a commercial venture out of it.
If Windows 95 went public, it could be supported by other people, and MicroSoft would have even more trouble getting people to upgrade than they do now. Considering that MicroSoft's biggest competition these days is MicroSoft from the past, it's greatly in their interests to make their old software as dead as possible.
But why would Apple be liable (even from a PR standpoint) for problems with a beta leaked by somebody else? If it's being distributed by somebody else, the problems you have with it could just as easily come from the intermediary rather than Apple. It makes sense for them to limit who they actually give the software directly to, but they shouldn't care who ends up with what purports to be an unreleased version, whether or not it matches an intermediate Apple code base.
So far as I know, the only driver for SD cards is closed-source and only available for 2.4.8; does anyone know if the 5600 supports them, or just the MMC version?