Wow, that's a really old story! Friday, Jul. 27, 1962
The best part, though, was this one at the end:
Computers--one capable of 200,000 calculations per second-- handle information so swiftly that the whole process lasts two or three minutes from detection to interception.
Blu-ray has higher storage and (I think) slightly more DRM, while HD-DVD has no region codes. I'm sure a lot of people won't be affected by region codes, but those of us who get international stuff would have prefered HD-DVD.
Dunno about the government but the MPAA-types sure would love that. It must be nice being able to pressure*cough*bribe*cough* people into making laws to help your antiquated business plans stay afloat.
Just saying "will publish APIs" is rather useless - MSDN already has thousands of pages of fantastic documentation for APIs. Which new ones will they be publishing? Exports that are considered volatile across versions? Better ways to make shell extensions? Newer custom controls? Ways to plug your own storage engine into SQL Server? Need some specifics, please!
Now, a lot of sites have this crazy idea of embedded video that streams from a site or source that's dedicated to streaming video. You know like YouTube, Blip.tv or any of the.tv sites really. Does Microsoft utilize any of those freely available options? Oh no, of course not! YouTube is Google! Even if we don't have a competing solution we must not use theirs!
You would think Microsoft would at least use its own video streaming service, Soapbox
Assuming this is a compile from the main trunk, memory usage should be better in this for Windows users. A week ago a ported version of FreeBSD's malloc was checked in. This has much less fragmentation compared to Windows' low-frag heaps which should result in less memory used over time and slightly better performance.
The reason for Java/C#'s popularity isn't because of the VM, it's because of the huge accompanying frameworks that allow for rapid development which is in most cases much more important than efficient cpu/memory usage these days. Build one of these frameworks for C/C++ and you will find it much easier to compete with newer langs.
Server 2008 is just Vista SP1 with different things installed and increased artificial limits. If Vista doesn't work for you, 2008 won't either. For what it's worth, I ran XP x64 since it was in beta and the only incompatible thing was an old printer - it's far from unsupported, though Vista does have a much improved x64 memory manager.
I don't understand how it would effect Linux (much less the GNU utilities), but it might slow down a few Y! projects. These projects, even if MS succeeds and stops all development on them, will still be continued if someone in the community thinks they are useful. That's the beauty of Open Source.
If it was there to help, there would be a way to turn it off other than hitting F8 every time you boot. They wouldn't have disabled the DDISABLE_INTEGRITY_CHECKS boot option, so that knowledgable people and developers wouldn't have a big hassle. They wouldn't suddenly enforce it on 32-bit whenever you try to load up certain DRMed media.
The two things I find annoying are UAC and enforced DRM. Yes, you can be affected by DRM even without buying any DRMed media--just try to load an unsigned driver in 64-bit.
Everything else is more disappointment than annoyance. With how much time they had to bake it, Vista could have come out amazing and full of great features. It was disappointing that it didn't live up to the hype.
It may not have been revolutionary, but it is still a solid improvement on XP. In my opinion.
READ the license before putting your code under it. I know the GPL is big, but you only need to do it once. You can change the license on future releases (assuming you own the copyright), but you can't revoke the rights the GPL grants to people using past releases.
I don't have any book recommendations, but if you're developing for Windows, be sure to read the Windows Vista User Experience Guidelines. Even if you're not on Windows it has some design advice applicable anywhere.
Now that XCode/ObjC has garbage collection, there's really no good reason a Java developer couldn't move over to Objective C if they really want to develop something for the platform.
The strength of Java is not garbage collection, buts the massive backing library that allows for rapid development.
I generally agree with you, except for one area where there IS abusive DRM: mandatory x64 driver signing.
They snuck it in under the guise of improved security, when the real purpose is to stop people from making drivers to intercept DRMed data. For proof of this, try watching certain DRMed content in 32-bit Vista with an unsigned driver loaded - it won't let you.
End result? People who want to still get past the DRM, developers have to pay large yearly amounts for a code signing certificate (which can be a severe cost for small-time and Free/Open Source developers), and users have to pay more to offset development costs.
think of scoped_ptr and auto_ptr. no reference counting there. shared_ptr may get a bulk of the talk, but it's not the only smart pointer out there (and certainly shouldn't be used as an app-wide garbage collection).
And I wish people would stop using GC as an argument why languages as Java are so much better to use than C++.
As a C++ developer, GC is the main thing that turns me off to so many languages. With C++ I know exactly when objects will be destroyed - with C# I have no clue, leading to silly stuff like "using" and "try...finally" to make sure that file/socket/etc. is closed. Java/C# proponents always point to memory leaks as a reason for GC, but C++ makes it mind-numbingly easy to avoid them. You do not usually need to use pointers that often, but when you do smart pointers can help manage lifetime without any overhead.
Slashdot Mirror
What? I'm sorry, I couldn't here you over cleaning my SNES cartridge.
Blu-ray has higher storage and (I think) slightly more DRM, while HD-DVD has no region codes. I'm sure a lot of people won't be affected by region codes, but those of us who get international stuff would have prefered HD-DVD.
Dunno about the government but the MPAA-types sure would love that. It must be nice being able to pressure*cough*bribe*cough* people into making laws to help your antiquated business plans stay afloat.
Just saying "will publish APIs" is rather useless - MSDN already has thousands of pages of fantastic documentation for APIs. Which new ones will they be publishing? Exports that are considered volatile across versions? Better ways to make shell extensions? Newer custom controls? Ways to plug your own storage engine into SQL Server? Need some specifics, please!
You would think Microsoft would at least use its own video streaming service, Soapbox
Assuming this is a compile from the main trunk, memory usage should be better in this for Windows users. A week ago a ported version of FreeBSD's malloc was checked in. This has much less fragmentation compared to Windows' low-frag heaps which should result in less memory used over time and slightly better performance.
The reason for Java/C#'s popularity isn't because of the VM, it's because of the huge accompanying frameworks that allow for rapid development which is in most cases much more important than efficient cpu/memory usage these days. Build one of these frameworks for C/C++ and you will find it much easier to compete with newer langs.
I think those are only available for testers.
Does Britannia count? Might be more appropriate here.
Which is rather hypocritical, considering Dre got in trouble for using the THX sound on his last CD.
Server 2008 is just Vista SP1 with different things installed and increased artificial limits. If Vista doesn't work for you, 2008 won't either. For what it's worth, I ran XP x64 since it was in beta and the only incompatible thing was an old printer - it's far from unsupported, though Vista does have a much improved x64 memory manager.
I don't understand how it would effect Linux (much less the GNU utilities), but it might slow down a few Y! projects. These projects, even if MS succeeds and stops all development on them, will still be continued if someone in the community thinks they are useful. That's the beauty of Open Source.
In the end it doesn't matter if it's a bluff or not, because Microsoft will never reveal anything either way. It's the FUD they want, not the money.
If it was there to help, there would be a way to turn it off other than hitting F8 every time you boot. They wouldn't have disabled the DDISABLE_INTEGRITY_CHECKS boot option, so that knowledgable people and developers wouldn't have a big hassle. They wouldn't suddenly enforce it on 32-bit whenever you try to load up certain DRMed media.
The two things I find annoying are UAC and enforced DRM. Yes, you can be affected by DRM even without buying any DRMed media--just try to load an unsigned driver in 64-bit.
Everything else is more disappointment than annoyance. With how much time they had to bake it, Vista could have come out amazing and full of great features. It was disappointing that it didn't live up to the hype.
It may not have been revolutionary, but it is still a solid improvement on XP. In my opinion.
READ the license before putting your code under it. I know the GPL is big, but you only need to do it once. You can change the license on future releases (assuming you own the copyright), but you can't revoke the rights the GPL grants to people using past releases.
I don't have any book recommendations, but if you're developing for Windows, be sure to read the Windows Vista User Experience Guidelines. Even if you're not on Windows it has some design advice applicable anywhere.
They could have been bought by EA instead. Count your blessings.
does one perform a scientific review of religion? either believe or not, there is no science. that's why they call it faith.
I generally agree with you, except for one area where there IS abusive DRM: mandatory x64 driver signing.
They snuck it in under the guise of improved security, when the real purpose is to stop people from making drivers to intercept DRMed data. For proof of this, try watching certain DRMed content in 32-bit Vista with an unsigned driver loaded - it won't let you.
End result? People who want to still get past the DRM, developers have to pay large yearly amounts for a code signing certificate (which can be a severe cost for small-time and Free/Open Source developers), and users have to pay more to offset development costs.
think of scoped_ptr and auto_ptr. no reference counting there. shared_ptr may get a bulk of the talk, but it's not the only smart pointer out there (and certainly shouldn't be used as an app-wide garbage collection).
My old PC can't handle Crysis and I've been waiting to see the Phenom before upgrading!
As a C++ developer, GC is the main thing that turns me off to so many languages. With C++ I know exactly when objects will be destroyed - with C# I have no clue, leading to silly stuff like "using" and "try...finally" to make sure that file/socket/etc. is closed. Java/C# proponents always point to memory leaks as a reason for GC, but C++ makes it mind-numbingly easy to avoid them. You do not usually need to use pointers that often, but when you do smart pointers can help manage lifetime without any overhead.