“Patterns are signs of weakness in programming languages”
This is a conclusion of Mark Dominus on his blog, an interesting and thought-provoking post (very worth reading). Anyway, I don’t agree with his idea. Though we can create a very complicated programming language, there will always be something left and these things are likely to be patterns.
3 nhận xét:
The view you're using is different from the author's view. Hence each may reason in one's way. Weekness in design patterns doesn't coincide with unefficient programming languages. The point here is "the long-term goal of trying to understand how to improve the language so that the pattern becomes invisible or unnecessary".
Most of his saying are correct, but only the conclusion. There's awlays a compromise between putting everything in programming language and its simplicity. The more you put design patterns in a language, the more complicated it is. No matter how many design patterns are implemented in a language, there's always something left. And these things will likely be patterns in this language.
Patterns are not invented, but rather discovered and observed from actual practice in the field. Some specific patterns, later on, may come into a language but others will be found out. Hence, pattern will never become invisible or unnecessary.
I totally agree with you :-). From the point of whole view pattern will never becomes unnecessary or invisible. But in a project scope, the chosen programming language or framework is the one that have most of useful patterns are implemented, so that patterns are invisible or unnecessary to take time.
Đăng nhận xét