note that this increase in division parallels the resurgence of leftist philosophies over the past decade or so.
Like, for example, when people propose cutting public funding for education, healthcare, welfare, abortion, and all that
or you propose doing away with corporate welfare, rural subsidies, mortgage deductions, etc...
Here are the examples you asked for: http://www.ebony.com/black-his...
Heck, you should even count the US Civil War.
Note the lack of official punishment for any of these acts. They were tacitly condoned. Even the Civil War instigators were pardoned and allowed to reintegrate.
Riots, looting, and violent political actions are overwhelmingly carried out by leftists (and I include fascists in that), not by conservatives or libertarians.
Well...who needs to riot or loot when you can twist the laws to do your bidding. As conservatives become unable to do so, you'll see much more rioting, looting,and violence; rest assured.
Wow, you wrote that entire rant over a single letter. That's pathetic.
Language is an art, like painting. Technical language is an art where miscommunication leads to real world problems, and where evidence of lack of expertise leads to well justified lack of confidence up front.
With language, as with painting, you can paint like a master, or you can finger-paint like an addled child.
Which do you think will carry you further in life and in your career? Which do you think will result in more actual pathos?
((((((((((((I hate lisp too))))))))))
Just having higher-order functions doesn't make a language a functional language any more than having structs makes C an object-oriented language.
Structs do, however, make the critical aspects of an object oriented approach practical in c. They can carry data, function pointers, etc., and they can be passed around.
I've been writing my c code like that since the 1980's. There are significant benefits.
I would add to this that reducing the complexity by turning everything into separate functions tends to also increase what I call "opacity by non-locality."
Not only are some things hard, some things benefit from having the logic right there in front of your face; not in a header, not in some function elsewhere, not in a library.
Benefits in both comprehension, and so ease of construction, but also in execution time and smaller executables depending on just how smart the language is in constructing its own executables.
IMHO, unit testing is a far, far more important aspect of advancing programming in general than are lambdas. Just my 2c.
So, for example, by storing functions as values in a dict you can build complex structures of execution without using any conditional codes
This is the core mechanism of my text markup language. Once the specific built-in tokens are parsed out, they are immediately accessed via the language's function dictionary. This approach is quick, ultimately low-complexity, trivially extensible, and highly maintainable.
Would you consider unions in c a "means to circumvent the type system" as compared to a language with strong up-front typing?
Unions are certainly a very powerful, useful, and concise tool for manipulating data across type boundaries. If you don't have them, in trying to accomplish similar tasks as those unions make easy, in many languages you're going to be a lot more verbose, and likely a lot less efficient, than if you do.
I am assuming competence. Strong typing is a safety net. The need for such a thing varies with one's skill set. The fewer the participants, the more likely it is that the skill sets can be arranged to be similar. With larger teams, the need for safety nets almost always increases.
The power to destroy a planet is insignificant when compared to the power of the Force. - Darth Vader