DaveC said:
I do worry about dynamic libraries. What if you have an app that uses a certain one, then the library gets updated for a newer app and then the old app stops working? The old app could be updated but you know how devs come and go and many times don't release the source. Could be an issue. Static ones are bigger but apps are generally pretty small anyway. What is a meg here and there when 8-gig cards are getting cheaper by the day and will be real cheap by the time this is released?
Don't worry about that - nearly every system uses dynamic linked libraries (or what do you think .DLL files in Windows are?)
The Amiga also did use libraries (in libs-directory).
Newer libraries are backwards-compatible, so all old stuff will run.
But the good thing is: A newer version of the library might be more optimized, etc., and the program runs faster without recompiling.
Have you seen what I did with Super Methane Bros.?
I simply recompiled it with the Open2x Libs and it ran even smoother with 75MHz than the old GPH version ran at 200MHz.
If such programs used dynamic libraries, they'd run smoother without any recompiling
In theory that will work. It may be OK 95% of the time. But haven't you heard of the problems with windows .dll files? The same thing that I said has happened alot.. Someone installs app with new .dll, old app breaks.
This timing improvement you speak of could break stuff. What if the coder took the timing of the old lib into account when doing the sound or screen update etc into their app? Update and the sound may be off etc. You can't assume anything.