The address size isn't the issue, it's the data size. If all your ints are now 64bits by default, then naturally they'll take up twice the amount of RAM. None of the data sizes are changing in 64 bit mode. int and long will continue to be 32 bits. This is probably because some applications (including those from Microsoft) expect these data types to be 32 bits long.
2GB is the ideal configuration for 64-bit Vista, we're told. Vista 32-bit will work ideally at 1GB, and minimum 512. However, since 64-bit is handling data chunks that are double the size, you'll need double the memory, hence the 2GB. Does this make sense to anyone? It sounds like he thinks the memory footprint of all applications will double just because the address size has. Or perhaps this is just what they're going to tell users when the next version of MS Word occupies 200 megs of RAM.
For short trips in temperate weather, a backpack isn't likely to weigh 40 pounds. The equipment has gotten exceedingly light in the past decade. But the technology is darn interesting nevertheless.
So the students who get fad degrees based on expected income are drifting away from programming towards more traditional business careers. The only difference between now and a few years ago is that the reason has changed. No longer the DotCom collapse, it's now offshoring that's driving the switch. How surprising.
Voice/IP isn't like traditional the traditional telephone system at all. I can't install my own private telephone network with encrypted lines but with V/IP this is fairly easy to achieve. It's always been easy to achieve, provided you had a computer at each end. Remember PGPFone?
Don't make business decisions based on rumor when accurate information is easily obtainable. I agree that it's wise to choose the proper venue for any conversation, but that's an entirely separate issue. That isn't to say I don't have similar stories of my own, but I consider such behavior far more appropriate in a highschool hallway than in a boardroom. Talk is talk but business is busines.
From performance tests, I've noticed that it's possible to get CPU coolers with nerarly identical performance where one is rates at 22 decibels and the other is rated at 45. Case fans are another easy one. Compare air displacement between models and buy the quietest one that moves air at the rate you need. Just by doing this, I've reduced my computer from sounding like a hovercraft to being barely audible. And if you aren't review-inclined, many popular online retail sites list the noise rating of these products, so there's often no need to go looking for this information.
Originally developed by Bruce Schneier so you know the crypto doesn't suck, this software is both free and very easy to use. I don't know what I'd do without it.
As far as I'm concerned, Anakin already made the transition, though it was never really reflected onscreen. Let's see if I remember the sequence of events correctly:
* Anakin is a whiny brat on an extended date with Amidala * Anakin murders an entire community of sand people for practically no reason * Anakin goes and tells Amidala this, and in celebration they declare their love from one another and conceive the twins
That "murders an entire community of sand people" bit was the transition, IMO. It just happened offscreen with no real preamble in the story.
Quite simply, the cinematography in the first two films was bad and terrible, respectively. Also, the technology failed at rendering some scenes that should have been done with more traditional methods (Anakin riding some beast critter standing up springs to mind). Finally, the story progression was at once both trite and confusing, made worse by the terrible acting (which I personally attribute to poor direction).
From Kevin Smith's review it's clear that the Jar Jar issues have been addressed, and that Lucas makes at least a few attempts to connect with the hardcore fans, but the review says nothing about cinematography or direction. I'm going to give this film the benefit of the doubt and go see it, but I don't expect these particular two issues to have been addressed adequately. I'm hoping for a good action film and will try to withhold any criticisms about plot, depth, or continuity.
MD players may have sold for $400 at the outset, but the price quickly dropped to $200 or less. And player/recorders were available both in stereo-sized versions and in pocket-sized versions. Also, blanks were (and are) readily available.
The problem with MiniDiscs was timing. They were just starting to gain momentum in the US when MP3s exploded in popularity. If the option is a MiniDisc players with 74-minute discs (MDs store 74 minutes of audio in compressed format, so they're comparable to CDs but with the quality of good MP3s) or an MP3 player, most people opted for an MP3 player (I'll speculate on why later). And this was despite the fact that all this happened before the iPod was released and average MP3 player storage was around 128MB.
Personally, I like MiniDiscs. Tracks can be named, rearranged, and deleted. Discs only store 74 minutes of audio but they're tiny, which made them a better choice than CD walkmen or even solid-state MP3 players if you're willing to carry around extra discs. And being able to record in digital format cheaply and portably (compared to a DAT walkman--I still haven't seen a pocket-sized MP3 recorder) is a great feature, provided you are willing to live with the 74 minute limit.
What may have really killed MiniDisc was Napster. Unlike Japan, CDs can't be rented in the US, but Napster was easy to use, similarly free, and had everything you'd ever want. And why bother trying to figure out how to convert MP3's to audio to write to a MiniDisc when you can buy an MP3 walkman? Sure they couldn't store as much as a pocketfull of MiniDiscs, but there aren't many folks out there willing to go through the machniations of data conversion just to use a specific device. And now with iPods and similar devices selling fairly cheaply, there is little reason to invest in what has become an obsolete technology.
My principal interest in Grouper is to have an easy way to share data with friends and family members. And while I could set up an NFS share or FTP server to do this, it's much easier to suggest Grouper to the less technically inclined. Personally, I think Grouper is a very primising applicaton, though the restriction on music sharing seems pointless.
I posted about Group in response to the GAIM thread the the other day. That said, my only complaint about Grouper is the obvious one--music is only streamable, not downloadable (though I imagine renaming the extension and/or compressing the file would be an easy way around this). If the filesharing is truly private, why bother with such a restriction?
Even if the jammer costs as much as the satellite and its destruction is guaranteed, the venture would be worthwhile. While it's quite easy to keep a bunch of these jammers in reserve somewhere and deploy them rather quickly, the satellite-owner would be hard-put to get another satellite in orbit promptly (assuming they don't have a sufficiently redundant system already in place). If time is everything in warfare, this seems like an effective tactic to neutralize enemy technology.
That said, the guy with the jammer has to be able to find and target the satellite for this to work. Do we have enough information to be able to accurately target the satellites we'd care about neutralizing?
I one had a coworker who said he always writes an address book as a first project when learning a new language or api. It covers a fairly broad range of stuff--common ui components, collections, sorting, searching, file io, etc--while being conceptually pretty simple.
I've been looking for a small, cheap, low heat/power server for quite a while now. If AMD stuck a NIC in this thing and Apache ran on it I'd buy one in a second. And if someone discovered a way to get BSD or Linux to run on it I'd be even happier.
Since most computer games take place in fantasy settings where real-world advertisements would be inappropriate, I have to wonder just how popular this is going to be. It also assumes certain display models--a FPS could display billboards while there's no good place in RTS games but the load screen. It's an interesting idea that's a bit ahead of its time, but I don't see it being used in any of the games that are on my christmas list.
Frankly, I've become a bit put off by all of these aptitude tests Google has been assaulting us with. The method of advertising has given me the impression that Google lacks any real direction or organization but is banking on its collection of brilliant people to do something wonderful. There was a time that working at Google sounded kind of interesting, but that time has passed.
Verifying IDs against purchased tickets does theoretically guarantee that a valid passenger manifest is available in the event of a Mishap. Assuming all passengers presented valid IDs, the feds could root about and figure out the likely passengers that may have caused said Mishap, then track down their friends, etc. The issue then becomes: is the possibility of effective ID fraud high enough among these theoretical evildoers that the ID checks will be useful? My guess is that the answer is "yes" but only by a slight margin.
But the real issue is why the text of this law must be kept secret. I can think of two general reasons: if the text of the law reveals something that may allow evildoers to circumvent the law itself, or if publicizing the text of the law could cause a panic. Since I find it unlikely that knowing the reasons IDs should be checked would allow would-be terrorists any advantage (unless it includes a list of suspected terrorists), my conclusion is that there is likely something in the text of the law that could cause a panic. Still seems like a dumb reason to necessite the secrecy of a law, but then the government doesn't always act in a sensible manner.
It's worth noting that the quoted statement is not protected by the first amendment, though the wording is such that it could probably be argued both ways. Findlaw has this to say about "clear and present danger. " In fact, I remember reading somewhere that the FBI is actually required to investigate any citizen who advocates violence against the president. Another useful link on the history and limitations of the first amendment is here.
Very well said. The DB applications I've written use stored procedures exclusively for these very reasons. If a DB does not support stored procs then it isn't even a candidate.
That said, views do have the same performance advantages, but don't have quite the same degree of encapsulation. If I had to I'd use views but they still aren't as effective as stored procs.
Slashdot Mirror
The address size isn't the issue, it's the data size. If all your ints are now 64bits by default, then naturally they'll take up twice the amount of RAM.
None of the data sizes are changing in 64 bit mode. int and long will continue to be 32 bits. This is probably because some applications (including those from Microsoft) expect these data types to be 32 bits long.
2GB is the ideal configuration for 64-bit Vista, we're told. Vista 32-bit will work ideally at 1GB, and minimum 512. However, since 64-bit is handling data chunks that are double the size, you'll need double the memory, hence the 2GB.
Does this make sense to anyone? It sounds like he thinks the memory footprint of all applications will double just because the address size has. Or perhaps this is just what they're going to tell users when the next version of MS Word occupies 200 megs of RAM.
For short trips in temperate weather, a backpack isn't likely to weigh 40 pounds. The equipment has gotten exceedingly light in the past decade. But the technology is darn interesting nevertheless.
So the students who get fad degrees based on expected income are drifting away from programming towards more traditional business careers. The only difference between now and a few years ago is that the reason has changed. No longer the DotCom collapse, it's now offshoring that's driving the switch. How surprising.
Voice/IP isn't like traditional the traditional telephone system at all. I can't install my own private telephone network with encrypted lines but with V/IP this is fairly easy to achieve.
It's always been easy to achieve, provided you had a computer at each end. Remember PGPFone?
Don't make business decisions based on rumor when accurate information is easily obtainable. I agree that it's wise to choose the proper venue for any conversation, but that's an entirely separate issue. That isn't to say I don't have similar stories of my own, but I consider such behavior far more appropriate in a highschool hallway than in a boardroom. Talk is talk but business is busines.
From performance tests, I've noticed that it's possible to get CPU coolers with nerarly identical performance where one is rates at 22 decibels and the other is rated at 45. Case fans are another easy one. Compare air displacement between models and buy the quietest one that moves air at the rate you need. Just by doing this, I've reduced my computer from sounding like a hovercraft to being barely audible. And if you aren't review-inclined, many popular online retail sites list the noise rating of these products, so there's often no need to go looking for this information.
As far as I know, the philosophic community has long since given up on the existence or nonexistence of God as a provable argument.
http://passwordsafe.sourceforge.net/
Originally developed by Bruce Schneier so you know the crypto doesn't suck, this software is both free and very easy to use. I don't know what I'd do without it.
As far as I'm concerned, Anakin already made the transition, though it was never really reflected onscreen. Let's see if I remember the sequence of events correctly:
* Anakin is a whiny brat on an extended date with Amidala
* Anakin murders an entire community of sand people for practically no reason
* Anakin goes and tells Amidala this, and in celebration they declare their love from one another and conceive the twins
That "murders an entire community of sand people" bit was the transition, IMO. It just happened offscreen with no real preamble in the story.
Quite simply, the cinematography in the first two films was bad and terrible, respectively. Also, the technology failed at rendering some scenes that should have been done with more traditional methods (Anakin riding some beast critter standing up springs to mind). Finally, the story progression was at once both trite and confusing, made worse by the terrible acting (which I personally attribute to poor direction).
From Kevin Smith's review it's clear that the Jar Jar issues have been addressed, and that Lucas makes at least a few attempts to connect with the hardcore fans, but the review says nothing about cinematography or direction. I'm going to give this film the benefit of the doubt and go see it, but I don't expect these particular two issues to have been addressed adequately. I'm hoping for a good action film and will try to withhold any criticisms about plot, depth, or continuity.
Seriously. Does China have a valid complaint or not? No one knows yet. Until then, there's nothing to report.
MD players may have sold for $400 at the outset, but the price quickly dropped to $200 or less. And player/recorders were available both in stereo-sized versions and in pocket-sized versions. Also, blanks were (and are) readily available.
The problem with MiniDiscs was timing. They were just starting to gain momentum in the US when MP3s exploded in popularity. If the option is a MiniDisc players with 74-minute discs (MDs store 74 minutes of audio in compressed format, so they're comparable to CDs but with the quality of good MP3s) or an MP3 player, most people opted for an MP3 player (I'll speculate on why later). And this was despite the fact that all this happened before the iPod was released and average MP3 player storage was around 128MB.
Personally, I like MiniDiscs. Tracks can be named, rearranged, and deleted. Discs only store 74 minutes of audio but they're tiny, which made them a better choice than CD walkmen or even solid-state MP3 players if you're willing to carry around extra discs. And being able to record in digital format cheaply and portably (compared to a DAT walkman--I still haven't seen a pocket-sized MP3 recorder) is a great feature, provided you are willing to live with the 74 minute limit.
What may have really killed MiniDisc was Napster. Unlike Japan, CDs can't be rented in the US, but Napster was easy to use, similarly free, and had everything you'd ever want. And why bother trying to figure out how to convert MP3's to audio to write to a MiniDisc when you can buy an MP3 walkman? Sure they couldn't store as much as a pocketfull of MiniDiscs, but there aren't many folks out there willing to go through the machniations of data conversion just to use a specific device. And now with iPods and similar devices selling fairly cheaply, there is little reason to invest in what has become an obsolete technology.
Or does the US actually produce more emissions per year than they do?
My principal interest in Grouper is to have an easy way to share data with friends and family members. And while I could set up an NFS share or FTP server to do this, it's much easier to suggest Grouper to the less technically inclined. Personally, I think Grouper is a very primising applicaton, though the restriction on music sharing seems pointless.
I posted about Group in response to the GAIM thread the the other day. That said, my only complaint about Grouper is the obvious one--music is only streamable, not downloadable (though I imagine renaming the extension and/or compressing the file would be an easy way around this). If the filesharing is truly private, why bother with such a restriction?
and ran across Grouper. Only for Windows, but it does almost exactly what these folks want.
Even if the jammer costs as much as the satellite and its destruction is guaranteed, the venture would be worthwhile. While it's quite easy to keep a bunch of these jammers in reserve somewhere and deploy them rather quickly, the satellite-owner would be hard-put to get another satellite in orbit promptly (assuming they don't have a sufficiently redundant system already in place). If time is everything in warfare, this seems like an effective tactic to neutralize enemy technology.
That said, the guy with the jammer has to be able to find and target the satellite for this to work. Do we have enough information to be able to accurately target the satellites we'd care about neutralizing?
I one had a coworker who said he always writes an address book as a first project when learning a new language or api. It covers a fairly broad range of stuff--common ui components, collections, sorting, searching, file io, etc--while being conceptually pretty simple.
I've been looking for a small, cheap, low heat/power server for quite a while now. If AMD stuck a NIC in this thing and Apache ran on it I'd buy one in a second. And if someone discovered a way to get BSD or Linux to run on it I'd be even happier.
Since most computer games take place in fantasy settings where real-world advertisements would be inappropriate, I have to wonder just how popular this is going to be. It also assumes certain display models--a FPS could display billboards while there's no good place in RTS games but the load screen. It's an interesting idea that's a bit ahead of its time, but I don't see it being used in any of the games that are on my christmas list.
Frankly, I've become a bit put off by all of these aptitude tests Google has been assaulting us with. The method of advertising has given me the impression that Google lacks any real direction or organization but is banking on its collection of brilliant people to do something wonderful. There was a time that working at Google sounded kind of interesting, but that time has passed.
Verifying IDs against purchased tickets does theoretically guarantee that a valid passenger manifest is available in the event of a Mishap. Assuming all passengers presented valid IDs, the feds could root about and figure out the likely passengers that may have caused said Mishap, then track down their friends, etc. The issue then becomes: is the possibility of effective ID fraud high enough among these theoretical evildoers that the ID checks will be useful? My guess is that the answer is "yes" but only by a slight margin.
But the real issue is why the text of this law must be kept secret. I can think of two general reasons: if the text of the law reveals something that may allow evildoers to circumvent the law itself, or if publicizing the text of the law could cause a panic. Since I find it unlikely that knowing the reasons IDs should be checked would allow would-be terrorists any advantage (unless it includes a list of suspected terrorists), my conclusion is that there is likely something in the text of the law that could cause a panic. Still seems like a dumb reason to necessite the secrecy of a law, but then the government doesn't always act in a sensible manner.
It's worth noting that the quoted statement is not protected by the first amendment, though the wording is such that it could probably be argued both ways. Findlaw has this to say about "clear and present danger. " In fact, I remember reading somewhere that the FBI is actually required to investigate any citizen who advocates violence against the president. Another useful link on the history and limitations of the first amendment is here.
Very well said. The DB applications I've written use stored procedures exclusively for these very reasons. If a DB does not support stored procs then it isn't even a candidate.
That said, views do have the same performance advantages, but don't have quite the same degree of encapsulation. If I had to I'd use views but they still aren't as effective as stored procs.