You're completely wrong - there are a number of subtle differences between the platforms that requires a fair amount of additional testing. Distribution to distribution, you end up with a lot of version mismatches between the distros. One version might have the pam modules at 1.7.2, another might have 1.7.4 (version numbers are arbitrary, not necessarily correct) and thats one of the difficulties in testing your products on multiple distributions. Mix that with the differing base installs and the amount of customization you're allowed to do during installation and you've got a testing hell hole that requires near full testing on each distribution of linux you want to support.
Yes but no - rail isn't quite the same as a paved surface. I would assume that asphalt is cheaper than rail, foot per foot. You're limited with regard to terrain with rail, as well. You can't put a twisty in laid rail and you can't have great elevation gains without substantial space.
Although somewhat on point with what it sounds like the point of the book is, something that is still important to point out is that user education is one of the best ways to "secure" "IM, P2P, and IRC applications". Just because you can secure the most use applications doesn't stop your employee from installing abnormal, so to speak, and then misusing it as a means of getting around restrictions. Educate your employees and users and ensure they know why there are restrictions and the need for security with applications they use.
These are the first real steps towards completely autonomous vehicles that have any sense about them. You're not going to see these things out on roads like we have today for a long time, if ever, because of how unpredictable the real world is. However, imagine if you build roads that are only used by autonomous vehicles. It could be similar to an airplane - when you reach altitude, you program your heading and let it go at it, but when you're close to your destination, off it goes and you're back in full control. That, in my opinion, is where this technology is eventually going to go.
Like most slashdot articles comparing things, this is an apples vs. oranges argument. Look at some of the comparisons when they line them up side by side. Some of the comparison factors are completely useless and only present to make MySQL appear better than it really is. I'm a MySQL fan, but I'm also a fan of using the right tool for the job. If you use MySQL in a production environment, you better hope you never need to expand much. MS, IBM, Oracle all provide migration to beefier versions that will do a whole lot more than MySQL and thats what their express/limited versions are targeted towards. Migration to a better product as the need arises, without having to restructure your applications.
He doesnt appear to be an IBM employee. To comment on what some people have said previously, all articles on developerWorks are screened - there is a process for publishing. It won't be removed unless it gets negative attention, and this is anything but negative.
They're not the same - the link posted was from pushing amplified signal through the hard drives, chirping the heads enabling you to hear the signal. The link from the story is just tearing apart a hard drive and using a few pieces from it to create a rudimentary speaker.
Gee, the site promoting it didnt last long - wonder who had that shutdown? Hah... guess they dont realize that publicizing it will only make matters a lot worse and draw more people to it.
Wasnt it Yamaha who came up with the burner that will burn images and text onto the front side of the cd as well? Innovative idea, too bad it probably wont take off now since its not gonna be produced anymore.
If it would take sales away, would that really matter? Thats just Microsofts problem, if you ask me - its like saying that people upgrading an old computer will take sales away from new computer sales. Im sure the media center units will be sporting greater hardware than is in the XBox.
A GUI isnt always desired - why WOULDNT you have a command line version of a utility like this? If you're going to be doing batch jobs, it would be a lot easier to have something that would be easily scriptable that doesnt require a bloated GUI version (or any GUI for that matter - Im not implying that the given product has a bloated GUI, before you flame). Not all users have a need for a graphical windowing system.
I dont understand why everyone is trying to jump on the all-in-one unit bandwagon. If I want a cell phone, I want a cell phone, not a bulky handheld that has 50 other functions and is 10 times the price of a standard cell phone. If I want something to play games on, Im going to choose something like a gameboy that has a large game base. I just dont think the mass markets are going to support and hold on to this type of all-in-one technology.
On the bright side, I guess these make cell phones less likely to be discarded - repair prices would probably be under the cost of a new phone unlike most standard cell phones today.
You're completely wrong - there are a number of subtle differences between the platforms that requires a fair amount of additional testing. Distribution to distribution, you end up with a lot of version mismatches between the distros. One version might have the pam modules at 1.7.2, another might have 1.7.4 (version numbers are arbitrary, not necessarily correct) and thats one of the difficulties in testing your products on multiple distributions. Mix that with the differing base installs and the amount of customization you're allowed to do during installation and you've got a testing hell hole that requires near full testing on each distribution of linux you want to support.
Yes but no - rail isn't quite the same as a paved surface. I would assume that asphalt is cheaper than rail, foot per foot. You're limited with regard to terrain with rail, as well. You can't put a twisty in laid rail and you can't have great elevation gains without substantial space.
Although somewhat on point with what it sounds like the point of the book is, something that is still important to point out is that user education is one of the best ways to "secure" "IM, P2P, and IRC applications". Just because you can secure the most use applications doesn't stop your employee from installing abnormal, so to speak, and then misusing it as a means of getting around restrictions. Educate your employees and users and ensure they know why there are restrictions and the need for security with applications they use.
These are the first real steps towards completely autonomous vehicles that have any sense about them. You're not going to see these things out on roads like we have today for a long time, if ever, because of how unpredictable the real world is. However, imagine if you build roads that are only used by autonomous vehicles. It could be similar to an airplane - when you reach altitude, you program your heading and let it go at it, but when you're close to your destination, off it goes and you're back in full control. That, in my opinion, is where this technology is eventually going to go.
Like most slashdot articles comparing things, this is an apples vs. oranges argument. Look at some of the comparisons when they line them up side by side. Some of the comparison factors are completely useless and only present to make MySQL appear better than it really is. I'm a MySQL fan, but I'm also a fan of using the right tool for the job. If you use MySQL in a production environment, you better hope you never need to expand much. MS, IBM, Oracle all provide migration to beefier versions that will do a whole lot more than MySQL and thats what their express/limited versions are targeted towards. Migration to a better product as the need arises, without having to restructure your applications.
He doesnt appear to be an IBM employee. To comment on what some people have said previously, all articles on developerWorks are screened - there is a process for publishing. It won't be removed unless it gets negative attention, and this is anything but negative.
The first link returned from Google is the site for Acid2. I consider that justification...
http://www.google.com/
And whats just as sad, the above statement came from someone with the username 'poot_rootbeer'.
They're not the same - the link posted was from pushing amplified signal through the hard drives, chirping the heads enabling you to hear the signal. The link from the story is just tearing apart a hard drive and using a few pieces from it to create a rudimentary speaker.
Gee, the site promoting it didnt last long - wonder who had that shutdown? Hah... guess they dont realize that publicizing it will only make matters a lot worse and draw more people to it.
Wasnt it Yamaha who came up with the burner that will burn images and text onto the front side of the cd as well? Innovative idea, too bad it probably wont take off now since its not gonna be produced anymore.
If it would take sales away, would that really matter? Thats just Microsofts problem, if you ask me - its like saying that people upgrading an old computer will take sales away from new computer sales. Im sure the media center units will be sporting greater hardware than is in the XBox.
A GUI isnt always desired - why WOULDNT you have a command line version of a utility like this? If you're going to be doing batch jobs, it would be a lot easier to have something that would be easily scriptable that doesnt require a bloated GUI version (or any GUI for that matter - Im not implying that the given product has a bloated GUI, before you flame). Not all users have a need for a graphical windowing system.
I dont understand why everyone is trying to jump on the all-in-one unit bandwagon. If I want a cell phone, I want a cell phone, not a bulky handheld that has 50 other functions and is 10 times the price of a standard cell phone. If I want something to play games on, Im going to choose something like a gameboy that has a large game base. I just dont think the mass markets are going to support and hold on to this type of all-in-one technology.
On the bright side, I guess these make cell phones less likely to be discarded - repair prices would probably be under the cost of a new phone unlike most standard cell phones today.