New version of OgreMap

HeatDeath · 09-30-2016, 02:48 PM

He's probably just using .NET's built-in object serialization code. Each hex is probably an instantiated object of the same type, so that multiplies out the overhead significantly. Sure it's not efficient, at all. But it's literally one line of code, that doesn't have to change even when you add new features to the program.

Memory, bandwidth, and HD space are cheap. Developer time and mindspace is expensive. And premature optimization is the root of all evil. :)

09-30-2016, 02:48 PM	#23
HeatDeath Join Date: May 2012	Re: New version of OgreMap He's probably just using .NET's built-in object serialization code. Each hex is probably an instantiated object of the same type, so that multiplies out the overhead significantly. Sure it's not efficient, at all. But it's literally one line of code, that doesn't have to change even when you add new features to the program. Memory, bandwidth, and HD space are cheap. Developer time and mindspace is expensive. And premature optimization is the root of all evil. :) Last edited by HeatDeath; 09-30-2016 at 02:56 PM.