You put them in the belly of your space ship and smuggle them off the planet. Just hope angry local cowboys don't shoot you when your doctor is nowhere to be found.
No one I know with it had any copper removed. Not one.
As I said in my reply direct to him, there are a bunch of incorrect things people (who strangely don't have it) seem to keep repeating. To enumerate:
1) they do not remove copper usually. They never will if asked not to. 2) you do not need phone service 3) their phone service is regulated, if you do have it 4) Their network absolutely can handle the bandwidth. I can saturate my 15 mbit connection 24/7. 1.8meg/sec sustained, with no problems. (I know the grandparent didn't mention THAT FIOS rumor, but I thought I'd toss it in there)
I have FiOS. And contrary to the "they remove the copper" bullshit people seem to hype up online, I still have copper lines. And, contrary to that article, I do not have (and never have had) a Verizon phone line.
If you order FiOS and don't want them to remove the copper, tell them you don't want them to. If you don't want phone service, don't order it. I think I pay $5 more a month for the service because I don't have phones, but that may be wrong. Its $44.95/month for 15mbit. Someone who knows what they pay with phone service can chime in if its less than that.
There's no grand conspiracy to force people off copper. Of course they'd rather do that, but they don't force it on anyone.
Oh, and your phone service is quite considered a telephone line if you are getting phone service from Verizon over the fiber -- you still pay all the taxes and have all the "rights" associated with phone lines. Only if you use a 3rd party VOIP over FiOS would you lose those. (Verizons fiber-based phone service is NOT VOIP)
Give someone a pro DSLR and they'll still hold it at arms length? Apparently this braniac has never used an SLR or realized you CAN'T get an image on the screen before the shutter opens.
I stopped reading after that. I assume it kept getting worse?
Not to get into an argument, but there are "nerds" who think they know what Vista brings to the table, and "nerds" actively doing development against it.
The former believes Vista brings nothing signficant to the table. The latter, who is making huge changes to their apps to support it knows exactly what has changed, and the big stuff isn't in your list.
As someone suffering through using a crappy Dell laptop running Ubuntu Dapper or WinXT because his iBook did the typical "died a month out of warranty" thing, my suggestion would be to run OSX on there. They say the grass is greener on the other side, but in this case they're wrong.
I do like Dapper, though. Its the only Linux distro I could get running on this laptop, and it was largely out of the box.
I work at a high school as a Network Administrator and I have three things to say.
1. The school can't suspend a student for what they say in a blog, UNLESS the student was using a school computer during school time to do the blog.
Funny, but how is being a network administrator at a school a useful thing to prequalify a legal opinion with? Thats like saying "I work at a hospital as a network administrator and the radiologist can't say that the results of that MRI indicate cancer."
The US founding fathers were businessmen who took over the government of the US from the British to protect their commercial interests. They gave lip service to the rest because they needed the support of the people.
Look at who the vast majority of the founding fathers were, and look at how their business interests were being impacted by British control and taxes.
Bush is the worst thing to happen to this country in a hundred years, and I say that as a fairly conservative libertarian not a blindly anti-Bush neo-con, but what he's doing is very much in line with the intents of the founding fathers.
Invoking them is not what we need to be doing. Invoking the tradition they created not based on their intents but their results is what we need to be doing.
Sparc doesn't. And the Java memory model explicitly doesn't. Java code on any platform has to assume there is no cache coherancy, and that no change to any variable not marked volatile will ever be seen by any other thread. Volatile inserts memory barriers, whereas synchronized is more about guaranteeing that a block of code will execute in-order and completely with respect to other code also locking on the same lock.
A very common misconception is that synchronized acts as a full memory barrier and causes a flush of all data associated with the block before entry and after exit, which isn't the case. (Note the comment the other reply to my post made, which was incorrect)
It inserts a memory barrier around that single object, not the entire code block. If you're not running agressive optimizations, you usually won't see any difference, but when the JVM starts reordering operations as part of optimizing the code, weird things can start happening because a simple read of a variable which may be able to be modified in other code may happen at times you don't expect and could never be seen by other threads.
Its *hard* to write Java threading code correctly. Its damn near impossible prior in Java 5 (there's a reason they completely replaced the memory model in Java 5 -- there were patterns that could not be coded correctly prior to that). And in my experience the more certain someone is that they're doing it right, the more likely it is its wrong.
I couldn't tell you how many Swing applications I've seen using anonymous inner classes declared in the constructor (which is a good example of something that is never thread safe, no matter what you do, prior to Java 5)
Don't take the apparent ease of threaded programming in Java or other modern languages as an indication that modern code is typically written to be thread safe.
Virtually every open source Java project I've used, and every single commercial application I've seen source for in Java has not been written to be properly thread safe. Even your typical principal-level Java engineer typically does not know what synchronized really does, and how it relates to the volatile keyword (which I've rarely ever seen in Java code -- and if its not there, the code is NOT thread safe). Not a single one I've ever spoken to in a professional situation has ever been able to detail what the threading rules in the java memory model are.
Java code tends to work because Intel systems guarantee cache coherency and most Java is run on Intel systems.
There is no real difference between threading in C and more modern languages -- the primary difference is that modern languages like Java and the suite of.NET languages have strict memory models, and C varies among systems. Java is very specific -- there is no guarantee that the value of a variable will be seen consistently across threads if it isn't marked volatile, for example. It *may* work (as it frequently does on Intel systems), but Java says you must not count on that. Hotspot optimizations can impact that, and different cache architectures on other platforms can. C on the other hand has different rules per platform that the engineer has to know.
But until 100% of Java developers know how to write thread safe Java, instead of 1/10th of 1% of them, I wouldn't go throwing stones at C.
I noticed the new Ikea has them, too... seems pretty useful there, too. They've got busses from the city down to there, take the zip car home and drop it off in the city.
There is a LOT of stuff MS Office does that Open Office doesn't do or does poorly.
There are also a LOT of people who have tried OO, and hate the interface and overall look and feel of it.
Its funny with this whole ODF thing that there are two camps here -- those who want document access, and the anti-Microsoft people. The former win big in this case, and the latter get laughed at -- they hitched their wagon to the wrong horse train.
This is the perfect solution -- it shuts up the vendor lockin crowd, and lets businesses and governments continue to use the best product out there without pressure from the masses.
(I should add before the slashbots mod me into oblivion that I happen to use OpenOffice on my systems at home, but I just can't see a business that really uses office being able to ever switch to it without a HUGE amount of work around the product.)
Its the hair. Within a few inches of the tits, no matter how glorious they may be, you're almost certain to find a sprouting bush of hair that gives real meaning to the old saying "buckwheat in a headlock".
Yeah it takes a fortune to sample 60 tracks and compress the dynamic range down to a few db.
Give me a break. When you compress the output as much as pop music does these days, you absolutely don't need that kind of gear. They're not recording and playing back a symphony here.
Some of the best albums I've heard in years have been done in home studios using precisely the hardware and software you scoff at.
I'd think the software interpolating the final image would have to correct for the differences in angles from each image sensor to produce a flat 2-D image...
Which would imply if you shut it off, you'd be taking fairly detailed 3-D images (left/right view 3-D limits the viewer to a single viewing angle, but if you were taking 1600 images from left to right, you'd have a LOT more image data to produce a truer 3-D model)
To be fair, its pretty trivial to create strongly typed WMI proxy classes. There's a command line to do it, or you can do it from code.
Just create a strongly typed proxy and use that, much easier. If you haven't done WMI before, you'd be suprised how rich of a mechanism it is for doing just about anything you'd want in a Windows environment.
Slashdot Mirror
You put them in the belly of your space ship and smuggle them off the planet. Just hope angry local cowboys don't shoot you when your doctor is nowhere to be found.
Second hand intarweb posts.
No one I know with it had any copper removed. Not one.
As I said in my reply direct to him, there are a bunch of incorrect things people (who strangely don't have it) seem to keep repeating. To enumerate:
1) they do not remove copper usually. They never will if asked not to.
2) you do not need phone service
3) their phone service is regulated, if you do have it
4) Their network absolutely can handle the bandwidth. I can saturate my 15 mbit connection 24/7. 1.8meg/sec sustained, with no problems. (I know the grandparent didn't mention THAT FIOS rumor, but I thought I'd toss it in there)
I have FiOS. And contrary to the "they remove the copper" bullshit people seem to hype up online, I still have copper lines. And, contrary to that article, I do not have (and never have had) a Verizon phone line.
If you order FiOS and don't want them to remove the copper, tell them you don't want them to. If you don't want phone service, don't order it. I think I pay $5 more a month for the service because I don't have phones, but that may be wrong. Its $44.95/month for 15mbit. Someone who knows what they pay with phone service can chime in if its less than that.
There's no grand conspiracy to force people off copper. Of course they'd rather do that, but they don't force it on anyone.
Oh, and your phone service is quite considered a telephone line if you are getting phone service from Verizon over the fiber -- you still pay all the taxes and have all the "rights" associated with phone lines. Only if you use a 3rd party VOIP over FiOS would you lose those. (Verizons fiber-based phone service is NOT VOIP)
Um. I can saturate my FiOS 15mb connection with XBox Live.
Why would I care where the data was coming from? If they've got big enough pipes to give me 1.8mb/sec all the time, I could care less.
Give someone a pro DSLR and they'll still hold it at arms length? Apparently this braniac has never used an SLR or realized you CAN'T get an image on the screen before the shutter opens.
I stopped reading after that. I assume it kept getting worse?
Never worked at a real company, eh?
Shit flows downhill, and blame lands on the first person who isn't smart enough to pass it down the line.
Not to get into an argument, but there are "nerds" who think they know what Vista brings to the table, and "nerds" actively doing development against it.
The former believes Vista brings nothing signficant to the table. The latter, who is making huge changes to their apps to support it knows exactly what has changed, and the big stuff isn't in your list.
As someone suffering through using a crappy Dell laptop running Ubuntu Dapper or WinXT because his iBook did the typical "died a month out of warranty" thing, my suggestion would be to run OSX on there. They say the grass is greener on the other side, but in this case they're wrong.
I do like Dapper, though. Its the only Linux distro I could get running on this laptop, and it was largely out of the box.
No, but I think they'd believe they are.
Thats a cultural stereotype, not racial.
I work at a high school as a Network Administrator and I have three things to say.
1. The school can't suspend a student for what they say in a blog, UNLESS the student was using a school computer during school time to do the blog.
Funny, but how is being a network administrator at a school a useful thing to prequalify a legal opinion with? Thats like saying "I work at a hospital as a network administrator and the radiologist can't say that the results of that MRI indicate cancer."
The US founding fathers were businessmen who took over the government of the US from the British to protect their commercial interests. They gave lip service to the rest because they needed the support of the people.
Look at who the vast majority of the founding fathers were, and look at how their business interests were being impacted by British control and taxes.
Bush is the worst thing to happen to this country in a hundred years, and I say that as a fairly conservative libertarian not a blindly anti-Bush neo-con, but what he's doing is very much in line with the intents of the founding fathers.
Invoking them is not what we need to be doing. Invoking the tradition they created not based on their intents but their results is what we need to be doing.
Clearly you weren't in the troop I was in...
No I saw the title and thought it said "Monty Python's Guide to Programming"
Question is, will you blame Zonk when he reposts it tomorrow?
Sparc doesn't. And the Java memory model explicitly doesn't. Java code on any platform has to assume there is no cache coherancy, and that no change to any variable not marked volatile will ever be seen by any other thread. Volatile inserts memory barriers, whereas synchronized is more about guaranteeing that a block of code will execute in-order and completely with respect to other code also locking on the same lock.
A very common misconception is that synchronized acts as a full memory barrier and causes a flush of all data associated with the block before entry and after exit, which isn't the case. (Note the comment the other reply to my post made, which was incorrect)
It inserts a memory barrier around that single object, not the entire code block. If you're not running agressive optimizations, you usually won't see any difference, but when the JVM starts reordering operations as part of optimizing the code, weird things can start happening because a simple read of a variable which may be able to be modified in other code may happen at times you don't expect and could never be seen by other threads.
Its *hard* to write Java threading code correctly. Its damn near impossible prior in Java 5 (there's a reason they completely replaced the memory model in Java 5 -- there were patterns that could not be coded correctly prior to that). And in my experience the more certain someone is that they're doing it right, the more likely it is its wrong.
I couldn't tell you how many Swing applications I've seen using anonymous inner classes declared in the constructor (which is a good example of something that is never thread safe, no matter what you do, prior to Java 5)
Don't take the apparent ease of threaded programming in Java or other modern languages as an indication that modern code is typically written to be thread safe.
.NET languages have strict memory models, and C varies among systems. Java is very specific -- there is no guarantee that the value of a variable will be seen consistently across threads if it isn't marked volatile, for example. It *may* work (as it frequently does on Intel systems), but Java says you must not count on that. Hotspot optimizations can impact that, and different cache architectures on other platforms can. C on the other hand has different rules per platform that the engineer has to know.
Virtually every open source Java project I've used, and every single commercial application I've seen source for in Java has not been written to be properly thread safe. Even your typical principal-level Java engineer typically does not know what synchronized really does, and how it relates to the volatile keyword (which I've rarely ever seen in Java code -- and if its not there, the code is NOT thread safe). Not a single one I've ever spoken to in a professional situation has ever been able to detail what the threading rules in the java memory model are.
Java code tends to work because Intel systems guarantee cache coherency and most Java is run on Intel systems.
There is no real difference between threading in C and more modern languages -- the primary difference is that modern languages like Java and the suite of
But until 100% of Java developers know how to write thread safe Java, instead of 1/10th of 1% of them, I wouldn't go throwing stones at C.
I noticed the new Ikea has them, too... seems pretty useful there, too. They've got busses from the city down to there, take the zip car home and drop it off in the city.
There is a LOT of stuff MS Office does that Open Office doesn't do or does poorly.
There are also a LOT of people who have tried OO, and hate the interface and overall look and feel of it.
Its funny with this whole ODF thing that there are two camps here -- those who want document access, and the anti-Microsoft people. The former win big in this case, and the latter get laughed at -- they hitched their wagon to the wrong horse train.
This is the perfect solution -- it shuts up the vendor lockin crowd, and lets businesses and governments continue to use the best product out there without pressure from the masses.
(I should add before the slashbots mod me into oblivion that I happen to use OpenOffice on my systems at home, but I just can't see a business that really uses office being able to ever switch to it without a HUGE amount of work around the product.)
Its the hair. Within a few inches of the tits, no matter how glorious they may be, you're almost certain to find a sprouting bush of hair that gives real meaning to the old saying "buckwheat in a headlock".
No child should have to see that.
Yeah it takes a fortune to sample 60 tracks and compress the dynamic range down to a few db.
Give me a break. When you compress the output as much as pop music does these days, you absolutely don't need that kind of gear. They're not recording and playing back a symphony here.
Some of the best albums I've heard in years have been done in home studios using precisely the hardware and software you scoff at.
Don't forget the ebay $50k off $300k coupon, too.
That gets him down to $280k, which is quite a bargain.
I'd think the software interpolating the final image would have to correct for the differences in angles from each image sensor to produce a flat 2-D image...
Which would imply if you shut it off, you'd be taking fairly detailed 3-D images (left/right view 3-D limits the viewer to a single viewing angle, but if you were taking 1600 images from left to right, you'd have a LOT more image data to produce a truer 3-D model)
Interesting...
To be fair, its pretty trivial to create strongly typed WMI proxy classes. There's a command line to do it, or you can do it from code.
Just create a strongly typed proxy and use that, much easier. If you haven't done WMI before, you'd be suprised how rich of a mechanism it is for doing just about anything you'd want in a Windows environment.