Lawyers? Well, lawyers are evil. Evil right down to their cold, black hearts which pump not blood, like yours or mine, but rather a thick, vomitous oil that oozes through their rotten veins and clots in their pea-sized brains, becoming the cause of their Nazi-esque patterns of violent behaviour.
Do you understand?
Good. Now go inside and make software like a good little codemonkey. </MrGarrison>
I remember reading an article last year (in the New Scientist, i think) about how relatively easy it would be to build an EMP bomb within something roughtly the same size and shape as a pipe bomb.
Taking out inadequately shielded stock exchanges, major database centres, backup facilities, etc, would have frightening consequences.
In the old days with 128-byte CMOS's, there were settings and bytes that weren't standard across different makes and models of motherboards anyway. I don't see what this has to do with recent boards requiring more CMOS settings/memory whatever.
And most people just use the default CMOS settings anyway, apart from maybe configuring the hard drives.
You can bet that countries like Japan and Korea have gadgets which perform similar functions. They've got so many things we've never even heard of this side of the world - which is one of the reasons I intend to move there!
Problem is you probably won't turn up much online since the web pages and such will be in local languages.
I'd like to hear what information anybody has who's been living in those parts for a while.
One of the things I hate most is apps and web pages which screw up when running on a machine with a non-default colour scheme.
I like my white-on-black colour scheme very much, thanks. Why do certain apps/web pages find it neccessary to set a foreground colour to black, but then leave the background colour alone? Great, now the only way for me to read that is to highlight the text or change my scheme back.
Moral of the story: Either set BOTH foreground and background colours to what you want (and for goodness sake, make it user-configurable), or LEAVE THE COLOURS ALONE.
'Nie has his own list of applications for such bioelectronic devices, such as tissue engineering and sound and light censors, which "either enhance the body's function or act as a probe that lets you observe the body's function," he said.'
Sound and light "censors" argh! That's audio and video conquered in one fell swoop. Soon it'll be pay-per-view just to drive to work...
Well said. I was just trying to think of a hyperthetical example like that. It's true - if the boot was on the other foot, guess who would've got their way. Dmitri is a good example right now, and that situation's because of some big corporate, not even something concerning national interest!
Actually, don't be so sure of yourself. The author changed the article after realising his error - what you see in my post was the original, duplicated with nice, healthy cut and paste. Don't call me an idiot just because you're slow on the trigger.
What are you talking about? The purpose of the author's example was to store the result in C as opposed to overwriting A. Or maybe you just made a joke I didn't get.
We're still thinking according to the Pentium I mindset. Stalls like that one aren't really an issue anymore thanks to the out-of-order instruction execution scheme that has been evolving since the P-II.
--
SIMD, standing for "Single Instruction, Multiple Data" (ph34r my acronym skillz), has been around on x86 CPU's since the PI-166Mhz MMX, for the record. It should also be noted that there were clever ways to do simple SIMD-like operations using the standard registers and instructions.
--
The first command adds the two numbers, and the second command moves the result from A to C. Of course, you still have the potential problem that the original value of A was erased by the add command, so if you wanted preserve A's value then you'd have to insert even more instructions to store A in a temporary register and then restore its value once the addition has been performed.
----snip----
Not quite. I'm sure even people who _dont_ know x86 assembly language will realise all you don't need any extra instructions at all. Simply reorder them:
mov C, A
add C, B
Obviously, the example was being used to show how much nicer it would be to have three or more operands in your instructions, but it was a lousy example.
On a sidenote, we've been able to specify more than two operands with certain instructions since the 80386. Look up the syntax for the "imul" instruction.
Slashdot Mirror
Lightbulbs- NO. You GOTTA be joking here. Thomas Edison was NOT British...
Erm, Nikola Tesla actually. Although he was Serbian. Edison funded research and marketted the suckers.
Lawyers? Well, lawyers are evil. Evil right down to their cold, black hearts which pump not blood, like yours or mine, but rather a thick, vomitous oil that oozes through their rotten veins and clots in their pea-sized brains, becoming the cause of their Nazi-esque patterns of violent behaviour.
Do you understand?
Good. Now go inside and make software like a good little codemonkey.
</MrGarrison>
The Canadian one, perhaps?
How did you go on for so long without good quality 'net prØn?
I remember reading an article last year (in the New Scientist, i think) about how relatively easy it would be to build an EMP bomb within something roughtly the same size and shape as a pipe bomb.
Taking out inadequately shielded stock exchanges, major database centres, backup facilities, etc, would have frightening consequences.
$0.02
Indeed :^)
In the old days with 128-byte CMOS's, there were settings and bytes that weren't standard across different makes and models of motherboards anyway. I don't see what this has to do with recent boards requiring more CMOS settings/memory whatever.
And most people just use the default CMOS settings anyway, apart from maybe configuring the hard drives.
I really don't get this question.
Sex. It's a team sport too :) I even know some geeks who engage in this activity regularly.
You can bet that countries like Japan and Korea have gadgets which perform similar functions. They've got so many things we've never even heard of this side of the world - which is one of the reasons I intend to move there!
Problem is you probably won't turn up much online since the web pages and such will be in local languages.
I'd like to hear what information anybody has who's been living in those parts for a while.
Expect a whole new onslaught of X10 ads as soon as this technology becomes popular :(
"We must destroy X10! We must destroy all Internet ad!" - KOMPRESSOR
I'm sure it does. As you say, it's by example.
I, too, am interested to see what the general public's take on this subject is.
a nice start.
sounds a lot like a certain stimulant a few friends of mine were using this weekend.
--------
:)
And also, never hard-code the colors for window/dialog backgrounds, fonts
--------
Damn, beat me to it!
One of the things I hate most is apps and web pages which screw up when running on a machine with a non-default colour scheme.
I like my white-on-black colour scheme very much, thanks. Why do certain apps/web pages find it neccessary to set a foreground colour to black, but then leave the background colour alone? Great, now the only way for me to read that is to highlight the text or change my scheme back.
Moral of the story: Either set BOTH foreground and background colours to what you want (and for goodness sake, make it user-configurable), or LEAVE THE COLOURS ALONE.
I'm going to stay at my console and get pissed while making a fool of myself on IRC. It's sad, but true :)
23:59:50 on the pictures.
'Nie has his own list of applications for such bioelectronic devices, such as tissue engineering and sound and light censors, which "either enhance the body's function or act as a probe that lets you observe the body's function," he said.'
Sound and light "censors" argh! That's audio and video conquered in one fell swoop. Soon it'll be pay-per-view just to drive to work...
Well said. I was just trying to think of a hyperthetical example like that. It's true - if the boot was on the other foot, guess who would've got their way. Dmitri is a good example right now, and that situation's because of some big corporate, not even something concerning national interest!
No big surprise I guess.
Actually, don't be so sure of yourself. The author changed the article after realising his error - what you see in my post was the original, duplicated with nice, healthy cut and paste. Don't call me an idiot just because you're slow on the trigger.
What are you talking about? The purpose of the author's example was to store the result in C as opposed to overwriting A. Or maybe you just made a joke I didn't get.
Good call dude :) I wondered whether it was worth getting into detail like that, but you put it across nicely. Like I said, the example used was lousy.
And I agree - the article basically sucked.
PS: moderators - the above should be marked "Insightful". He makes a good point.
We're still thinking according to the Pentium I mindset. Stalls like that one aren't really an issue anymore thanks to the out-of-order instruction execution scheme that has been evolving since the P-II.
--
It was going to create a stall _anyway_, and it was already two instructions _anyway_. The point is, you don't need any extra instructions....
--
SIMD, standing for "Single Instruction, Multiple Data" (ph34r my acronym skillz), has been around on x86 CPU's since the PI-166Mhz MMX, for the record. It should also be noted that there were clever ways to do simple SIMD-like operations using the standard registers and instructions.
--
----snip----
add A, B
mov C, A
The first command adds the two numbers, and the second command moves the result from A to C. Of course, you still have the potential problem that the original value of A was erased by the add command, so if you wanted preserve A's value then you'd have to insert even more instructions to store A in a temporary register and then restore its value once the addition has been performed.
----snip----
Not quite. I'm sure even people who _dont_ know x86 assembly language will realise all you don't need any extra instructions at all. Simply reorder them:
mov C, A
add C, B
Obviously, the example was being used to show how much nicer it would be to have three or more operands in your instructions, but it was a lousy example.
On a sidenote, we've been able to specify more than two operands with certain instructions since the 80386. Look up the syntax for the "imul" instruction.