Choose life. Choose inheritance. Choose a job subclassing all the controls you ever built, and all the 3rd party ones you might ever use. Choose combinatorial explosion. Choose painfully recreating designers to work against the subclasses you just built. Choose aggregated proxy-by-reflection just to get the damned sealed classes working, and waking up in a cold sweat in the middle of the night panicking over the grotesqueness of it all. Choose backing yourself into a corner. Choose starting from scratch for the next version. Choose wishing you could call base.base.method() because your immediate subclass overrode the method to do something you didn't want. Choose your future. Choose inheritance.
(me getting wound up on aus-dotnet list again)
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Summary: Even if you think you know what you're doing, it is not safe to store anything in a ThreadStatic member, CallContext or Thread...
-
I love PowerShell, and use it for pretty much everything that I’m not forced to compile. As a result I’ve got fairly competent, and people h...
-
Look, it’s really not that hard. Programs are still in the same place, in %ProgramFiles%, unless you need the 32 bit version, which is in...
No comments:
Post a Comment