So back in July I was pretty upset about the stutter or micro freezing as it may be known. Now it's been pretty much concluded it is due to the GC of Unity 4.x, and I have been playing 1.0.5 and see it is worse than ever.
For reference I play off a custom rig running:
Windows 10 Home
GTX 980 Ti
16 GB DDR4
I generally use a resolution of 2160p or 1440p
I have run the game from the following 3 drives:
SM951 256 m.2 SSD
850 Pro 256 SATA
...this is, simply, the wrong way to write code that runs under Unity (or any other system that uses a garbage collection based allocator).
If you actually mean "why is KSP like this?" then the main reason (IMO) is that it is very easy to make this sort of mistake, the developer has to be constantly aware of how much memory is being allocated on the heap and write the important bits (i.e. any code that is run on every frame or physics update) to create the minimum garbage po