what if you 'outgrew' ".Not" (aka ".Net") itself?
I 'outgrew' '.Not' back in the early noughties, when they thought it up.
I just do a native compile. Seems to go blisteringly fast, too. It's WAY better than some p-code wannabe that's part of ".Not". Bleah. Throw it away along with 'garbage collection' and the bass-ackwards pseudo-object-oriented way of doing things that's so "core" to ".Not".
I mean, do you REALLY need "Universe.Galaxy.system.planet.continent.country.province" <line break> ".county.city.district.street.house.pet.flea" just to get to "flea"? beginning by enumerating the 'universe' collection? And getting EVERY! STINKING! DETAIL! about EVERY! OTHER! FLEA! during the enumeration to find the matching flea? Seriously?
OK maybe not THAT bad, but it was an illustration of the bass-ackwards thinking behind ".Not"s very design. Thanks, I'll use API functions instead, and write efficient C/C++ code that compiles to a NATIVE BINARY and doesn't need a MONOLITHIC TOP-HEAVY SHARED LIB [that gets updated _ALL_ of the time because it's so flawed] just to LOAD [let alone RUN].
[and - dirty little secret - if I design my C++ code properly, I can compile it for MFC _or_ wxWidgets with the SAME! CODE! BASE! Imagine that!]
Biting the hand that feeds IT
