Reading more about writing code than actually writing code would imply very little coding experience, or a vast desire for redundancy, or a career in software engineering research.
Whoever made the movies would still need to license the character, because Spider-Man is a trademark of Marvel's. Copyright expiration just means people can make reprints of the old comics.
What I'd like to know is how BD+ stops someone from making bit image dupes of a Bluray disc, mass producing them by the millions and selling them on street corners in cheap boxes for $5.
Oh, what, the goal of DRM isn't to stop such blatant profit motivated piracy? They're going after people who actually lose money by paying for their own bandwidth and storage to share files? I... I... I... don't get it!
Hmmm... I've got Linux on four machines at home (Ubuntu and RedHat 7.x), but one dual-boots WinXP. Then there's my wife's two Macs that run OSX. And then there's her Win2K work laptop that she uses to connect to Solaris machines at work. And then there's my WinXP work laptop that I use to connect to Linux boxes (RHEL) at work.
So I guess count us as users of pretty much everything?
20€ is more like $27 USD right now. The exchange rate is bad, but it isn't THAT bad. Also, the price in Euros probably includes VAT, unlike prices here. VAT ranges from 15% to 25%, so a 20€ mouse there probably compares to a $20 mouse here. That sounds pretty reasonable for a retail optical mouse.
Might I suggest that the engineers may have insisted very thoroughly to others that they were designing for 90 days, but really they were designing for much longer. Might I suggest this essay: Exaggerate with Extreme Prejudice.
It's called derating. I'm sure the Mars rovers were designed to last far, far longer than 90 days. They just set the "success" threshold very low given all the unknowns of the trip.
I agree for the bulk of code. If you have something tabular with many columns, you can go wider than 80 pretty quick, but not lose comprehension, mainly because each column is much narrower than 80 and that's the unit of importance: column width.
To stay in the 80-column limit for tables requires lots of abbreviations, which works against comprehension. I have some tables I wrote in here and here and here that *just* fit in 80, and really wanted to be wider.
At least the commit log should tell you WHO likes it that way. Armed with that, you know where to send Guido and his lead pipe to teach the culprit some lessons in taste.;-)
That said, there are times I have something tabular that really begs for something wider than 80 columns. I can totally see that, but I consider such tables to be a special case.
I agree with tabbing, although 8-character tab stops are too much, and 2-character is too little. 4 seems just right. StupidLongAndBoringSquishCapsNames can die though.
Whatever happened to concise acronyms and abbreviations? Sure, the very first time you see a name, you might want it spelled out. But once you've internalized it, having to distinguish between LongAndBoringIndexVariableName and LongAndBoringArrayVariableName gets pretty tiring.
I'm quite happy with 80 columns, 4-character indentations, tabs expanded to spaces, and fixed width fonts for my code. So far fancy GUIs do nothing but get in my way. I'll stick with VIM and xterm.:-)
Seems like a simple regular expression to break it into multiple lines is in order, followed by some joins to make it into a nice 25 - 35 line block. Trivial in a modern editor.;-)
I agree to a fair extent. I imagine if temperature compensation equipment went into play, all we'd see is even higher posted gas prices in the summer, actually. We'd still end up spending about the same amount of money, though.
See, there's supply, and there's demand. If the below-ground tanks are above nominal temperature at all, then that artifically increases supply, and automatically puts a downward pressure on price. Conversely, summer sees an increase in travel because the weather's nice, the kids are out of school, and so on. This puts an upward pressure on price.
Because of this expansion, the amount you're getting charged per BTU goes up more than the amount you're getting charged per gallon. My hypothesis is that since the demand for BTUs is what went up, but you're actually buying fewer BTUs of gasoline per measured gallon, the offered price per measured gallon doesn't go up as far as it otherwise would if gasoline stayed at a constant temperature year-round.
If you started charging people based on temperature-compensated gallons instead of measured gallons (so, for instance, 1 measured gallon might equal 0.95 compensated gallons when it's hot out), the "price/gallon" will go up, if only because now the price reflects price per BTU. There won't be this persistent blunting effect on the upward gasoline price pressure.
In other words, this is too big of a market for the effect to have not already been priced in. And yes, it probably is the local gas station that's getting the short end of the stick here, if anyone, although I imagine the attached Quicky-Marts help act as a counter balance, since summer travel season == families with kids buying snacks. The actual below-ground temperaturs for the tanks doesn't really shift much (take a look here for one example), so it's really gasoline being sold from above ground that sucks. (Think fuel delivery truck.)
If nothing else, I'll skip a gas station from now on if I see it has just gotten a fuel delivery in the summer. The rest of the time? It should be fine.
That's only true if you audit the entire Blackberry software stack for side-channel information leaks at the machine code level. I refer you to Ken Thompson's classic, Reflections on Trusting Trust. I've actually worked with a vendor that has tools for embedding special kinds of sentinels in object code, taking an even more direct and undetectable route than Ken did.
I wasn't quite so fancy, being a poor high school kid at the time, using the school's computers during my lunch break or after school. But, I did manage (with documentation I nabbed from a Beagle Bros cheat sheet I think) to make "password protected" disks. You'd boot them and all you'd see is the password program. Run that, and if you got the password right it would "unlock" the disk. All it was really doing was changing the DOS 3.3 directory start from sector 1 to sector 2 or some such.:-) (Track 11 for the win!) And, by then, I was actually using ProtoDOS for my DOS 3.3 needs.
Ah, memories. 6502 was the second assembly language I learned. TMS9900 was the first.
Slashdot Mirror
W's smarter than he looks. He's been continually misunderestimated.
Reading more about writing code than actually writing code would imply very little coding experience, or a vast desire for redundancy, or a career in software engineering research.
Whoever made the movies would still need to license the character, because Spider-Man is a trademark of Marvel's. Copyright expiration just means people can make reprints of the old comics.
--JoeWhy? Did the tapes go bad? Did the VCR die?
It worked for W.
What I'd like to know is how BD+ stops someone from making bit image dupes of a Bluray disc, mass producing them by the millions and selling them on street corners in cheap boxes for $5.
Oh, what, the goal of DRM isn't to stop such blatant profit motivated piracy? They're going after people who actually lose money by paying for their own bandwidth and storage to share files? I... I... I... don't get it!
--Joe
Not who I had in mind, but I'm sure he'd be horrified also.
...except BSD. But isn't BSD dying? ;-)
Hmmm... I've got Linux on four machines at home (Ubuntu and RedHat 7.x), but one dual-boots WinXP. Then there's my wife's two Macs that run OSX. And then there's her Win2K work laptop that she uses to connect to Solaris machines at work. And then there's my WinXP work laptop that I use to connect to Linux boxes (RHEL) at work.
So I guess count us as users of pretty much everything?
--Joe20€ is more like $27 USD right now. The exchange rate is bad, but it isn't THAT bad. Also, the price in Euros probably includes VAT, unlike prices here. VAT ranges from 15% to 25%, so a 20€ mouse there probably compares to a $20 mouse here. That sounds pretty reasonable for a retail optical mouse.
--JoeMight I suggest that the engineers may have insisted very thoroughly to others that they were designing for 90 days, but really they were designing for much longer. Might I suggest this essay: Exaggerate with Extreme Prejudice.
--JoeIt's called derating. I'm sure the Mars rovers were designed to last far, far longer than 90 days. They just set the "success" threshold very low given all the unknowns of the trip.
--JoeI agree for the bulk of code. If you have something tabular with many columns, you can go wider than 80 pretty quick, but not lose comprehension, mainly because each column is much narrower than 80 and that's the unit of importance: column width.
To stay in the 80-column limit for tables requires lots of abbreviations, which works against comprehension. I have some tables I wrote in here and here and here that *just* fit in 80, and really wanted to be wider.
--JoeAt least the commit log should tell you WHO likes it that way. Armed with that, you know where to send Guido and his lead pipe to teach the culprit some lessons in taste. ;-)
--JoeThat said, there are times I have something tabular that really begs for something wider than 80 columns. I can totally see that, but I consider such tables to be a special case.
I agree with tabbing, although 8-character tab stops are too much, and 2-character is too little. 4 seems just right. StupidLongAndBoringSquishCapsNames can die though. Whatever happened to concise acronyms and abbreviations? Sure, the very first time you see a name, you might want it spelled out. But once you've internalized it, having to distinguish between LongAndBoringIndexVariableName and LongAndBoringArrayVariableName gets pretty tiring.
I'm quite happy with 80 columns, 4-character indentations, tabs expanded to spaces, and fixed width fonts for my code. So far fancy GUIs do nothing but get in my way. I'll stick with VIM and xterm. :-)
--JoeSeems like a simple regular expression to break it into multiple lines is in order, followed by some joins to make it into a nice 25 - 35 line block. Trivial in a modern editor. ;-)
I agree to a fair extent. I imagine if temperature compensation equipment went into play, all we'd see is even higher posted gas prices in the summer, actually. We'd still end up spending about the same amount of money, though.
See, there's supply, and there's demand. If the below-ground tanks are above nominal temperature at all, then that artifically increases supply, and automatically puts a downward pressure on price. Conversely, summer sees an increase in travel because the weather's nice, the kids are out of school, and so on. This puts an upward pressure on price.
Because of this expansion, the amount you're getting charged per BTU goes up more than the amount you're getting charged per gallon. My hypothesis is that since the demand for BTUs is what went up, but you're actually buying fewer BTUs of gasoline per measured gallon, the offered price per measured gallon doesn't go up as far as it otherwise would if gasoline stayed at a constant temperature year-round.
If you started charging people based on temperature-compensated gallons instead of measured gallons (so, for instance, 1 measured gallon might equal 0.95 compensated gallons when it's hot out), the "price/gallon" will go up, if only because now the price reflects price per BTU. There won't be this persistent blunting effect on the upward gasoline price pressure.
In other words, this is too big of a market for the effect to have not already been priced in. And yes, it probably is the local gas station that's getting the short end of the stick here, if anyone, although I imagine the attached Quicky-Marts help act as a counter balance, since summer travel season == families with kids buying snacks. The actual below-ground temperaturs for the tanks doesn't really shift much (take a look here for one example), so it's really gasoline being sold from above ground that sucks. (Think fuel delivery truck.)
If nothing else, I'll skip a gas station from now on if I see it has just gotten a fuel delivery in the summer. The rest of the time? It should be fine.
--Joe
I know you were trying to be smart, but hasn't 20th June passed already?
Yeah, only spanning 3 or 4 centuries, depending on how you count. :-)
Although, like all long lasting friendships, it has its ups and downs. Would you like some Freedom Fries with that?
That's the surface concern, but really they should be concerned end-to-end, and probably are.
--JoeThat's only true if you audit the entire Blackberry software stack for side-channel information leaks at the machine code level. I refer you to Ken Thompson's classic, Reflections on Trusting Trust. I've actually worked with a vendor that has tools for embedding special kinds of sentinels in object code, taking an even more direct and undetectable route than Ken did.
They're right to be wary.
--JoePsychologists call this "projection." That's why adulterers are more likely to accuse their spouse of cheating, etc.
That said, we both probably spy on each other as much as possible.
--JoeErrr.. Track $11...
I wasn't quite so fancy, being a poor high school kid at the time, using the school's computers during my lunch break or after school. But, I did manage (with documentation I nabbed from a Beagle Bros cheat sheet I think) to make "password protected" disks. You'd boot them and all you'd see is the password program. Run that, and if you got the password right it would "unlock" the disk. All it was really doing was changing the DOS 3.3 directory start from sector 1 to sector 2 or some such. :-) (Track 11 for the win!) And, by then, I was actually using ProtoDOS for my DOS 3.3 needs.
Ah, memories. 6502 was the second assembly language I learned. TMS9900 was the first.
--Joe