RngPack is a psuedo-random number generation package. It includes implementations of Ranecu, Ranmar, Ranlux, the Mersenne Twister, a wrapper for Java's built-in RNG, and a class that uses a second RNG to destroy statistical correlations in the first RNG. It can return uniform or Gaussian deviates and several other distributions. It is intended for numerical simulations, and is not intended for cryptography or security applications. Most generators are slightly faster than the Java built-in.
No time for CrashGreSQL
or is it CorrupedTablesGreSQL. When I started learning how to use databases, I believed the propaganda about ACID properties and tried using PostgreSQL. What a mistake. Every time I had PostgresSQL crash again and again and often I had corrupted tables.
Then I'd switch to MySQL and it would work just fine.
Then a new version of PostgreSQL would come out and the people around PostgreSQL would say how great the new version was, how it fixed all the new bugs, and I'd try a simple query and find that it takes PostgreSQL 60 seconds to do what MySQL can do in 0.1 second.
I can think of a number of major web sites that use MySQL. I can only think of one that uses PostgresSQL -- the independent media center -- and they have so much trouble with crashes that they really regret that choice. MySQL's web site has case studies of major organizations that use MySQL. PostgresSQL doesn't have any case studies -- maybe that's because PostgresSQL isn't being used by any major organiations because major organizations can't accept crashes and corrupted tables.
Sure, PostgresSQL has all kinds of features like subselects and transactions -- maybe MySQL is 1/2 a database because it lacks them. But after PostgresSQL crashes (particularly if your tables got corrupted) then you've got no database and 1/2 is greater than zero.
What particularly angers me is that the PostgresSQL mafia is always going around using lies and scare tactics. When they talk about performance, they always mysteriously seem to get 100x better performance than anybody else does. It seems like crashes and corrupted tables never happen to them. And then they go blabbering about the ACID property and never mention that corruted tables break the ACID property.
People are using MySQL because MySQL works. It might not be perfect. But if you learn MySQL and understand how to take advantage of it's strengths and work around it's weaknesses, you can build high-performing and robust applications. PostgreSQL has been around as long or longer than MySQL, but the fact is that it doesn't work -- at least not for ordinary mortals who download it, compile it, and try to use it. Maybe there's some secret about it that they're not telling us. If PostgresSQL can fix the crashing and corrupted tables, I might give it another chance, but they've lied so many times about the crashing and corrupted tables I don't know if I trust them anymore.
I think a lot of the time RSI problems aren't caused by using particular muscles too much, but more by not using other muscle enough. I felt tendonitis coming on at one time in my life and was really frustrated that it was going to get in the way of my work. I noticed, however, that I was feeling a lot of weakness in the muscles of my shoulders and upper arms.
I started doing push-ups, which are simple and free and don't require any equipment. In two weeks, all the symptoms of tendonitis were gone. I can't guarantee that this will work for everyone, but it's free and it can't hurt.