Linux has needed a proper NFS lock manager for many years. If Linux could duplicate its functionality, it would put a LOT of Solaris NFS servers out to pasture.
It's economic feasability, too. Rotating media is roughly $100/terabyte, it's gonna take more than one breakthrough for SSD to come close to that.
Nifty new technology doesn't get bought because it's nifty-new, it gets bought because it fills the need better than its predecessor for the price.
And YES there are plenty of applications where multiple terabytes are necessary, maybe not on your home system.
In case you're wondering, I have both on my system: / is SSD,/home is multi-terabyte RAID. Rotating mechanical media is sticking around at least for now.
Sure they are cool and retro and all that, but what are/were they actually good for? I mean activities that one might actually get paid for.
The only time I ever saw an Amiga actually doing something useful was at a live show, where an Amiga was used to generate the (admittedly cool looking) video images projected behind the performers. Everything else seems to be just games and standard applications available on any normal computer.
In the course of an entire web session's worth of CPU consumption, you are worried about the time taken to compare password characters? Any modern optimized processor should require one clock cycle per character.
Do you actually profile your code or do you just make funny noises? Or maybe you're running your web server on a Commodore 64?
I know a Vietnamese woman who grew up in a single-room shack, with brothers, sisters, mom and dad. Needless to say she learned about sex at a Very Early Age. She said it was perfectly common and ordinary, nobody thought twice about it.
In the modern days of cheap disk, big disk caches, and large ram, proper modelling is more important than strict normalization.
Back when those books were written, disk was expensive and not cached, RAM was very expensive, and machines had terrible I/O bottlenecks.. Normalization is critical under these circumstances for maximum performance.
Today, these normalization techniques will increase performance but not as much as you might think. Really it is best to concentrate efforts elsewhere, especially for a one-person shop.
All of that normalization work requires coding changes and it will undoubtedly make the code much less readable and maintainable.
For many aspects of coding, you are barking up the wrong tree. You should really concentrate your design thinking at the object persistence level instead of the database level. Use Hibernate or something similar to hide the database from your code.
Then you can take a critical look at your choices of database vendors, and you will be easily able to migrate your code the one whose product best fits your needs. You will be able to run your own benchmarks with your own data and see what will work best for you. You may even find that an object-based database will give you far better performance for the same coding effort.
Do you really think Cisco is going to be happy if their customer list falls into the hands of their competitors? If this data has profile info like "How much Cisco equipment have you bought in the last year" then it could be VERY VERY useful to their competitors.
Every Kin cell phone buyer is now locked into a (usually) 2 year contract to use and pay for a phone with no future.
What if it's "lost" or "stolen"? Insurance might cover replacement cost. If they're not making them any more, then they will have to replace it with something else.
You'll certainly be marked as a sucker when people see you with one.
I read all the responses here and I think, "so that's why it's 18% and not 0%". Yes the slashdot developer crowd will keep their big monitors, but the rest of the world, that only needs an occasional glance at a monitor screen, doesn't need that expense or inconvenience.
Those are "excuses", not reasons. We are talking about Adobe, a large software company that can actually write software. They are supposed to fix things like this BEFORE stepping out onto a new platform.
Yeah and names like "IEEE 802.3" are so much better? We can go back over time to things like PCMCIA and SCSI. Give me a break. Weird names have been in tech forever.
I think the general public gave up looking for sane tech product names a LONG time ago. Nobody attaches any significance to them. Products sell and people don't care about the buzzwords as long as the product functions.
Well I wouldn't want to build Flash or Reader from scratch so what I said is true. Source is optional for yum but of course it can be required by the repository.
The nice thing about yum is you use it to update the system packages, and third parties can use the same system to update their software. All they have to do is drop a file in/etc/yum.d and their "app store" is visible to all the package installation tools.
Slashdot Mirror
Sure you don't want to write the test because you are done with that stuff and you want to move on.
If you write the test first then you don't end up in this situation.
The test will be a beacon on the horizon to shoot for, and a validation of your specification (you DID write a specification?!?)
Put a bottle of something fun on the shelf, open it when the test passes. Motivation!
Opponents of "socialized medicine" argue that capitalism is necessary for cutting-edge medical research, here is an example of the opposite.
the NFS lock manager
Linux has needed a proper NFS lock manager for many years. If Linux could duplicate its functionality, it would put a LOT of Solaris NFS servers out to pasture.
Software developers who work at home
(well at least the part about parking spots)
"about a decade ago."
I'm not talking about decades. I'm talking about today, tomorrow, next week, next year.
Maybe you missed the part where I said "for now".
It's economic feasability, too. Rotating media is roughly $100/terabyte, it's gonna take more than one breakthrough for SSD to come close to that.
Nifty new technology doesn't get bought because it's nifty-new, it gets bought because it fills the need better than its predecessor for the price.
And YES there are plenty of applications where multiple terabytes are necessary, maybe not on your home system.
In case you're wondering, I have both on my system: / is SSD, /home is multi-terabyte RAID. Rotating mechanical media is sticking around at least for now.
Sure they are cool and retro and all that, but what are/were they actually good for? I mean activities that one might actually get paid for.
The only time I ever saw an Amiga actually doing something useful was at a live show, where an Amiga was used to generate the (admittedly cool looking) video images projected behind the performers. Everything else seems to be just games and standard applications available on any normal computer.
That guy is a walking train wreck, I worked with him long ago.
I can't believe anybody would do business with him. There must be a lot of gullible fools out there.
Are you serious?
In the course of an entire web session's worth of CPU consumption, you are worried about the time taken to compare password characters? Any modern optimized processor should require one clock cycle per character.
Do you actually profile your code or do you just make funny noises? Or maybe you're running your web server on a Commodore 64?
I know a Vietnamese woman who grew up in a single-room shack, with brothers, sisters, mom and dad. Needless to say she learned about sex at a Very Early Age. She said it was perfectly common and ordinary, nobody thought twice about it.
How better to sell a product, than to know what the customer is currently buying?
In the modern days of cheap disk, big disk caches, and large ram, proper modelling is more important than strict normalization.
Back when those books were written, disk was expensive and not cached, RAM was very expensive, and machines had terrible I/O bottlenecks.. Normalization is critical under these circumstances for maximum performance.
Today, these normalization techniques will increase performance but not as much as you might think. Really it is best to concentrate efforts elsewhere, especially for a one-person shop.
All of that normalization work requires coding changes and it will undoubtedly make the code much less readable and maintainable.
For many aspects of coding, you are barking up the wrong tree. You should really concentrate your design thinking at the object persistence level instead of the database level. Use Hibernate or something similar to hide the database from your code.
Then you can take a critical look at your choices of database vendors, and you will be easily able to migrate your code the one whose product best fits your needs. You will be able to run your own benchmarks with your own data and see what will work best for you. You may even find that an object-based database will give you far better performance for the same coding effort.
Do you really think Cisco is going to be happy if their customer list falls into the hands of their competitors? If this data has profile info like "How much Cisco equipment have you bought in the last year" then it could be VERY VERY useful to their competitors.
- This code was not "cracked" it was found on google.
- MD5 is deprecated.
- The word "cyberspace" is a science-fiction invention, ill-defined.
- "military cyberspace operations" ??? Yes instead of landing on Normandy Beach, hundreds of troops and equipment will emerge from cable modems.
- William Gibson would dedicate an entire chapter in a book to denigrating the cretins who thought that this was a suitable symbol.
Tell that to the UPS delivery person.
Every Kin cell phone buyer is now locked into a (usually) 2 year contract to use and pay for a phone with no future.
What if it's "lost" or "stolen"? Insurance might cover replacement cost. If they're not making them any more, then they will have to replace it with something else.
You'll certainly be marked as a sucker when people see you with one.
"our music"
Deliberate misrepresentation of the "copyright" concept.
I read all the responses here and I think, "so that's why it's 18% and not 0%". Yes the slashdot developer crowd will keep their big monitors, but the rest of the world, that only needs an occasional glance at a monitor screen, doesn't need that expense or inconvenience.
Yeah, you let the SOFTWARE choose the paper size depending on what country you're in.
If the user is printing out standard forms to be used in shipping the last thing you want to do is let the user change the paper size.
Darwin will clean up this mess soon enough. These people will NOT be passing their curiosity onto their children.
Those are "excuses", not reasons. We are talking about Adobe, a large software company that can actually write software. They are supposed to fix things like this BEFORE stepping out onto a new platform.
Yeah and names like "IEEE 802.3" are so much better? We can go back over time to things like PCMCIA and SCSI. Give me a break. Weird names have been in tech forever.
I think the general public gave up looking for sane tech product names a LONG time ago. Nobody attaches any significance to them. Products sell and people don't care about the buzzwords as long as the product functions.
Well I wouldn't want to build Flash or Reader from scratch so what I said is true. Source is optional for yum but of course it can be required by the repository.
The nice thing about yum is you use it to update the system packages, and third parties can use the same system to update their software. All they have to do is drop a file in /etc/yum.d and their "app store" is visible to all the package installation tools.