One language

WTF is all this crap about which language is best and which language should I learn blah blah blah. Like 75% of the posts in here are about that shit.

There is really only one computer programming language, all the so called "languages" are really just dialects.

Once you know how to code picking up a new language should take 2 weeks tops.

So when you start a new project, figure out what the constraints are on that project and then use those to
pick a language.  If don't know the language that suits
your project the best. Learn it. Too many programmers
try to fit their projects to the languages they know
as opposed to just using the best language for the project.
This makes for shitty programs written by shitty programmers.

So I won't be hypocrite, one idea that I've been musing about is
the connection between computer programs, graphs, and linear algebra.

Like how you can represent a graph as a matrix and operations on the graph as matrix multiplications.  The matrices end up having huge dimensions, but you can apply an algorithm like Strassen's amazing algorithm to make high dimensional matrix multiplication asymtotically better than the naive algorithm.
It's really freakin neat.

>>37 My point is once you know one well, picking up others should be cake and the knowledge a good coder acquires isn't for the most part language specific its abstract.
Our point is that you're wrong. How many programmers know C/C++/Java/Python/Perl well but are utterly stymied by Lisp, Smalltalk, Forth, and functional languages? Lots. Learning a failanguage well enough to hammer out some code doesn't equip a programmer to understand high-level constructs. Maybe you didn't have much trouble learning languages from many paradigms, but that doesn't mean it's easy for everyone.