I totally agree with you, foss.
And here my cents...
Jez, that discussion again. It's not like it hasn't been there for a year
In science, and I regard software engineering as science,
sentences like "all are doing that" or "it has always been like this"
are a no go! Otherwise men kin would not have made any progress as
at a particular point in time everything "has always been like it is"!
Science always lives from objectiveness, transparency,
measure-ability, reproducibility and re-thinking of finding, laws and
processes (by the way, good base principles for life also ;-).
It's simply similar to how a great deal of other software behaves. Just the
Bitcoin client foss, says? What about
- All Office applications
- Adobe applications as already mentioned
- Visual Studio
- System Center consoles
If a system has to load a lot of libraries and to do a lot of configs at
startup it is wise to separate this into threads, build the mostly
used features first, show UI etc. and load the other stuff in background.
You're welcome to write a patch that loads the main UI while it displays a
wheel until everything is ready.
This splash screen is something like telling:
"You have to watch how long we need to start! No other way!" This kind of
hinders the acceptance a lot, as foss pointed out.
Oh great. The I consider the acceptance problem of "I doubleclicked, where
the app?" much bigger than a splash screen at login while I have to wait for
the rest of my system anyway.