...there's absolutely no upside to telling Americans that dumping tons of pollutants into the atmosphere is going to have a bad effect, so researchers on one side who are going where the data takes them and researchers on the other who are paid handsomely to find out that there's absolutely no problem with spewing ever-growing quantities of hydrocarbons into the atmosphere.
Really? Where are these unbiased researchers getting their funding? Further, how much funding do you think they get the year after they tell us everything is doing fine? A terrified public anxious for answers keeps money coming in. There's certainly at least the potential for bias on either side of the issue.
If you've ever watched soccer on television you'd have to wonder if we couldn't implement some sort of soccer-compression algorithm that only sends partial-video frames for the one guy who's looking around deciding where to pass. It seems like an awful shame to waste bits for the six players on the screen that aren't moving.
Hilarious. I love that MS thinks that "Our product is more stable because we've fixed less bugs than our competitors" is a valid argument.
Perhaps their next tactic will be to impress us with the fact that those 15 patches were hundreds of mbs, cumulatively.
I definitely agree, there are plenty of commercial sites that provide movie listings via dvd/video sales as well (including Amazon), but I still find imdb.com to be a lot more exhaustive.
My guess is the only thing keeping most/.ers from building their own house is a healthy fear of sunlight...
As for *most* people, wouldn't they find themselves more interested in some sort of Best-Buy-Tivo situation?
I'm pretty sure the market for this thing is mostly Visual Basic developers.
I'm a JAVA developer forced to learn C# for a recent project. Frankly, the C# language borrowed almost everything from java anyways. There are alot of keyword replacements, some added complexity (delegates, structs), and some missing nessecity ('throws' statement)..
All in all, the C# LANGUAGE is essentially JAVA, syntactically. You'd be better off spending time reading about the.NET platform and the CLR. IMHO that's where the signifigant differences are.
-phill
ps. The books I found usefull were Programming C#, Jesse Liberty (Oreilly)... and Understanding.Net, Chappel (?)..
Anyone with a PocketPC should definitely give the demo a spin. I tried it (last time/. covered this.. hehe), and it's pretty impressive how quickly you can become not just effective, but downright fast.
Slashdot Mirror
If you've ever watched soccer on television you'd have to wonder if we couldn't implement some sort of soccer-compression algorithm that only sends partial-video frames for the one guy who's looking around deciding where to pass. It seems like an awful shame to waste bits for the six players on the screen that aren't moving.
Hilarious. I love that MS thinks that "Our product is more stable because we've fixed less bugs than our competitors" is a valid argument. Perhaps their next tactic will be to impress us with the fact that those 15 patches were hundreds of mbs, cumulatively.
I definitely agree, there are plenty of commercial sites that provide movie listings via dvd/video sales as well (including Amazon), but I still find imdb.com to be a lot more exhaustive.
-phill
My guess is the only thing keeping most /.ers from building their own house is a healthy fear of sunlight...
As for *most* people, wouldn't they find themselves more interested in some sort of Best-Buy-Tivo situation?
I'm pretty sure the market for this thing is mostly Visual Basic developers.
I'm a JAVA developer forced to learn C# for a recent project. Frankly, the C# language borrowed almost everything from java anyways. There are alot of keyword replacements, some added complexity (delegates, structs), and some missing nessecity ('throws' statement).. All in all, the C# LANGUAGE is essentially JAVA, syntactically. You'd be better off spending time reading about the .NET platform and the CLR. IMHO that's where the signifigant differences are.
-phill
ps. The books I found usefull were Programming C#, Jesse Liberty (Oreilly)... and Understanding .Net, Chappel (?)..
Anyone with a PocketPC should definitely give the demo a spin. I tried it (last time /. covered this.. hehe), and it's pretty impressive how quickly you can become not just effective, but downright fast.