Since you are evidently going after the Desktop market with Corel Linux, it would seem to me that one thing that every administrator needs is a good application distribution manager utility.
Something that would allow network admins to keep an image on the network of what a healthy installation looks like (for each app) and then be able to repair and dynamically reinstall programs that become damaged.
From someone who knows a good deal about both I can tell you that Python is *absolutely* the best way to go. It would immeadiately add (a la MS VBA) a powerful OO scripting language to Corel's office suite....
Related Question for Dr. Cowpland: On the question of licensing Corel Office... It seems that any company that seriously wants to take on MS will need at least 3 things. * OS * Programming Languages * Office Apps Given Suns recent purchase of StarOffice, it would seen that RedHat would be on the war path for the third item in that list right about now. (Having just gotten Cygnus and HKS). If RedHat made you an offer to purchase or license your Office Suite from you - would you consider it or reject it outright?
As someone whos done work in the financial services area I'd like to point out a few things:
1. Customer is only liable for $50 *if* its after 30 days from time a fake charge was made. If the consumer notices the charge before, then the credit card company eats the bill (and consequently puts more requirements on existing laws (see # 2) and merchants for greater secuirty)
2. Alot of these problems could be corrected with strong encryption - but since its not feasible to run a global web site with strong encryption for US users and weaker encryption for non-US...this is a mute point...But once credit card companies start losing $$$ because of this, congress will suddenly have a new outlook on the whole issue.
3. Fixed credit card numbers will be a thing of the past within the next 5 years or so.. A much better approach is to have valid session id's. That is, dynamic credit card "numbers" that are good for one transaction and one transaction only..that way if the merchant you did business with has crappy security and that information gets released to the world at large...doesn't matter because the number is no longer valid...
4. and finally, #1 was *really* put into effect by the govt (it is called Reg D) to make consumers comfortable using credit cards period. The reason for this is it makes the IRS's job much easier come audit time. Umm...you had $30k of credit card bills that all got paid last year, so now we know you made at least $30k...
Slashdot Mirror
I can see the error messages for Win2010 now:
"Error - user32.exe performed an illegal operation in this universe - please continue in another universe or restart..."
Something that would allow network admins to keep an image on the network of what a healthy installation looks like (for each app) and then be able to repair and dynamically reinstall programs that become damaged.
Anything like this in the works from corel??
From someone who knows a good deal about both I can tell you that Python is *absolutely* the best way to go. It would immeadiately add (a la MS VBA) a powerful OO scripting language to Corel's office suite....
Related Question for Dr. Cowpland: On the question of licensing Corel Office... It seems that any company that seriously wants to take on MS will need at least 3 things. * OS * Programming Languages * Office Apps Given Suns recent purchase of StarOffice, it would seen that RedHat would be on the war path for the third item in that list right about now. (Having just gotten Cygnus and HKS). If RedHat made you an offer to purchase or license your Office Suite from you - would you consider it or reject it outright?
As someone whos done work in the financial services area I'd like to point out a few things:
1. Customer is only liable for $50 *if* its after 30 days from time a fake charge was made. If the consumer notices the charge before, then the credit card company eats the bill (and consequently puts more requirements on existing laws (see # 2) and merchants for greater secuirty)
2. Alot of these problems could be corrected with strong encryption - but since its not feasible to run a global web site with strong encryption for US users and weaker encryption for non-US...this is a mute point...But once credit card companies start losing $$$ because of this, congress will suddenly have a new outlook on the whole issue.
3. Fixed credit card numbers will be a thing of the past within the next 5 years or so.. A much better approach is to have valid session id's. That is, dynamic credit card "numbers" that are good for one transaction and one transaction only..that way if the merchant you did business with has crappy security and that information gets released to the world at large...doesn't matter because the number is no longer valid...
4. and finally, #1 was *really* put into effect by the govt (it is called Reg D) to make consumers comfortable using credit cards period. The reason for this is it makes the IRS's job much easier come audit time. Umm...you had $30k of credit card bills that all got paid last year, so now we know you made at least $30k...
-deep_magic