What good does that do? The most effective worms propagate by looking at the infected computer's mail folders, then sending themselves out with an existing Subject line (prepending the Re: if it is not present) and mailing themselves to the sender and all other recipients of the message being 'cloned'.
So you don't auto-preview the message - you still see what looks like a continuation of an existing message thread, from someone you've gotten mail from, or sent to, before. And you open the message. And BAM! You're infected too.
The problem with LookOut is not auto-preview - it's the insane idea that assumes viewing an email requires opening attachments and executing arbitrary code without at a minimum asking the viewer whether he wants to execute the code before doing so.
This time, they are saying that the Sequent license means that Dynix/ptx is a derivative form of Unix, and that the leakage of the NUMA and RCU code to Linux is a violation of the license. They're not even talking about AIX this time.
They hope to get a court to rule that they do indeed own the code, and can collect lotsabux as a result, or alternatively if they don't, that can be used to attack the GPL's assertion of control over derivative works as well.
most people not only need to learn how the program works, to use any accounting software they need a tutorial in accounting 101
Absolutely. I would venture to say that the overwhelming majority of people get 'debit' and 'credit' backwards. This is most likely because of most people's exposure to accounting terms comes from having been on the receiving end of statements produced by businesses with whom they have accounts.
Once you understand the basic rules of accounting, which sound an awful lot like the laws of physics when stated thusly:
Every transaction must be balanced; one or more accounts are debited (that is a positive number) and one or more accounts are credited (negative), with the sum of all of the debits and credits in the transaction being exactly zero.
Therefore the sum of the entire Chart of Accounts
Assets (positive)
Liabilities (negative)
Equity (negative - think of it as the liability the business has to its owner)
Capital invested
Accumulated earnings (from prior periods)
Current-year Profit (negative) or Loss (positive)
= 0
Operating transactions include something from an asset or liability account and something from an income or expense account. The P/L section of the balance sheet breaks down this way:
Income (negative)
Expense (positive)
but the signs are usually omitted in the P/L (when they match the normal directions indicated here) to avoid the confusion that arises from income accounts being negative (but they must be, because an income account shows where the income came from, so going back to Rule #1 the increase in an asset must correspond to an equal and opposite negative to balance it)
OK, so it's not exactly Sesame Street, but the logic flows inexorably from Rule #1, and as long as you understand the math of negative numbers, you can get it.... The devil is indeed in the details, but Generally Accepted Accounting Practices aren't too difficult to grasp once you get these basics down
At the end of the day, though, accounting software is simply database software to keep all the accounts straight, with some pre-built reports and forms defined for you. I wonder if GNUCash is suffering from excessive complexity from having to couple the interface (that is specific to accounting) to the back end (that could be MySQL or whatever) and make a single package out of it
No, I think technically Wales is a principality, officially joined to England as a subsidiary entity by The Statute of Rhuddlan in 1284, codifying what was accomplished on the battlefield two years earlier. The Union Jack of the UK is formed from individual flags of the three kingdoms (although the Irish abandoned the Cross of St. Patrick in favor of their current tricolor when the Republic was formed) with no reference to Wales whatsoever.
US and UK - separated by a common language
on
Flavor vs. Flavour
·
· Score: 0, Flamebait
So let's not excuse the bizarre US spelling by saying it uses up less space
Why is the US spelling 'bizarre'? I wonder if English towns have 'mayours', and whether someone peddling his goods is a 'vendour'? American English is in this respect just a bit more consistent in its evolution from under the French influence.
Besides, if it weren't for the US, you'd probably be spelling it '(das) Aroma' anyway.
In the situation where the spammer gets paid by hit, the spammer would be rich overnight. But, then the customer might see somthing a little fishy, then start asking questions.
So you're saying that the long-term effect would be to destroy the spammers' business model?
Looking for a downside to this plan . . . still looking . . . Nope. I can't see one.
evolved into a case about the GPL, probably due to MS's insistence
Yep. MS wants to paint this picture of the GPL. They'll spin it like Professor Harold Hill himself...
Well, ya got trouble, my friend. Right here, I say trouble right here in Silicon Valley Why, sure, we're a software company Certainly mighty proud to say, I'm always mighty proud to say it I consider the hours we spend with code on our screens are golden Help you cultivate horse sense and a cool head and a keen eye Didja ever take an' try an' give an iron clad leave to yourself from Scalable Multiprocessing? But just as I say it takes judgement, brains and maturity to test and debug Enterprise Software with full Code Review I say that any boob can take and shove C source in the GCC compiler And I call that sloth, the first big step on the road to the depths of degreda- I say, first- medicinal wine from a teaspoon, then beer from a bottle And the next thing you know your son is hackin' Distributed Denial of Service Attacks. and listenin' to some big pseudonymous script kiddie Hear him tell about mp3 downloadin' Not a wholesome CD, no, but a compressed format where the entire _player_ can be smaller than the smallest disk. Like to hear some disposable Ko-rean hardware playin' Mozart? Make your blood boil, well I should say Now, folks, let me show you what I mean You got zero, through twelve - that's THIRTEEN terms and conditions in the 'Public License'. Terms that mark the difference between a gentleman and a bum With a capital 'B' and that rhymes with 'G' and that stands for 'GNU'
And all week long, your Silicon Valley programmers'll be fritterin' away I say, your coders'll be fritterin' Fritterin' away their noontime, suppertime, WORKtime, too Run the code through the compiler Never mind gettin' Digital Rights Management implemented or the security holes in Outlook patched or Total Information Awareness connected Never mind filing for any patents 'til the software industry is caught with an IP portfolio empty and no one to sue and that's trouble Oh, ya got lots and lots o' trouble I'm thinkin' of the kids in the cargo pants, young ones learnin to install Linux on their Game Boys after school Ya got trouble, folks, right here in Silicon Valley with a capital 'T' and that rhymes with 'G' and that stands for 'GNU'
Oh, we got trouble Right here in Silicon Valley Right here in Silicon Valley With a capital 'T' and that rhymes with 'G' That stands for 'GNU' We surely got trouble We surely got trouble Right here in Silicon Valley Right here
Gotta figure out a way to keep customers paying dues . . .
I see this "lab" only producing... whitepapers where Microsoft.... wins!
In a roundabout way, sure. I expect MS to look VERY carefully at what Linux can do for them. They've already taken the BSD TCP stack....
What's to keep them from pulling an Apple Maneuver and making a version of Windows that runs totally on top of a fork (containing serious DRM mods, naturally) of BSD? With Personality Modules that let you run Classic Windows programs (and device drivers? A better WINE than WINE?) as well as proprietary binaries compiled for Linux. If necessary, they could have portions of the OS that are GPL'ed (although I'm sure they want to test whether BSD code is good enough) but these extra PMs technically licensed separately. One of the things the SCO tactics will test is just how 'viral' various licenses are. In the meantime, if they can figure out the technical aspects to making money off Open Source, whichever way the legal winds blow, they'll have a plan in place to exploit it.
So, don't be surprised if a whitepaper comes out talking about certain advantages that certain OS designs have, ultimately translating to:
"Aw, shucks, if you can't beat 'em, join 'em!" (Embrace)
"We believe that we can improve on these open source implementations to protect against {hackers|pirates|terrorists}" (Extend}
Except in this case they all had the same hardware on each machine...
That is frankly impossible. Even though the machines were supposed to be identical:
Upon testing with hdparm, it was apparent that this machine was having troubles setting above udma2. Eventually this problem was traced to the HD cable, a salutary lesson in the
variability of identical hardware setups.
This is just the difference they caught. Who knows how many other subltle variations exist between nominally identical machines? An honest attempt to determine how fast 3 distros do the same thing would be to really use the same hardware, by running the tests on one or more machines with one distro, then wiping the HDs and installing the second and repeating the tests, then on to the third.
The only way to have the same hardware is to use the same machine for each distro. Period.
Have you ever tried parsing XML in order to read in one piddly little fucking config file?
I didn't say to make the config file be in XML. I said to make the Model be in XForms, so that a consistent front end can be used for everything. You can still have your config file with colon-delimited fields in linefeed-delimited records, or linefeed-delimited fields in double-linefeed-delimited record, or whatever you want. Existing config tools that use sed / grep / awk / perl / ruby / python / <your favorite scripting language here> just keep working the way they already do
The XML is a metaconfiguration file, which tells the front end how to deal with the config file for the application, so that it is not necessary to write a GUI front end for everything, and have users learn how to interact with each one's peculiarities. You just write the Model that describes the form, and backend code that manipulates the config file into the right format.
It bears repeating, but XML is not really a document storage format; it's a document interchange format. That Open Office uses gzipped XML indicates they're more interested in the interchange than the storage; I tend to agree with them on this. I'm talking about using XForms to facilitate the interchange between the user and the program configuration.
One of the biggest problems with running Linux for non-geeks is configuration. Every app has its own.appnamerc or appname.conf with its own peculiar syntax and options. Now that we have a standard for filling out forms, we can build the infrastructure for a single front end to them all.
To enable Web content developers to meet these challenges XForms will be designed to cleanly distinguish between form
instance data, form description (called the em>XForms Model), and form presentation (called the XForms User Interface).
So, for each *rc or *conf file, we need an XForms Model that describes the form and how to validate it, and an X-forms-aware UA like Mozilla (but you can't get there from here!), or perhaps on the server side through Apache and Cocoon's XMLForm to handle the work of getting the input. XForms can become the glue that holds Linux together.
When users can right-click on something, select Properties from the menu, and configure it in a consistent interface, one of the biggest impediments to Linux use by non-techies will be removed.
If you're doing something for profit, it's by definition not fair use.
Then Cringely is wrong in one regard. Instead of being a for-profit entity, Snapster needs to be incorporated as a not-for-profit! Any funds it collects from its members must be poured back into acquiring more CDs, bigger hard drives, and purchasing insurance to pay legal expenses in the event of action against it.
If you have to reinstall Windows, it'll kill your existing Linux partition because it will overwrite the drive with its image.
I wonder about that. If you boot to Linux and mess with the MBR to show the entire disk occupying just the cylinders of the NTFS partition, and go into the BIOS to show that same number of cylinders, it might just leave the rest alone.
On my desktop box, when I reinstalled XP, reformatted both NTFS partitions, but left the ext3, FAT32 and swap the heck alone.
The logical conclusion of the Tao of Unix
on
State Of The Filesystem
·
· Score: 4, Interesting
Reiser's vision of files that are also directories, and putting metadata into files, is just the logical perfection of the fundamental *nix notion that 'everything is a file'. It is this which has given the OS such strength for three decades - before anyone knew about 'object-oriented programming', Unix was behaving in an o-o manner at the macro level, with individual programs doing encapsulation, etc. Having plugins that expose the details as ordinary files, allowing you to access information with your editor of choice, as well as scripting tools such as sed, grep, awk, perl, or Python is what Unix is all about.
The only thing I'm concerned about is backward compatibility - if someone accidentally tries to open a file with a trailing slash, and gets an error because now it's a directory, then it's a Bad Thing.
It sounded so intelligent until he started playing
on
State Of The Filesystem
·
· Score: 3, Funny
sure, im going to listen to this guy about filesystem implementation when he cant even set up MIME types on his webserver.
or spell: (emphasis mine)
If you just want to
give them some default settings,have that line below their home directory's line.
Viola! Lock down framework.
I know we hackers like to, uh, fiddle with our computers...
How about an implementation that doesn't tie you down to any single platform?
Like, say, an SSL-encrypted session with simple HTML <form> structure? That would not only be platform-independent, but should be accessible to disabled voters as well.
And that's just off the top of my head. Maybe it's from reading the Software Sharecropping article that mentions the liberating influence of browser-based user interfaces. Nothing for anyone to 'download and install' - just email the voters a link they can click on.
When my daughter logs into Linux on this PC, her.bashrc starts up her own personal X server - I can flip between her desktop and mine (if I'm in X) with Ctrl-Alt-F7/8, and all of our programs continue to run just fine. Been doing this even before WinXP made it popular with the point-n-grunt crowd
Finally, I think the author does an even greater disservice, and exposes his bias, by referring to sharecroppers in a derogatory manner.
He does no such thing. He recognizes that sharecroppers are in a very weak position, and if anything empathizes with them. If a sharecropper doesn't produce much, he suffers. If he does, then the land owner figures out that the land is too good to let the sharecropper take his cut from it, and either kicks the sharecropper out or renegotiates the percentages so that the sharecropper stays just at subsistence.
Also, it's a historical fact that most sharecroppers were African American,
Yeah. Working on the Boss Man's land and watching him get the benefits was something recently-freed slaves were used to. Sharecropping isn't outright slavery, but it certainly isn't true independence either. For people who had spent their entire lives being told they were The Man's property, it's about the best that can be expected. As Malik (Malcolm) X. Shabazz put it so well, when you can put chains on a man's mind, and get him to accept his low status, you don't need to put any on his body. That's why he was killed. An intelligent, articulate advocate who preaches to the downtrodden that they have to take the responsibility to improve themselves (starting with their own mental state) is just too damn dangerous for the elites to stand.
The author is telling Software Sharecroppers that they do not deserve to be treated the way they are - they are not Microsoft's/Apple's/whoever's n-----s. And there is not a damn thing racist about it, either. Unless you agree with the idea that there are some people who just deserve second-class citizen status structly on the basis of ethnicity. Discussing the fact that people are racists is not racist.
But nobody really noticed until we came to expect instant internet access to government information, since all local governments have copies of the copyrighted building codes available for inspection in the office.
Long before I heard of the Internet, I thought this was suspect. I don't know how it is in other states, but in KS the only reason a lot of county newspapers stay in business is because of a state law that requires publication of certain legal documents, including every new local ordinance, in the 'official county newspaper'.
When dealing with such a complex subject as building codes, having the county/city buy a few copies for the courthouse/city hall and a few more for each library, and 'incorporating by reference' made some kind of sense. But now we have the technology to communicate law for virtually zero transaction cost, so I propose this simple idea for governments to consider enacting if they want to open up the whole business of law to make it accessible to the citizenry:
Every
proposed law (bill/resolution/etc), when first introduced by a member of the legislative body, must be submitted in a well-defined markup language - I'm thinking XHTML - to show the exact text of the proposal and track any amendments as they are attached using span classes that show every jot and tittle that's altered, when, by what vote... When the law is passed, the document is cryptographically signed by the presiding officer of the legislative body - when the executive has the power to approve or veto with a pen and ink, he also applies an electronic signature to the bill
And the entire base of existing law must be transcribed into such a format within 5 years. Then do the same with administrative regulations promugated by agencies, with hyperlinks back to the law that gave them the power to promulgate. And all the judicial decisions. ..
Making the law open to the people electronically will be far cheaper and effective than doing it by just printing fat books that sit in law libraries.
I have no doubt that Michigan will take the position that it has personal jurisdiction over any person or company that intentionally sends e-mail to Michigan residents in violation of the statute. I have little doubt that the courts will uphold this assertion of jurisdiction. Traditionally, when a business specifically solicits business in a state via mail or advertising specifically targeted to residents of the state (e.g., advertising in local newspapers, local TV and radio stations, etc.)it is held to have submitted to personal jurisdiction in that state.
Unless and until the State of Michigan applies this law exclusively to email addresses in the.mi.*.us domains, your logic does not apply. Just as an advert that's placed with the network, even though it's carried on MI stations, is not specifically targeting MI, an email address that does not self-identify as being under MI jurisdiction is not 'targeted'.
Like it or not, there really is no way that state law can govern email that is carried over the Internet originally built by the Department of Defense - this is going to be a Federal law or it will be shot down.
I can't even refer to this as "compression" with the quotes, because it isn't compression - it's higher data density. It's no more compression than using 1.44 MB floppies instead of 720K, or 2.88 instead of 1.44.
And that's the main reason why this probably won't go anywhere. Doubling data density from 720K to 1.44 M was accepted by the marketplace because the 720's hadn't really become dominant over the 5.25" formats yet. OTOH, the 2.88 couldn't put a dent in 1.44 because just doubling the density isn't enough to get people to pay for drives that support it, and until a substantial percentage of drives do, nobody would want to use the format. We can move along to DVDs for a big gain in density, once we have standards (to give people the confidence that other drives will support the format, once again).
Slashdot Mirror
So you don't auto-preview the message - you still see what looks like a continuation of an existing message thread, from someone you've gotten mail from, or sent to, before. And you open the message. And BAM! You're infected too.
The problem with LookOut is not auto-preview - it's the insane idea that assumes viewing an email requires opening attachments and executing arbitrary code without at a minimum asking the viewer whether he wants to execute the code before doing so.
They hope to get a court to rule that they do indeed own the code, and can collect lotsabux as a result, or alternatively if they don't, that can be used to attack the GPL's assertion of control over derivative works as well.
Once you understand the basic rules of accounting, which sound an awful lot like the laws of physics when stated thusly:
- Every transaction must be balanced; one or more accounts are debited (that is a positive number) and one or more accounts are credited (negative), with the sum of all of the debits and credits in the transaction being exactly zero.
- Therefore the sum of the entire Chart of Accounts
- Operating transactions include something from an asset or liability account and something from an income or expense account. The P/L section of the balance sheet breaks down this way:
OK, so it's not exactly Sesame Street, but the logic flows inexorably from Rule #1, and as long as you understand the math of negative numbers, you can get it.... The devil is indeed in the details, but Generally Accepted Accounting Practices aren't too difficult to grasp once you get these basics down-
Assets (positive)
- Liabilities (negative)
- Equity (negative - think of it as the liability the business has to its owner)
- Capital invested
- Accumulated earnings (from prior periods)
- Current-year Profit (negative) or Loss (positive)
= 0- Income (negative)
- Expense (positive)
but the signs are usually omitted in the P/L (when they match the normal directions indicated here) to avoid the confusion that arises from income accounts being negative (but they must be, because an income account shows where the income came from, so going back to Rule #1 the increase in an asset must correspond to an equal and opposite negative to balance it)At the end of the day, though, accounting software is simply database software to keep all the accounts straight, with some pre-built reports and forms defined for you. I wonder if GNUCash is suffering from excessive complexity from having to couple the interface (that is specific to accounting) to the back end (that could be MySQL or whatever) and make a single package out of it
Besides, if it weren't for the US, you'd probably be spelling it '(das) Aroma' anyway.
Looking for a downside to this plan . . . still looking . . . Nope. I can't see one.
Well, ya got trouble, my friend.
Right here, I say trouble right here in Silicon Valley
Why, sure, we're a software company
Certainly mighty proud to say,
I'm always mighty proud to say it
I consider the hours we spend with code on our screens are golden
Help you cultivate horse sense and a cool head and a keen eye
Didja ever take an' try an' give an iron clad leave
to yourself from Scalable Multiprocessing?
But just as I say it takes judgement, brains and maturity
to test and debug Enterprise Software with full Code Review
I say that any boob can take and shove C source in the GCC compiler
And I call that sloth,
the first big step on the road to the depths of degreda-
I say, first- medicinal wine from a teaspoon,
then beer from a bottle
And the next thing you know your son is hackin'
Distributed Denial of Service Attacks.
and listenin' to some big pseudonymous script kiddie
Hear him tell about mp3 downloadin'
Not a wholesome CD, no, but a compressed
format where the entire _player_ can be smaller than the smallest disk.
Like to hear some disposable Ko-rean hardware playin' Mozart?
Make your blood boil, well I should say
Now, folks, let me show you what I mean
You got zero, through twelve - that's THIRTEEN terms and conditions in the 'Public License'.
Terms that mark the difference between a gentleman and a bum
With a capital 'B' and that rhymes with 'G' and that stands for 'GNU'
And all week long, your Silicon Valley programmers'll be fritterin' away
I say, your coders'll be fritterin'
Fritterin' away their noontime, suppertime, WORKtime, too
Run the code through the compiler
Never mind gettin' Digital Rights Management implemented or the security holes in Outlook patched
or Total Information Awareness connected
Never mind filing for any patents 'til the software industry is caught
with an IP portfolio empty and no one to sue and that's trouble
Oh, ya got lots and lots o' trouble
I'm thinkin' of the kids in the cargo pants,
young ones learnin to install Linux on their Game Boys after school
Ya got trouble, folks, right here in Silicon Valley
with a capital 'T' and that rhymes with 'G' and that stands for 'GNU'
Oh, we got trouble
Right here in Silicon Valley
Right here in Silicon Valley
With a capital 'T' and that rhymes with 'G'
That stands for 'GNU'
We surely got trouble
We surely got trouble
Right here in Silicon Valley
Right here
Gotta figure out a way to keep customers
paying dues
. . .
What's to keep them from pulling an Apple Maneuver and making a version of Windows that runs totally on top of a fork (containing serious DRM mods, naturally) of BSD? With Personality Modules that let you run Classic Windows programs (and device drivers? A better WINE than WINE?) as well as proprietary binaries compiled for Linux. If necessary, they could have portions of the OS that are GPL'ed (although I'm sure they want to test whether BSD code is good enough) but these extra PMs technically licensed separately. One of the things the SCO tactics will test is just how 'viral' various licenses are. In the meantime, if they can figure out the technical aspects to making money off Open Source, whichever way the legal winds blow, they'll have a plan in place to exploit it.
So, don't be surprised if a whitepaper comes out talking about certain advantages that certain OS designs have, ultimately translating to:
The only way to have the same hardware is to use the same machine for each distro. Period.
The XML is a metaconfiguration file, which tells the front end how to deal with the config file for the application, so that it is not necessary to write a GUI front end for everything, and have users learn how to interact with each one's peculiarities. You just write the Model that describes the form, and backend code that manipulates the config file into the right format.
It bears repeating, but XML is not really a document storage format; it's a document interchange format. That Open Office uses gzipped XML indicates they're more interested in the interchange than the storage; I tend to agree with them on this. I'm talking about using XForms to facilitate the interchange between the user and the program configuration.
One of the biggest problems with running Linux for non-geeks is configuration. Every app has its own .appnamerc or appname.conf with its own peculiar syntax and options. Now that we have a standard for filling out forms, we can build the infrastructure for a single front end to them all.
So, for each *rc or *conf file, we need an XForms Model that describes the form and how to validate it, and an X-forms-aware UA like Mozilla (but you can't get there from here!), or perhaps on the server side through Apache and Cocoon's XMLForm to handle the work of getting the input. XForms can become the glue that holds Linux together.When users can right-click on something, select Properties from the menu, and configure it in a consistent interface, one of the biggest impediments to Linux use by non-techies will be removed.
The advantage of Anonyx is that it's binary-compatible with Linux applications, but it's called 'Anonyx', so it isn't Linux.
On my desktop box, when I reinstalled XP, reformatted both NTFS partitions, but left the ext3, FAT32 and swap the heck alone.
The only thing I'm concerned about is backward compatibility - if someone accidentally tries to open a file with a trailing slash, and gets an error because now it's a directory, then it's a Bad Thing.
And that's just off the top of my head. Maybe it's from reading the Software Sharecropping article that mentions the liberating influence of browser-based user interfaces. Nothing for anyone to 'download and install' - just email the voters a link they can click on.
When my daughter logs into Linux on this PC, her .bashrc starts up her own personal X server - I can flip between her desktop and mine (if I'm in X) with Ctrl-Alt-F7/8, and all of our programs continue to run just fine. Been doing this even before WinXP made it popular with the point-n-grunt crowd
The author is telling Software Sharecroppers that they do not deserve to be treated the way they are - they are not Microsoft's/Apple's/whoever's n-----s. And there is not a damn thing racist about it, either. Unless you agree with the idea that there are some people who just deserve second-class citizen status structly on the basis of ethnicity. Discussing the fact that people are racists is not racist.
When dealing with such a complex subject as building codes, having the county/city buy a few copies for the courthouse/city hall and a few more for each library, and 'incorporating by reference' made some kind of sense. But now we have the technology to communicate law for virtually zero transaction cost, so I propose this simple idea for governments to consider enacting if they want to open up the whole business of law to make it accessible to the citizenry:
Making the law open to the people electronically will be far cheaper and effective than doing it by just printing fat books that sit in law libraries.Like it or not, there really is no way that state law can govern email that is carried over the Internet originally built by the Department of Defense - this is going to be a Federal law or it will be shot down.
I do not like pop-ups and spam
I do not like them, Sam-I-Am!
I will not click them with my mouse
Nor will my daughter, dog, or spouse
I do not like them with Slashdot
I don't like them on any spot
I don't like them, no Sir! - no ma'am!
I do not like pop-ups and spam
I don't like your E-U-L-A
This is a game I will not play
Don't like them in the spring or fall
I do not like them, not at all
I do not like pop-ups and spam
I do not like them, Sam-I-Am!
And that's the main reason why this probably won't go anywhere. Doubling data density from 720K to 1.44 M was accepted by the marketplace because the 720's hadn't really become dominant over the 5.25" formats yet. OTOH, the 2.88 couldn't put a dent in 1.44 because just doubling the density isn't enough to get people to pay for drives that support it, and until a substantial percentage of drives do, nobody would want to use the format. We can move along to DVDs for a big gain in density, once we have standards (to give people the confidence that other drives will support the format, once again).