Yeah.... I know. Information just wants to be
free.
However, AT&T (and Warner and anybody else
pushing cable), along with the state of Texas
would beg to differ with you. If you read your
service agreement, it probably explicitly says
no cable, and if you've got a free feed, some
installer screwed up and didn't install the
appropriate traps. This latter fact isn't a
defense.
In Texas, this could get you a fine or an extended
vacation at the state's expense. If you're dumb
enough to let someone pay you to do it, it becomes
2K + 2 years minimum.
By your definition, GCC is essentially
the only production quality compiler as most vendor compilers only support the processors of
their architecture.
I'm currently using the IBM AIX compiler to port
50K lines from VC++ - in a shop where all the Unix codes are GCC - because GCC will not compile it.
We've also done performance metrics and use GCC
because the cross platform compatibility is more
important than the fact it loses badly to every
vendor's compiler, performance wise.
My previous employer (Red Sky) couldn't have scheduled the interviews for the object model design phase in the time allowed.
Most of the infrastructure would have been unacceptable - we couldn't spell Linux or Apache, Solaris/and an expensive ap server was OK but we were really an NT shop.
MySQL wouldn't have passed muster. The rest of
the mess...? Don't even mention it.
A year later, Salon would have been out the better
part of a million and still not have a system.
First, the problem only happened 0.001% of the time on one particular type of query involving a particular key blend. Unless you ran extensive regression testing every f--d up release from MS, you probably wouldn't catch it. I didn't see but I suspect this was developed pre 6.5 which didn't have the bug.
Second, DBAs don't write code, at least in any shop I've ever worked. I've known developers who fancied themselves DBAs but usually knew ERStudio or some other tool.
Third, MS tried two - for the clue impaired, that's one more time than one - times to fix the problem and still couldn't get it right.
Fourth, their idiot suggestion was to essentially rewrite the app to get around the bug. Of course, that would probably trip more MS bugs and entail a complete revalidation suite. Got a few mil lying around?
Finally, the dumb Russians found the bug and can at least recover from it. We trusted the app and nuked all our backups.
Slashdot Mirror
However, AT&T (and Warner and anybody else pushing cable), along with the state of Texas would beg to differ with you. If you read your service agreement, it probably explicitly says no cable, and if you've got a free feed, some installer screwed up and didn't install the appropriate traps. This latter fact isn't a defense.
In Texas, this could get you a fine or an extended vacation at the state's expense. If you're dumb enough to let someone pay you to do it, it becomes 2K + 2 years minimum.
Don't do it
I'm currently using the IBM AIX compiler to port 50K lines from VC++ - in a shop where all the Unix codes are GCC - because GCC will not compile it.
We've also done performance metrics and use GCC because the cross platform compatibility is more important than the fact it loses badly to every vendor's compiler, performance wise.
My previous employer (Red Sky) couldn't have scheduled the interviews for the object model design phase in the time allowed.
Most of the infrastructure would have been unacceptable - we couldn't spell Linux or Apache, Solaris/and an expensive ap server was OK but we were really an NT shop. MySQL wouldn't have passed muster. The rest of the mess...? Don't even mention it.
A year later, Salon would have been out the better part of a million and still not have a system.
which really are a debt instrument of the Federal Reserve System
which really isn't part of the Federal Government
for silver. We had previously lost the right to redemption in gold in 1933.
Second, DBAs don't write code, at least in any shop I've ever worked. I've known developers who fancied themselves DBAs but usually knew ERStudio or some other tool.
Third, MS tried two - for the clue impaired, that's one more time than one - times to fix the problem and still couldn't get it right.
Fourth, their idiot suggestion was to essentially rewrite the app to get around the bug. Of course, that would probably trip more MS bugs and entail a complete revalidation suite. Got a few mil lying around?
Finally, the dumb Russians found the bug and can at least recover from it. We trusted the app and nuked all our backups.