This sequence of events is starting to remind me of Ross Perot on Larry King Live, and the Saturday Night Live that made fun of it. In. Out. In. Out. Take Orders. Cancel Orders. Reinstate Orders. Re-cancel Orders.
"The Millionaire Next Door" is a get rich SLOW book, not a get rich quick book. It's worth a read, although to assist you in the process of getting rich slow, I suggest you borrow it instead of buying it.:-)
The ironic thing is that the book probably caused the author(s) to get rich quick.
Actually, it's probably even more slanted than the study data indicates, because bright, rich criminals are probably also better at not getting caught in the first place (and therefore not being data points).
Actually, what I think he was trying to say was that although the Vietnam experience was unpleasant in oh so many ways, it did in fact acheive its underlying purpose... halting the spread of the Soviet Union's sphere of influence.
For security reasons, the article is IMHO completely wrong.
Microsoft "slipstreams" security fixes, etc. in to Service Packs - each new service pack closes various security holes, hopefully without opening new ones.
Is it a good idea to suffer from an intrusion do to a security hole before you fix it? Do you need to personally understand every security hole before you know you need to patch it? No and no.
What about if the RAID is something simple like RAID-1 (mirroring), with essentially no performance penalty on writing, and a speedup on reading?
It seems to me that doing a big Oracle system (with the dozen or more recommended seperate drives) without RAID would be a bad idea from an uptime point of view. Even if you can recover to the last millisecond, the odds of one of those drives dying (and requiring that the system be down to rebuild) is just too high.
How is it implemented in Oracle? Is it the default, always-on mode of operation?
I read somewhere that Oracle can do a form of MVCC, but in that mode of operation it is drastically slower due to implementing MVCC in an inefficient mannet, something having to do with transaction logs.
(Of course, I don't recall the source, and it could be completely inaccurate.)
I think you are unfortunately quite wrong. I believe the Space Shuttle takes off vertically, then rotates around and pitches "up" (which is actually down) almost immediately after it leaves the pad. This is apparently very similar to what other rockets do as well.
Physics class is but a fuzzy memory to me, but I am under the fading impression that fully enclosing something in a conductive metal box will keep all magnetic fields in/out. I don't think it has to be particularly thick. I also don't recall it having to be ferrous.
(I would appreciate if someone who knows what they are talking would correct me if I am wrong...)
>> its not something easy to sum up in a few words
Sure it is:-)
MVCC is a Very Good Thing, and is really the right way to implement multi-user concurrency; remarkably the high-dollar databases don't do it, probably because doing so would be a major change from their locking-based legacy designs. (Interbase does it, BTW)
I always get a chuckle out of the following two facts (about Win NT):
1) Many book, and many MS TechNet articles, have a very ominous warning along the lines of "don't edit the registry"
2) There are hundreds of very important administrative tasks that are performed by editing the registry... tasks that could have had a GUI, but for whatever reason do not.
If thus stuff about quantum whatever turns out to be true, then in a few years, 2048 bits won't seem like a very big key.
Are the algoritms and piece of software used for encryptions (PGP, RSA, etc.) able to trivially scale to an arbitrarily large # of bits? It might be a good idea to start thinking of 10,000 bit keys.
If "people kill all the XXXX" can be considered part of natural selection, then it only seems fair that "later people dig up some DNA and somehow come up with more XXXX" should also be considered part of natural selection.
Hmm. It's not as pure as you make it sound. Borland extended the Pascal language with a specific contruct to handle Windows messages (the message keyword), so in this sense, even the language itself is Windows-oriented. The VCL of course it full of code that calls the Win API, and is therefore quite specific to that API.
Nonetheless, the VCL is an elegant and effective wrapper, much, much nicer than MFC.
I believe you would find this to not be the case with Delphi in particular. The IDE produces rather minimal code anyway, and Delphi app GUIs are remarkably well-behaved "out of the box".
I think it would be reasonable to assume that, like bureaucracies everywhere, over time the effective purpose of these agencies evolves towards self-perpetuation.
*** The problem I see is that in any job where you're working on classified material you can't tell anyone about it. That would suck, to find out something cool and not be able to share it.
... which would make it VERY hard to use whatever tremendously cool experience you have there to get another job - hence, it would seem like a poor career choice, except for someone who planned to stay there forever.
On a related note, the managers there obviously know that the fact that you can't talk about what you did there limits your market value. I wonder how well they pay.
The complaint is that purchasing a (closed, of course) package of cards is an act of gambling, because the cards inside may be "worth" a little or a lot. With the Beanie Babies you mention, the buyer always knows what toy they are buying before they buy it, presumably. No gamble there.
If they administrators had been thinking ahead, they would have made the badges proximity-read card (like from CheckPoint) instead... making the idea you propose here quite easy to implement.
(I agree it is inevitable, due to some reason related to the "Safety of the Children")
Slashdot Mirror
This sequence of events is starting to remind me of Ross Perot on Larry King Live, and the Saturday Night Live that made fun of it. In. Out. In. Out. Take Orders. Cancel Orders. Reinstate Orders. Re-cancel Orders.
"The Millionaire Next Door" is a get rich SLOW book, not a get rich quick book. It's worth a read, although to assist you in the process of getting rich slow, I suggest you borrow it instead of buying it. :-)
The ironic thing is that the book probably caused the author(s) to get rich quick.
That seems like a great idea.
Until you move.
(I chose my domain name on the belief that my name is quite unlikely to change.)
Actually, it's probably even more slanted than the study data indicates, because bright, rich criminals are probably also better at not getting caught in the first place (and therefore not being data points).
I suspect that the Visa and/or the merchant bank will pass the charge on to the gambling operator.
Merchant accounts usually have terms roughly like this:
"No matter what, in any case, if anything goes wrong, you the merchant will absorb the loss."
Actually, what I think he was trying to say was that although the Vietnam experience was unpleasant in oh so many ways, it did in fact acheive its underlying purpose... halting the spread of the Soviet Union's sphere of influence.
For security reasons, the article is IMHO completely wrong.
Microsoft "slipstreams" security fixes, etc. in to Service Packs - each new service pack closes various security holes, hopefully without opening new ones.
Is it a good idea to suffer from an intrusion do to a security hole before you fix it? Do you need to personally understand every security hole before you know you need to patch it? No and no.
What about if the RAID is something simple like RAID-1 (mirroring), with essentially no performance penalty on writing, and a speedup on reading?
It seems to me that doing a big Oracle system (with the dozen or more recommended seperate drives) without RAID would be a bad idea from an uptime point of view. Even if you can recover to the last millisecond, the odds of one of those drives dying (and requiring that the system be down to rebuild) is just too high.
How is it implemented in Oracle? Is it the default, always-on mode of operation?
I read somewhere that Oracle can do a form of MVCC, but in that mode of operation it is drastically slower due to implementing MVCC in an inefficient mannet, something having to do with transaction logs.
(Of course, I don't recall the source, and it could be completely inaccurate.)
Can an Oracle guru comment on this?
I think you are unfortunately quite wrong. I believe the Space Shuttle takes off vertically, then rotates around and pitches "up" (which is actually down) almost immediately after it leaves the pad. This is apparently very similar to what other rockets do as well.
Physics class is but a fuzzy memory to me, but I am under the fading impression that fully enclosing something in a conductive metal box will keep all magnetic fields in/out. I don't think it has to be particularly thick. I also don't recall it having to be ferrous.
(I would appreciate if someone who knows what they are talking would correct me if I am wrong...)
>> its not something easy to sum up in a few words
:-)
Sure it is
MVCC is a Very Good Thing, and is really the right way to implement multi-user concurrency; remarkably the high-dollar databases don't do it, probably because doing so would be a major change from their locking-based legacy designs. (Interbase does it, BTW)
I always get a chuckle out of the following two facts (about Win NT):
1) Many book, and many MS TechNet articles, have a very ominous warning along the lines of "don't edit the registry"
2) There are hundreds of very important administrative tasks that are performed by editing the registry... tasks that could have had a GUI, but for whatever reason do not.
If thus stuff about quantum whatever turns out to be true, then in a few years, 2048 bits won't seem like a very big key.
Are the algoritms and piece of software used for encryptions (PGP, RSA, etc.) able to trivially scale to an arbitrarily large # of bits? It might be a good idea to start thinking of 10,000 bit keys.
Hmmmm...
If "people kill all the XXXX" can be considered part of natural selection, then it only seems fair that "later people dig up some DNA and somehow come up with more XXXX" should also be considered part of natural selection.
Considering what happened to DIVX, I wouldn't count on widespread consumer acceptance of Video-On-Demand as a substitute for retail purchases.
** BeOS 4.0 (haven't upgraded yet)
** instaled & rebooted in about 6 minutes
6 minutes !?!?
Wow.
Not if it's YOUR T1, it's not.
I have one, and it's not for sale. :-)
Hmm. It's not as pure as you make it sound. Borland extended the Pascal language with a specific contruct to handle Windows messages (the message keyword), so in this sense, even the language itself is Windows-oriented. The VCL of course it full of code that calls the Win API, and is therefore quite specific to that API.
Nonetheless, the VCL is an elegant and effective wrapper, much, much nicer than MFC.
I believe you would find this to not be the case with Delphi in particular. The IDE produces rather minimal code anyway, and Delphi app GUIs are remarkably well-behaved "out of the box".
I think it would be reasonable to assume that, like bureaucracies everywhere, over time the effective purpose of these agencies evolves towards self-perpetuation.
*** The problem I see is that in any job where you're working on classified material you can't tell anyone about it. That would suck, to find out something cool and not be able to share it.
... which would make it VERY hard to use whatever tremendously cool experience you have there to get another job - hence, it would seem like a poor career choice, except for someone who planned to stay there forever.
On a related note, the managers there obviously know that the fact that you can't talk about what you did there limits your market value. I wonder how well they pay.
The complaint is that purchasing a (closed, of course) package of cards is an act of gambling, because the cards inside may be "worth" a little or a lot. With the Beanie Babies you mention, the buyer always knows what toy they are buying before they buy it, presumably. No gamble there.
If they administrators had been thinking ahead, they would have made the badges proximity-read card (like from CheckPoint) instead... making the idea you propose here quite easy to implement.
(I agree it is inevitable, due to some reason related to the "Safety of the Children")