Comment 21 for bug 535806

Ok, on windows (lenovo t410i, win7 prof x64, widelands release build,virus scan active) the performance gain with mng is significant.
What i did is stopping the time with "widelands.exe --editor", with each build i did this at least 5 times and to avoid cache issues:
With mng after a few starts i only took 16 seconds to start the editor. With the current trunk build i was not able to get loading time below 41 seconds!

So some form of container would really help on win32...