4 ms·
I watched the first twenty minutes. One interesting take-away was "languages should support good habits and make anti-patterns harder" (paraphrased roughly, of
by joe_the_user 16y ago
I watched the first twenty minutes.
One interesting take-away was "languages should support good habits and make anti-patterns harder" (paraphrased roughly, of course). So it comes down to what one thinks good or bad habits are.
The video further reminded me of C#/.net's ginormous number of classes, interfaces and intermediate classes - it is standard procedure to use three different class-types to get a row of data from a database query. Thus my view would be that c#'s many clever looping and generics patterns actually are enabling tools the anti-pattern of too many classes/excessive indirection.
Thus it seems like Ruby's "Duck-typing", where you pass a single array around even when it's used slightly differently all around, is a general approach which allows you to escape this hell.