Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

One language

Name: Anonymous 2007-11-09 4:36

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.

Name: Anonymous 2007-11-12 0:07

You definitely have to know how to code before you can pick up languages quickly, no question.  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.

I'm sure you can always learn more about a language, but mainly thats different library fx's, api's, etc...stuff you can look up.  After two weeks you should be able to hammer out a program to do whatever you want within the capabilities of that language.

As for large projects in C shell, it was a system for acquiring satellite telemetry from a bunch of different groundstations, performing error correction, checking against a flatfile schedule to make sure all scheduled files were received, moving those files to their archive locations, and sending email notifications if anything was missing or out of order. You'd be surprised how much you can get done just using unix command line and the crontab

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List