My order of preference is c, b, a.
Here's the results of the sample poll (obviously I will wait for people to
state their actual preferences and not rely on my opinions):
A B C
Michael 0 1 2
Steve 2 1 0
Thomas 1 2 0
Leath 0 1 2
Totals 3 5 4
Winner: B
This is definitely the preferable way for me to go. I know there is
a lot of concern about legacy applications and their compatibility,
but quite simply, I would rather get things 'right'. (i.e.: vote C, B
then A)
Being primarily a windows developer moving slowly into Linux, I have
to say that I don't think that the support of legacy applications is
really that important (uh oh -- better jump into a pool full of flame
retardant liquid!!! :)
I know that sounds harsh and possibly detrimental in some areas, but
from what I can see from current Linux applications, you can very
easily fix them -- lets face it, you have to be a programmer at heart
to develop on Linux at all -- fixing older problems won't be hard, and
a few years down the track when Linux become the major development
platform for most companies (I can hope... :) they will be much happier
with a solid solution... and yes, I know that isn't the most solid
ground for my decision, but it's definitely what I am comfortable with.
'C' works best for me as I won't have to change anything with all my
current development projects such as the tools, main engine, and
research code...
'B' and 'A' are almost identical from my point of view, and to be
perfectly honest I just prefer 'B' because it appears that it can
work exactly the same way as 'A' anyway... is this right? With 'B'
it appears that I can do a #define GL_OGLBASE_EXTENSIONS and have
the glext.h included, or include it myself in the application exactly
the same way 'A' works (seemingly making 'A' moot).
If you want a second vote, mine is as above.
Leathal.
