So if programmers don't need to know assembler any more what does this tell us? C's abstractions are not significantly leaky....
No, -one- programmer doesn't need to know assembly. C's abstractions aren't leaky for him and his normal range of problems.
Have you ever had a stack overflow, say? Ever had to use volatile variables? Been bit in the ass by an optimizing compiler? Tried to write cache/MMU/device driver/context switch code exclusviely in C?
-I- still have to turn off optimization regularly when I'm writing a device driver.
The guy down the hall knows that C would roll over and start crying if he tried to write his perfectly reasonable cache management code in it.
I'd eat my shoes if we could write our OS in OCaml. You might be able to get away with using it, he might be able to get away with using it, but some areas will always have trouble with the leaks of any abstraction. That's the point.
I think the key is to make it clear to your current employers that you'd prefer to stay, but don't see how it is financially viable. I suppose it depends on your relationship with your boss, but I didn't have any trouble.
It might have helped that I told my boss I thought I was being underpaid at my previous review (and got a significant raise then.)
I may have had a particularly understanding boss and VP who I had a good relationship with. But, I think if you make it clear to them that you know you're being underpaid, and prove it to them, they'll accept it without holding a grudge.
Actually, I've done a few months of fencing (SCA style, where you can use your hands and circle, not modern where you are highly constrained) and fought with people both 6" shorter and taller than me, and with +/-6" of reach.
Reach is certainly an advantage, but it can be overcome with parries, feints and proper distance closing. Obviously, one side or the other needs to close, but Yoda should have been able to hold up calmly inside of Dooku's reach.
Certainly one thing you don't do when you're at a reach disadvantage is turn your back on your opponent by, let's say, spinning in a circle. This reduces your reach to approximately nil, and is an important part of why I didn't like the spinning in this scene. For at least 1/3 of any spin, you have -no- reach and -no- ability to parry.
I'm still annoyed at the Yoda fight scene, and I think the animators were right.
Yes, having Yoda kick ass was cool. But he didn't have to do it by spinning around at 3600RPM.
Yoda is supposed to be relaxed and smug. He should have overwhelmed Dooku with -skill- instead of just being four times faster, with no moment of inertia. That scene would have been twice as good if the big Y had stayed upright, and parried and feinted like a madman. No need for backflips.
Does communism work (circa 1906)? Is it worth getting in a fight over Archduke Ferdinand (circa 1914)? Will the world be better if I kill Hitler (circa 1935)? Will the allies win (circa 1939)? Should we commit to Vietnam (circa 1967)? Should I invest in Microsoft (circa 1985)? Should we fight the hijackers (circa 2001)?
Your calculations make no sense. Where did you get 2v/d from? How did the atomic radius enter into the picture at all? That calculation clearly involves a -lot- of assumptions, most of which I doubt you know/remember, and are not applicable to the situation you describe.
If I have a machine with 100 atoms, and propel it by ejecting a single atom at velocity V, the machine will be moving at ~V/100 in the opposite direction.
This is ignoring the numerous other methods for propelling an object, without ejecting a propellant. Various forms of electromagnetic fields do a damn good job.
It's a DBase file, with a user name and password. The data in the file has been encrypted based on this user name/password.
I don't know much about DBase security. I suppose it's possible the data hasn't been encrypted, but DBase won't let you access it. In which case an analogous solution would work: knowing the DBase format, write a program to open the file, ignore the password info, and save it out to a new user/add another user to the list/stream the data out. But I doubt DBase is that unsecure.
> Careful buddy, you gotta make sure she has the > upper hand: when the DEA [thedeasucks.com] finds > out about her love drug operation and busts in > to her dorm (breaking and entering, assault with > a deadly weapon, home invasion,...) and siezes > her MDMA and any liquid assets (theft...), and > throws her in prison (kidnapping...) make sure > she can properly defend herself. I would > recommend a few.50 caliber machine guns > mounted on turrets near her dorm, an RPG, > plenty of Kevlar and a few sets of night > goggles. Well, sure, an RPG goes without saying. The $64,000 question is: which one. You don't want her turning into some D&D monkey, but if you're not careful, she ends up playing fricking Wraith.
> Why cant we just use higher and higer frequencies? 2GHz full? Use 20GHz? Or 50GHz? Or a googlehertz?
Because, the higher the frequency, the shorter the wavelength.
And the shorter the wavelength, the less "penetrating power" the signal has, and the more the signal is absorbed by intervening walls/clouds/.../and eventually air.
In short, 100Ghz signals can't even make it across a room without getting in trouble.
The reviewer did a pretty good job of presenting balanced review, I think.
And the parent poster was beginning the predicted discussion (crank/genius.) He wasn't saying anything about the review, or the reviewer, jsut giving his opinion on the topic, and addressing a few off the possible counter-arguments (the appeal-to-authority type arguments.)
Slashdot Mirror
So if programmers don't need to know assembler any more what does this tell us? C's abstractions are not significantly leaky. ...
No, -one- programmer doesn't need to know assembly. C's abstractions aren't leaky for him and his normal range of problems.
Have you ever had a stack overflow, say?
Ever had to use volatile variables?
Been bit in the ass by an optimizing compiler?
Tried to write cache/MMU/device driver/context switch code exclusviely in C?
-I- still have to turn off optimization regularly when I'm writing a device driver.
The guy down the hall knows that C would roll over and start crying if he tried to write his perfectly reasonable cache management code in it.
I'd eat my shoes if we could write our OS in OCaml. You might be able to get away with using it, he might be able to get away with using it, but some areas will always have trouble with the leaks of any abstraction. That's the point.
I think the key is to make it clear to your current employers that you'd prefer to stay, but don't see how it is financially viable. I suppose it depends on your relationship with your boss, but I didn't have any trouble.
It might have helped that I told my boss I thought I was being underpaid at my previous review (and got a significant raise then.)
I may have had a particularly understanding boss and VP who I had a good relationship with. But, I think if you make it clear to them that you know you're being underpaid, and prove it to them, they'll accept it without holding a grudge.
Actually, I've done a few months of fencing (SCA style, where you can use your hands and circle, not modern where you are highly constrained) and fought with people both 6" shorter and taller than me, and with +/-6" of reach.
Reach is certainly an advantage, but it can be overcome with parries, feints and proper distance closing. Obviously, one side or the other needs to close, but Yoda should have been able to hold up calmly inside of Dooku's reach.
Certainly one thing you don't do when you're at a reach disadvantage is turn your back on your opponent by, let's say, spinning in a circle. This reduces your reach to approximately nil, and is an important part of why I didn't like the spinning in this scene. For at least 1/3 of any spin, you have -no- reach and -no- ability to parry.
I'm still annoyed at the Yoda fight scene, and I think the animators were right.
Yes, having Yoda kick ass was cool.
But he didn't have to do it by spinning around at 3600RPM.
Yoda is supposed to be relaxed and smug. He should have overwhelmed Dooku with -skill- instead of just being four times faster, with no moment of inertia. That scene would have been twice as good if the big Y had stayed upright, and parried and feinted like a madman. No need for backflips.
Pick six: six bytes.
$60 million say.
$10 million/byte isn't to shabby.
To answer such valuable yes/no questions as:
Does communism work (circa 1906)?
Is it worth getting in a fight over Archduke Ferdinand (circa 1914)?
Will the world be better if I kill Hitler (circa 1935)?
Will the allies win (circa 1939)?
Should we commit to Vietnam (circa 1967)?
Should I invest in Microsoft (circa 1985)?
Should we fight the hijackers (circa 2001)?
Huh?
Your calculations make no sense. Where did you get 2v/d from? How did the atomic radius enter into the picture at all?
That calculation clearly involves a -lot- of assumptions, most of which I doubt you know/remember, and are not applicable to the situation you describe.
If I have a machine with 100 atoms, and propel it by ejecting a single atom at velocity V, the machine will be moving at ~V/100 in the opposite direction.
This is ignoring the numerous other methods for propelling an object, without ejecting a propellant. Various forms of electromagnetic fields do a damn good job.
Because it's not an OS password.
It's a DBase file, with a user name and password. The data in the file has been encrypted based on this user name/password.
I don't know much about DBase security. I suppose it's possible the data hasn't been encrypted, but DBase won't let you access it. In which case an analogous solution would work: knowing the DBase format, write a program to open the file, ignore the password info, and save it out to a new user/add another user to the list/stream the data out. But I doubt DBase is that unsecure.
> Careful buddy, you gotta make sure she has the .50 caliber machine guns
> upper hand: when the DEA [thedeasucks.com] finds
> out about her love drug operation and busts in
> to her dorm (breaking and entering, assault with
> a deadly weapon, home invasion,...) and siezes
> her MDMA and any liquid assets (theft...), and
> throws her in prison (kidnapping...) make sure
> she can properly defend herself. I would
> recommend a few
> mounted on turrets near her dorm, an RPG,
> plenty of Kevlar and a few sets of night
> goggles.
Well, sure, an RPG goes without saying. The $64,000 question is: which one. You don't want her turning into some D&D monkey, but if you're not careful, she ends up playing fricking Wraith.
> Why cant we just use higher and higer frequencies? 2GHz full? Use 20GHz? Or 50GHz? Or a googlehertz?
Because, the higher the frequency, the shorter the wavelength.
And the shorter the wavelength, the less "penetrating power" the signal has, and the more the signal is absorbed by intervening walls/clouds/.../and eventually air.
In short, 100Ghz signals can't even make it across a room without getting in trouble.
The reviewer did a pretty good job of presenting balanced review, I think.
And the parent poster was beginning the predicted discussion (crank/genius.) He wasn't saying anything about the review, or the reviewer, jsut giving his opinion on the topic, and addressing a few off the possible counter-arguments (the appeal-to-authority type arguments.)
Don't install/uninstall AdAware.
Put some valuable piece of software in the AdAware default install directory.
Install RadLight.
Sue them for destroying your valuable property.