I'm frequently a person who fills out the original forms on the vendor site, but then doesn't proceed to the download, or to the install. My 4 biggest turnoffs are:
1. When it comes time to do the download, the site doesn't respond to my browser, is extremely slow, demands security be turned off, or shows errors. This happens very often.
2. If during the install, the registration / activation requires an analog phone-line, I'll cancel the install and remove the software.
3. If during the install, the package insists that I turn off my virus checkers, its gone.
4. After the install, if there isn't a de-install available, I revert the system.
With the single exception of potentially higher speed, which also requires all hierarchical access code to follow the structure carefully, relational still has facilities untouchable by other structures.
The commonest strength is not simply the way relational handles many-to-many, but the simple extension of recursive relationships in which relational is one of the few paradigms with this ability.
Relational also supports the network model, again another major weak area in the heirarchical model. I've yet to come across a potential database structure that I can't handle relationally; that is absolutely not true for every other paradigm.
Well, I've never used my CD R/W devices for anything but backups, and archives, and under one contract, legally burning copies of software for the copyright owner.
I'm Canadian, and absolutely refuse to by any Canadian music produced by Canadians, because of the government subsidies. Accordingly, I totally resent both the Canadian Government and the Canadian Music Industry for getting even 1 penny of the cost of my blank CDs.
Damned eastern Canadians love government and either hate or are unwilling to accept responsibility for themselves.
I just don't see how people don't get it. You haven't paid the least attention to the case I originally gave... the encrypted (possibly) cell phone does the communications... the heck with blue tooth all over the place. You're one of those who tries to treat bluetooth and wireless lan the same. If you don't understand the purpose of the technology, then try to learn about it. And this is at a fraction the cost and many times the reliability of your idea of bluetooth and camera coverage all over a city (which is likely an impossible task in any case).
What I'm talking about works reliably and inexpensively in every trial where there's been an understanding of the keyword 'LOCATION'.
Yeah, just like now. The cop ends up out of sight of the camera in the front of his car, and gets shot, and no one knows where he is. Get real, huh? Or alternatively he gets out of sight of his car's camera, and pockets some drugs... and again society gets screwed.
Radio is NOT more relible / useful. Think about the big picture of why we have cops, and maybe, just maybe you'll understand that technology can provide useful benefits to society.
I'm surprised at the majority of comments that show no understanding of the problems that BlueTooth tries to address, versus the problems of Wireless Lans.
The key to wireless (read BlueTooth enabled) computing is location... knowing where you are in the world. Think through the following not very hypothetical scenario...
A beat cop on patrol, with a voice-activated cell-phone, attached to his left lapel, with a headset in his ear (no wire connection courtesy of BlueTooth). A GPS transponder inside his uniform jacket lining, also bluetooth connected to his Palm-like display and note device.
A vidcam on his right lapel, again bluetooth enabled. Suddenly he is totally connected thru his cell to the Police Department servers. Now, 911 support can properly locate potential service providers, communicate, show maps,,etc. and on the obverse side, with always on communications via his cell his own activities are always being recorded / saved. This feels to me like an order of magnitude increase in protection to both the cop and to the public.
Without BlueTooth, or something else VERY similar (not 802.x), this scenario becomes impossible.
Bluetooth is aimed at making personal computing totally location independent. It supports mobile computing in a true sense, whereas 802.x supports mobile computing when the momentary location is stationary.
So, it appears that in some countries, vigilantes and snitches are encouraged throughout the system, eh? Oh well, I guess I'll never do business in Deutchland again.
Well, there's still a vastly different standard. In Canada, where I live, 'truth' is an absolute defence against libel or slander suits. This isn't true in many countries, and even in some U.S. states.
Are you really suggesting that I should live down to some other jurisdictions statutes which imply that fair and accurate comment which MAY injure someone's reputation is actionable? No thanks, I can't live by your standards, which imply very little except a stifling of free speech (of which Canada actually has very little).
In my opinion, it most definitely can be, if the business requirements are used as a primary factor in the database engine selection;
1. Availability: how crash-proof is the RDBMS is 1 part of the equation. Another is the ability to backup and recover the db. In a 24x7x52 shop, you virtually never get the opportunity to shut down the DB. A simple file or filesystem backup will NEVER let you recover a transaction-consistent system. Also, how well does the engine support high-availability clusters, with automatic replicatin and hot-standby servers.
2. Performance: This is the 1 area where no product is perfect, but the tier-1 products such as Oracle & DB2 particularly excel... dynamic tuning, and those dreaded vendor-specific extensions are often used in support of this area. In a modern enterprise, expect millions of transactions (each transaction could be updating 30 tables, with several hundred rows) on an hourly or daily basis.
Application availability: A company doesn't purchase a database just to have a database, anymore than they should purchase hardware or an OS for their own sake. There are more applications such as ERP and CRM, as well as many client-server and two-tier apps written to support the tier-1 engines.
Scalability: Its fine to cluster servers; I wouldn't want to tailor postgres or mysql to distribute my database on many servers in a number of different geographic areas. Tier-1 vendors have addressed this in the vendor-specific tools (although ANSI 92 attempts to incorporate many of the special features). Size is another factor; can the engine process terabytes as easily as gigabytes? If you have a server with 20GB RAM, will the database take advantage by caching objects (either automatically or by administrative instruction)?
Support: While support contracts CAN be purchased to support most anything, can you call the vendor at 8am Xmas day with an issue that has caused the database to crater? I know from personal experience that Oracle provides that level of support with reasonable expertise available.
Features: While this is a double-edged sword, can the database support all of the required corporate data entities? I include single fields of 400MB (Seismic traces and well logs), as well as providing indexing strategies that reflect the application (i.e. spacial data... 3+ dimensional location data). Similarly, can I distribute my data (I'm not simply referring to tuning) so that it resides where it is required? Without thee included features, what effort must I make to program around the DB engines deficiencies (usually called 'undocumented features' by the vendor).
Cost: The support and development cost of applications for a free engine MAY actually be higher than purchase of a packaged application for an expensive db.
Security: How does one secure transactions (not just https from the web) between the visible server and the application servers and the database servers? For example, in the petrophysical world, the most dangerous information for competitors to gain is the knowledge of the latitude and longitude that a company is querying.
There are few clear-cut answers in a general sense, but I believe that it is fair to say that the more demanding the application, the higher the probabability that a high-priced RDBMS will be required.
Your point is absolutely right; that is the way a democracy works. But, it also means that anyone who finds the inconvenience, or social aspects, or costs too high for them personally can (and maybe will) refulse to live & / or work in that jurisdiction. I've often flatly refused consulting assignments in venues where smoking isn't allowed anywhere but in your own home.
As most of the electorate in any democracy is highly uninformed, the true cost of any social policy is usually unknown to most.
I'd be lost without printed manuals. I spend half of my time travelling on the airlines, and its virtually impossible to open a laptop on some flights, and a Palm does have a very limited in-RAM capability. Give me a paper manual that I can open up on a plane, or carry to the washroom with me. CD-based HTML (or preferably PDF) documents have their very valued place, but absolutely can NOT replace paper.
I think it was in 1983 that I got my own first one. Space-age looking design, one of the better keyboards ever made, A useful desktop, and AT&T Unix SVR2 which did lots of useful things in 2MB. Later on, expandable to 3.5MB, and a 67MB hard drive.
Later on, SVR2.3, with a useful C-compiler (could use it to prepare GCC and emacs. The box kept appearing in movies and TV shows, and eventually seemed to be marketed as the center of PABX systems.
2 of mine are still in regular use by friends, although their real motivation to get them from me were those many shelf-feet of the red AT&T manuals.
We're already working with the configuration of Intel Red Hat 6.0 on Intel, KDE, Oracle 8.1.5ee as the primary platform, then installed VMWare, and configured W98 and NT4sp4 server, in which we've installed SQL*Nav Dev2K, Des2K, SQLServer 7, etc. Only awkwardness is the triple key-press to get back into the Linux desktop. Everything on the one desktop, all of the tools, and the ability to have an entire network of servers and clients on the one keyboard.
I would recommend although I haven't tried it here, 1 monitor per virtual desktop (think you'd need Metro-X to do that).
Read the GPL, and then read the Corel Beta Agreement. The Corel Beta Agreement has a clause which it states that it supersedes any and all other ownership rights. The GPL takes no rights away from Corel's ability to keep secret any Corel developed software... it just makes it contrary to law to attempt to alter a copyright holder's rights. Red Hat and Caldera handle this by making a clear difference between their and other's products vs the GPL. The non-GPLed products may have any license desired. The GPL products license may NOT be altered by anyone.
Slashdot Mirror
I'm frequently a person who fills out the original forms on the vendor site, but then doesn't proceed to the download, or to the install. My 4 biggest turnoffs are:
1. When it comes time to do the download, the site doesn't respond to my browser, is extremely slow, demands security be turned off, or shows errors. This happens very often.
2. If during the install, the registration / activation requires an analog phone-line, I'll cancel the install and remove the software.
3. If during the install, the package insists that I turn off my virus checkers, its gone.
4. After the install, if there isn't a de-install available, I revert the system.
With the single exception of potentially higher speed, which also requires all hierarchical access code to follow the structure carefully, relational still has facilities untouchable by other structures.
The commonest strength is not simply the way relational handles many-to-many, but the simple extension of recursive relationships in which relational is one of the few paradigms with this ability.
Relational also supports the network model, again another major weak area in the heirarchical model. I've yet to come across a potential database structure that I can't handle relationally; that is absolutely not true for every other paradigm.
Well, I've never used my CD R/W devices for anything but backups, and archives, and under one contract, legally burning copies of software for the copyright owner.
I'm Canadian, and absolutely refuse to by any Canadian music produced by Canadians, because of the government subsidies. Accordingly, I totally resent both the Canadian Government and the Canadian Music Industry for getting even 1 penny of the cost of my blank CDs.
Damned eastern Canadians love government and either hate or are unwilling to accept responsibility for themselves.
I just don't see how people don't get it. You haven't paid the least attention to the case I originally gave ... the encrypted (possibly) cell phone does the communications ... the heck with blue tooth all over the place. You're one of those who tries to treat bluetooth and wireless lan the same. If you don't understand the purpose of the technology, then try to learn about it. And this is at a fraction the cost and many times the reliability of your idea of bluetooth and camera coverage all over a city (which is likely an impossible task in any case).
What I'm talking about works reliably and inexpensively in every trial where there's been an understanding of the keyword 'LOCATION'.
Yeah, just like now. The cop ends up out of sight of the camera in the front of his car, and gets shot, and no one knows where he is. Get real, huh? Or alternatively he gets out of sight of his car's camera, and pockets some drugs ... and again society gets screwed.
Radio is NOT more relible / useful. Think about the big picture of why we have cops, and maybe, just maybe you'll understand that technology can provide useful benefits to society.
I'm surprised at the majority of comments that show no understanding of the problems that BlueTooth tries to address, versus the problems of Wireless Lans.
... knowing where you are in the world. Think through the following not very hypothetical scenario ...
,etc. and on the obverse side, with always on communications via his cell his own activities are always being recorded / saved. This feels to me like an order of magnitude increase in protection to both the cop and to the public.
The key to wireless (read BlueTooth enabled) computing is location
A beat cop on patrol, with a voice-activated cell-phone, attached to his left lapel, with a headset in his ear (no wire connection courtesy of BlueTooth). A GPS transponder inside his uniform jacket lining, also bluetooth connected to his Palm-like display and note device.
A vidcam on his right lapel, again bluetooth enabled. Suddenly he is totally connected thru his cell to the Police Department servers. Now, 911 support can properly locate potential service providers, communicate, show maps,
Without BlueTooth, or something else VERY similar (not 802.x), this scenario becomes impossible.
Bluetooth is aimed at making personal computing totally location independent. It supports mobile computing in a true sense, whereas 802.x supports mobile computing when the momentary location is stationary.
So, it appears that in some countries, vigilantes and snitches are encouraged throughout the system, eh? Oh well, I guess I'll never do business in Deutchland again.
Well, there's still a vastly different standard. In Canada, where I live, 'truth' is an absolute defence against libel or slander suits. This isn't true in many countries, and even in some U.S. states.
Are you really suggesting that I should live down to some other jurisdictions statutes which imply that fair and accurate comment which MAY injure someone's reputation is actionable? No thanks, I can't live by your standards, which imply very little except a stifling of free speech (of which Canada actually has very little).
In my opinion, it most definitely can be, if the business requirements are used as a primary factor in the database engine selection;
... dynamic tuning, and those dreaded vendor-specific extensions are often used in support of this area. In a modern enterprise, expect millions of transactions (each transaction could be updating 30 tables, with several hundred rows) on an hourly or daily basis.
... 3+ dimensional location data). Similarly, can I distribute my data (I'm not simply referring to tuning) so that it resides where it is required? Without thee included features, what effort must I make to program around the DB engines deficiencies (usually called 'undocumented features' by the vendor).
1. Availability: how crash-proof is the RDBMS is 1 part of the equation. Another is the ability to backup and recover the db. In a 24x7x52 shop, you virtually never get the opportunity to shut down the DB. A simple file or filesystem backup will NEVER let you recover a transaction-consistent system. Also, how well does the engine support high-availability clusters, with automatic replicatin and hot-standby servers.
2. Performance: This is the 1 area where no product is perfect, but the tier-1 products such as Oracle & DB2 particularly excel
Application availability: A company doesn't purchase a database just to have a database, anymore than they should purchase hardware or an OS for their own sake. There are more applications such as ERP and CRM, as well as many client-server and two-tier apps written to support the tier-1 engines.
Scalability: Its fine to cluster servers; I wouldn't want to tailor postgres or mysql to distribute my database on many servers in a number of different geographic areas. Tier-1 vendors have addressed this in the vendor-specific tools (although ANSI 92 attempts to incorporate many of the special features). Size is another factor; can the engine process terabytes as easily as gigabytes? If you have a server with 20GB RAM, will the database take advantage by caching objects (either automatically or by administrative instruction)?
Support: While support contracts CAN be purchased to support most anything, can you call the vendor at 8am Xmas day with an issue that has caused the database to crater? I know from personal experience that Oracle provides that level of support with reasonable expertise available.
Features: While this is a double-edged sword, can the database support all of the required corporate data entities? I include single fields of 400MB (Seismic traces and well logs), as well as providing indexing strategies that reflect the application (i.e. spacial data
Cost: The support and development cost of applications for a free engine MAY actually be higher than purchase of a packaged application for an expensive db.
Security: How does one secure transactions (not just https from the web) between the visible server and the application servers and the database servers? For example, in the petrophysical world, the most dangerous information for competitors to gain is the knowledge of the latitude and longitude that a company is querying.
There are few clear-cut answers in a general sense, but I believe that it is fair to say that the more demanding the application, the higher the probabability that a high-priced RDBMS will be required.
Bill
Your point is absolutely right; that is the way a democracy works. But, it also means that anyone who finds the inconvenience, or social aspects, or costs too high for them personally can (and maybe will) refulse to live & / or work in that jurisdiction. I've often flatly refused consulting assignments in venues where smoking isn't allowed anywhere but in your own home.
As most of the electorate in any democracy is highly uninformed, the true cost of any social policy is usually unknown to most.
Maybe I should place my personal copies ... hard-cover from 1975 up for bid?
I'd be lost without printed manuals. I spend half of my time travelling on the airlines, and its virtually impossible to open a laptop on some flights, and a Palm does have a very limited in-RAM capability. Give me a paper manual that I can open up on a plane, or carry to the washroom with me. CD-based HTML (or preferably PDF) documents have their very valued place, but absolutely can NOT replace paper.
I think it was in 1983 that I got my own first one. Space-age looking design, one of the better keyboards ever made, A useful desktop, and AT&T Unix SVR2 which did lots of useful things in 2MB. Later on, expandable to 3.5MB, and a 67MB hard drive.
Later on, SVR2.3, with a useful C-compiler (could use it to prepare GCC and emacs. The box kept appearing in movies and TV shows, and eventually seemed to be marketed as the center of PABX systems.
2 of mine are still in regular use by friends, although their real motivation to get them from me were those many shelf-feet of the red AT&T manuals.
I can show working code using Y2K windowing that I wrote in 1969. Maybe I should get a lawyer and take over the patent, huh?
Does the U.S. government really hire as many morons as us 2nd world countries?
Bill
We're already working with the configuration of Intel Red Hat 6.0 on Intel, KDE, Oracle 8.1.5ee as the primary platform, then installed VMWare, and configured W98 and NT4sp4 server, in which we've installed SQL*Nav Dev2K, Des2K, SQLServer 7, etc. Only awkwardness is the triple key-press to get back into the Linux desktop. Everything on the one desktop, all of the tools, and the ability to have an entire network of servers and clients on the one keyboard.
I would recommend although I haven't tried it here, 1 monitor per virtual desktop (think you'd need Metro-X to do that).
Bill
Read the GPL, and then read the Corel Beta Agreement. The Corel Beta Agreement has a clause which it states that it supersedes any and all other ownership rights. The GPL takes no rights away from Corel's ability to keep secret any Corel developed software ... it just makes it contrary to law to attempt to alter a copyright holder's rights. Red Hat and Caldera handle this by making a clear difference between their and other's products vs the GPL. The non-GPLed products may have any license desired. The GPL products license may NOT be altered by anyone.
To add insult to injury, looks like a Microsnot lover got at the site!