Subject Future feature priorities
Author t_j_haynes

Now, I really like Firebird and I want it to do well, but at the
moment I feel it is losing out for a number of fairly obvious
reasons. So here is my quick two pennies worth of where I see the
problem. I know it's just my view from the point of view of an end
user, but I wonder what the general feeling is?

Firebird's biggest problem today is the lack of a viable Windows
server. In the real world everyone runs multiple CPU servers, even
more so with hyperthreading and dual-core chips. Unfortunately the
Superserver doesn't handle multiple CPUs and the Classic server is
apparently not properly tested on Windows. This rules Firebird out
of most 'real' use on Windows. A multithreaded multi-CPU server
would be the ideal answer, but this isn't scheduled until V3.0
(Vulcan). A reliable Classic server today would at least allow those
thinking about adopting Firebird to make a start.

Next most urgent issue is the safety of information. A good backup
(including incremental) is critical, and I gather that this is being
addressed for version 2.0. Another not uncommon requirement is for
simple whole-database replication, but sadly Firebird's shadow
databases sadly fall just short of being a truly brilliant
distinguishing feature and trigger based replication mechanisms are
comparatively lousy.

Third is the lack of documentation. This is largely addressed by
buying the book, but the online stuff is a mess - a mix of current
and old Interbase stuff. It really needs to be current and Firebird

Last, but not least is the lack of a standard graphical
administrative interface. This doesn't worry me, but some of these
youngsters today can only function in a point-and-click world. A
problem is that there are several GUI tools available, causing
confusion among users who just want to install the standard package
and have it just work 'out of the box'.

I know that most of this stuff is in the schedule, but it all seems
so far away and a load of (relatively) trivial 'features' seem to be
coming first. With a working Classic server and an incremental
backup I could hold the PostgreSQL supporters at bay, but defending
Firebird is quite tough right now. Help!


PS: Any rough dates on 2.0 and 3.0? Those published don't seem to
have been updated for a while.