https://issues.dlang.org/show_bug.cgi?id=15218
Adam D. Ruppe <destructiona...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |destructiona...@gmail.com --- Comment #1 from Adam D. Ruppe <destructiona...@gmail.com> --- I absolutely, strongly disagree. Dynamic linking Phobos is a bad idea - it will lead to serious breakage around every corner for every application. Phobos changes with every release. All executables compiled before an update will now be liable to break. Phobos is not commonly installed on user's computers. To distribute D programs compiled with these defaults, we'd also have to distribute the library. That'd be a 10x size increase and a big hassle... and moves the update breakage to the user's side. Phobos is also not commonly in the system library location, so on Linux, this means running programs won't work without either changing that or setting the library path, another big annoying hassle. I'd virtually break the zip distribution (which is Linux distro agnostic and used by those of us who aren't on .rpm or .deb). I guarantee you this will cause a bigger support burden than 400 KB in hello world and very little benefit. C and C++ are very different - their libraries are commonly installed with operating systems and don't break binary compatibility every couple months. If you want me to ever get on board with dynamic linking phobos, work to get it included with all the OSes as an independent end-user component first. --