Mission Statement:
Making Software Better, One Bite at a Time

Imagine if every Thursday your shoes exploded if you tied them the usual way.
This happens to us all the time with computers, and nobody thinks of complaining
-- Jeff Raskin --

Blue Whale Software has been started when several developers (some with experience back to CPUs like i8080 or Z80, if somebody remembers what they were) got exceedingly tired with extremely poor quality of most of the software they needed to deal with as users. We got tired of browsers and mail agents eating hundreds of megabytes of memory without any apparent reason, got tired of databases which cannot avoid cache poisoning by single table scan or which have problems maintaining ACID transactional properties, got tired of operating systems which require gigabytes of RAM and minutes of intensive work just to boot (and not to be able anything useful afterwards because mere gigabyte is not enough for it), of DLL/.so mess, and so on. So we have decided to start a software development company to write software, which will be reliable, will work fast, and will use as little resources as possible. It does not mean that we are aiming to reinstate programming practices of 1970's, to the contrary - what we want is to achieve these ambitious goals based on new technology and research. Moreover, we are proud of our innovative ideas, and are going to submit our first bunch (around 10-12) of patent applications very soon, with (as we hope) much more to follow.

Obviously, we do realize that rewriting of all the software in the world at once would be way too ambitious even for us , so we adopted an approach of doing it "one bite at a time". If we can make one single piece of software better and to have it adopted by wide community, it is already a small victory on our way. The first project we have started within this company is development of OLTP-oriented ACID-compliant "database storage engine", aiming to surpass existing TPC-C and TPC-E benchmarks on the equivalent hardware by significant margin.

On the way of such an ambitious goal of making software better, one of the very first important questions we have run into was "To open source or not to open source?" After long thoughts and deliberations we have decided to divide software into large-scale modules and decide on open sourcing them on case-by-case basis. What is clear though that we are not going to use GPL; what will be published as open source, will be under MPL-style license (in some cases disjunction with LGPL can also be considered). On the other hand, we reserve the right of patenting algorithms, though within the spirit of MPL we will grant royalty-free licenses for everybody using our patents as a part of our published open source code.