Does anyone have a list of what the changes in 4.0.1 are? All I can find are the source diffs, not documentation. I'd really like to know what changed before I consider upgrading.
There is a Perl standard out there. Has been from the beginning.
It is called Larry Wall.
How Much / What Type of redundancy
on
Linux Failover?
·
· Score: 1
From what you describe it sounds like your consultant is trying to build full failover/redundancy. It is often more cost effective and easier to implement a limited failover/redundancy system where you only build failover/redundancy for critical components and components likely to fail. You also have to decide at what sort of level do you want redundancy/failover. Do you want failover at the network, server or application level? or all? If you're going whole-hog total availability there's a lot more to consider too:
backup power w/ generator
at least 2 outside network connections (T-1) from different providers that follow different cable-paths and enter the building from different sides (same for your power connections, better yet locate near a hospital).
backup datacenter geographically distant from your current datacenter
etc....
Building Linux Clusters - O'Reilly
on
Linux Failover?
·
· Score: 3
There are many good ways (and even more bad ways) to build a redundant/failover environment. Your consultant is just "seeing the one solution he knows). As others have posted there are many good solutions already out there.
Building Linux Clusters is just what you should read.... Uncoftunately it won't be out until August.
I don't know about the other slashdottes, but I for one would love to see how the Slashdot network is configured topologically.
When to use MySQL (and when not to)
on
Why Not MySQL?
·
· Score: 1
Many applications can be built easily and reliably using MySQL, some can not. MySQL is not suited to HUGE applications (where the database/application can not be understood by one programmer). Nor is MySQL suited to an application with large or complex transactions; or an application with a lot of interactivity. However, for building small applications that are predominantly read-oriented with no complex transactions I find MySQL an excelent solution.
I do find MySQL's lack of subqueries and views troublesome, but they are nothing that I can't code around (but I do keep my fingers crossed that they'll appear soon). Triggers are overrated and hard to use effectively unless you have a briliant developer designing them. FOreign-key-constraints are mainly useful for getting lines to appear on an ER diagram. Other than that they cause more trouble than they're worth.
Personally I avoid stored-procedures like the plague and will continue to until there is a standard stored-procedure language. All that stored-procedures accomplish at this point is to sometimes speed up your code with the drawback of making your system totally dependant on one particular RDBMS. When I want to provide stored-procedure like functionality I do it via an application level library, which allows me to be relatively RDBMS independant.
So far only one news orginization has gotten the story right. All the newscasts I've heard are leaading with titles like "E-mail Virus Criples Internet Users", none of them even mention that's its an MS-Outlook problem. This really irks me because they're missing the whole point that this is not an "Internet e-mail" virus it is a "Microsoft Outlook" virus. I felt vindicated 5 minutes ago when I heard on NPR's "All Things Considered" start off with the headline "Virus Inside Microsoft E-mail....". Congratulations NPR/All Things Considered for getting it right!
I agree that much of the complexity could be trimmed down. Perhaps by storing all previously analyzed positions so you would only have to analyze all possible moves from each position once (there are many more possible games than there are possible board positions, but I don't want to even think of the amount to storage space you'd need for that). Even after that the search space is still huge.
According to the Oxford Companion to Chess by David Hooper & Kenneth Whyld, the number of legal board positions is about 2 * 10E43.
In a game limited games to 50 moves, with a very modest average branching factor of 15 moves per ply. Exhaustive analysis of this limited tree would require enumerating 10^120 nodes.
One widely accepted estimate for the number of atoms in the observable universe is 10^80. If each such atom were a supercomputer capable of generating and evaluating 1 trillion board positions per second, and had been doing so since the Big Bang (say 20 billion years ago), only the tiniest fraction of the analysis would thus far have been completed.
Slashdot Mirror
Does anyone have a list of what the changes in 4.0.1 are? All I can find are the source diffs, not documentation. I'd really like to know what changed before I consider upgrading.
It is called Larry Wall.
Building Linux Clusters is just what you should read.... Uncoftunately it won't be out until August.
I don't know about the other slashdottes, but I for one would love to see how the Slashdot network is configured topologically.
I do find MySQL's lack of subqueries and views troublesome, but they are nothing that I can't code around (but I do keep my fingers crossed that they'll appear soon). Triggers are overrated and hard to use effectively unless you have a briliant developer designing them. FOreign-key-constraints are mainly useful for getting lines to appear on an ER diagram. Other than that they cause more trouble than they're worth.
Personally I avoid stored-procedures like the plague and will continue to until there is a standard stored-procedure language. All that stored-procedures accomplish at this point is to sometimes speed up your code with the drawback of making your system totally dependant on one particular RDBMS. When I want to provide stored-procedure like functionality I do it via an application level library, which allows me to be relatively RDBMS independant.
So far only one news orginization has gotten the story right. All the newscasts I've heard are leaading with titles like "E-mail Virus Criples Internet Users", none of them even mention that's its an MS-Outlook problem. This really irks me because they're missing the whole point that this is not an "Internet e-mail" virus it is a "Microsoft Outlook" virus. I felt vindicated 5 minutes ago when I heard on NPR's "All Things Considered" start off with the headline "Virus Inside Microsoft E-mail....". Congratulations NPR/All Things Considered for getting it right!
I agree that much of the complexity could be trimmed down. Perhaps by storing all previously analyzed positions so you would only have to analyze all possible moves from each position once (there are many more possible games than there are possible board positions, but I don't want to even think of the amount to storage space you'd need for that). Even after that the search space is still huge.
In a game limited games to 50 moves, with a very modest average branching factor of 15 moves per ply. Exhaustive analysis of this limited tree would require enumerating 10^120 nodes.
One widely accepted estimate for the number of atoms in the observable universe is 10^80. If each such atom were a supercomputer capable of generating and evaluating 1 trillion board positions per second, and had been doing so since the Big Bang (say 20 billion years ago), only the tiniest fraction of the analysis would thus far have been completed.