as a sidenote, size is the last consideration nowadays, it just doesn't matter when you can buy a 2TB drive for 50$. you should take care of security and reliabilty first, not size.
Dynamically linked components can be problematic for those who use foobar2000 as a portable app.The solution is simple(?): user can copy msvcr100.dll and msvcp100.dll in foobar2000 folder (I assume that the developer uses MSVS 2010).And: foobar2000 itself and its official components are linked statically.
Size does matter on the internet. Both in terms of time it takes for users to download, not hitting transfer caps imposed by evil ISPs, and not to be forgotten, bandwidth costs for the HydrogenAudio server.As for using the WDK, last I checked it had some rather ancient compilers and runtimes, without a trace of C++0x. If you want to write your C++ without going insane, you will need to use a recent runtime.If you re-read my post, you'll see that I only advocate using a shared runtime when it's technically unfeasible to use a static runtime or MSVCRT.As for using "installers", that's not possible with the current foobar2000 component ecosystem which mandates that a component shall be distributed in a self-contained zip file with any dependencies it requires inside. Even if it was, it'd be impossible to use them with portable installs as lvqcl mentions.The reason why fb2k can get away from having a shared runtime is because it reinvents most of the C++ standard library in PFC, with the shared bits in shared.dll (which everyone must link). It is not feasible to rewrite arbitrary third party code to use PFC.
user can copy msvcr100.dll and msvcp100.dll in foobar2000 folder
Of course, you can forget about using those headers and libraries if you use even an ounce of the STL. It's a good thing nobody uses that.
Using the WDK headers and libraries is not an option if you write any kind of non-trivial C++. They're really only feasible if you write balls-to-the-wall idiot-grade C.
As for "size doesn't matter on the internet", I'm sure that the guy paying the HA bills disagrees strongly with you.
That's quite a geeky solution for most users. It's up to developers to care about dependencies.
rather, it's a workaround of the lazy, clueless "devs" whose only perspective is file size.
huh? wdk comes with stl, atl, mfc and so on. so what are you bitchin' about without a clue?
Quoterather, it's a workaround of the lazy, clueless "devs" whose only perspective is file size.harhar, so you rather have brainless end users downloading crap JUST to run a teeny component??lawl.
There's not a single VS2008 runtime, there's like 12 over the years with the service pack and all the hotfixes, with a serious versioning hell.
So? Ship the latest one.