Re: Top 10 Worst C# Features

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Fri, 4 Sep 2015 16:34:40 -0500, Randy Brukardt wrote:

> Opportunity for what, madness? Event-driven GUI programming is just one step 
> short of madness as it is, I'd hate to expand that. Such code is necessarily 
> unstructured spaggetti, because every routine has to be able to handle 
> anything in essentially any order.

There are competing relationships which do not map each other. An
issuer-handler relationship is a mess because other relationship, the
hierarchy of widget types, is considered more important. Another messy
relationship is container-child. We cannot have all three structured, thus
two of them are necessarily mess.
 
> Much like OOP itself, I don't see it having much application away from the 
> GUI (and I'm dubious that it is that good of an organization even for a 
> GUI).

GUI is a poor example for OO actually, because of above.

> As such, it doesn't make much sense in a general purpose programming 
> language.

Only OOP makes sense. There is *no* application where procedural
decomposition is superior to OO decomposition.

Procedural decomposition is untyped per design, because procedures can work
with existing types only. Therefore you must have all types *before* you
start thinking in terms of procedures. So the only types which can be
involved are primitive scalar types or messy ad-hoc low-level records and
arrays.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de