A programming language is an artificial language designed to express computations that can be performed by a machine. **Please note:** As is the case elsewhere on Stack Overflow, resource and tutorial recommendation requests, requests for lists of things ("which languages have this feature..."), and excessively opinion-based ("what's the best...") questions are off topic.
- Stackoverflow.com Wiki
Programming language based on the one-liners of Arnold Schwarzenegger
Let’s make stacker, a programming language that implements a stack-based calculator.
There are about six major conceptualizations of memory that dominate today’s programming. Three of them derive from the three most historically important programming languages of the 1950s — COBOL, LISP, and FORTRAN — and the other three derive from the three historically important data storage systems: magnetic tape, Unix-style hierarchical filesystems, and relational databases.
I was reading yet another blog post titled “Why our team moved from to " (I forgot which one) and I started wondering if you can generalize it a bit. Is it possible to generate a N * N contingency table of moving from language X to language Y?
I don’t know about you, but nothing gets me going in the morning quite like a good old fashioned programming language rant. It stirs the blood to see someone skewer one of those “blub” languages the plebians use, muddling through their day with it between furtive visits to StackOverflow.
The MSDN documentation of the (hypothetical) GetFrobnicationInterval would explain that it returns the interval at which the object frobnicates. It will also state that the method will throw an InvalidOperationException if the frobnication interval cannot be retrieved. You will also find two "community comments", one of which will contain line noise and the other will inquire about what frobnication is at room temperature in broken English.
Generally speaking, taking advantage of these peculiar behaviors is considered evil since your code should be anything but surprising.
Sometimes we’re so wrapped up in the present and future and don’t take time to remember the past. Today’s popular programming languages will become tomorrow’s ancient languages, collecting dust. For some who still use Fortran or Cobol, to think that these languages were “hip” back in 1984 must feel like going back a thousand years ago.