A Brief, Incomplete, and Mostly Wrong History of Programming Languages (2009)
james-iry.blogspot.com
james-iry.blogspot.com
(On another note, James seems to have written a post back in March of this year. It's been such a long time since he wrote anything I wondered if he ever would again.)
Now back to writing an application in PL/SQL....
> Haskell gets some resistance due to the complexity of using monads to control side effects. Wadler tries to appease critics by explaining that "a monad is a monoid in the category of endofunctors, what's the problem?"
[0] https://books.google.com/books?id=gfI-BAAAQBAJ&lpg=PA138&dq=...
Or to not be polite to the compiler.
His goal is to create a language with the intelligence of a two year old. He proves he has reached his goal by showing a Prolog session that says "No." to every query.
is both more and less funny than it used to be now that I have a two year old.
Writing C++ without using C++'s idioms is usually, if not almost always, creating more technical and business risk for the writer and the consumer than using C++'s idioms in the first place. (That some of these idioms are conceptually very difficult is a very valid criticism of C++, and one that Rust in particular seems well-positioned to be better about, but I'd take the bear traps of C++ over the land mines of C almost any day.)
In a lecture once upon a time, some famous Lisp hacker joked that, if you will, to recurse over tree structure is to "cons descend". A blue-tied Fortran programmer from IBM in the audience didn't get the joke, and walked away with the idea that Lisp programmers are arrogant jerks who even program via condescension.
>1965 - Kemeny and Kurtz go to 1964.
Brilliant
After all the only way Haskell could be conceived is after a very long LSD (needed to grok monads) fueled BSDM (the type system) session.
Edit: Missed Haskell in the article. But I guess you could say the upper for different reasons about angular, enterprise software and spring. Or anything that transpires to JS, due to the build chain and difficulty debugging.