>>1
You should learn C first, and actually stick with it.
It's the best possible language, if you learn C you can learn almost every language (ruby, perl, php) but you won't need those because simply C IS AN EXPERT LANGUAGE FOR EXPERT PROGRAMMERS
>>11
You should learn lisp first, and actually stick with it.
It's the best possible language, if you learn lisp you can learn almost every language (ruby, perl, php) but you won't need those because simply LISP IS AN EXPERT LANGUAGE FOR EXPERT PROGRAMMERS
FIXED
Name:
Anonymous2007-04-01 8:18 ID:1TAc2Vdb
>>13
Learn Haskell: then you can trivially make EDSLs that serve your purpose.
FIXED
Name:
Anonymous2007-04-01 8:41 ID:tqD4YbVN
>>14
Learn Lisp: then you can trivially make EDSLs that serve your purpose AND about 1000 other purposes you havent even considered.
FIXED
Name:
Anonymous2007-04-01 9:42 ID:1TAc2Vdb
>>15
LISP is only good for AI research... Oh, wait. Not even that.
FIXED.
Name:
Anonymous2007-04-01 9:50 ID:3x8CS7dw
ONLY SMART ANSWER HERE
Learn C then C++ and don't be in a hurry to learn them take your time or you will forget everything
Dear C/C++ asshole who stole my assembly language:
I hope you die. You had to stand there while I learned my mnemonics and built my own data abstractions by hand because I'd bought good hardware---even cheap development tools are good when you buy fresh spices to go with it. I"m sure you think that you're somehow entitled to steal anything you can find because somehow you've been wronged. But consider this: this is who I am. You have just deprived me of one of my two methods of creating ultra-efficient programs, and my only method of writing a first-stage bootloader. I can feel the blackness sweeping in on me, a depression that a year of war somehow doesn't equal. In war people want to kill you. Evdiently your fellow citizens just want to screw you. I wonder if I were a young guy with muscles, a high-and-tight haircut, and the obvious look of a veteran if you'd have stolen their language.
I hope you die. I have no way of optimizing my code now, or of hacking my programs. That's what you did to me. That language represented 1/7th of life reading asm manuals and was a necessity. I had it exactly one month. You'll probably pop linker and compiler and use it to boast to all your shitty friends about how fast your program is. I paid for that language, and I hope karma tears you to shreds.
If anybody offers sympathy, I will scream. I want revenge. I want trial by combat. Oh, and by the way, Cub Foods? Tahnks for being so not helpful. There are assholes who steal, and then there are assholes who just shouldn't work with the public. Thanks bunches. I'll take it to corporate if I have to. I hate you.
>>1
Learn C if you want to learn how to write programs.
Learn C++ if you want to learn how to design programs.
Whichever you choose, learn how to use it, and learn how to use it well. Poorly written programs in either language are PURE LIQUID PAIN.
Name:
Anonymous2007-04-02 20:52 ID:ZEI0/+9C
Learn VB if you want to learn how to write programs.
Learn Java if you want to learn how to design programs.
Whichever you choose, learn how to use it, and learn how to use it well. Poorly written programs in either language are PURE LIQUID PAIN.
Name:
Anonymous2007-04-03 4:49 ID:omw0JCk5
>>22
I'm seeing this everywhere now and I really just have to know,
SAUCE PLZ?
Name:
Anonymous2007-04-03 7:04 ID:CGxGCdqC
>>26 Learn VB if you want to learn how not to write programs. Learn Java if you want to learn how not to design programs. programs in either language are PURE LIQUID PAIN.
I'm a 1337 gaem progremmaer and lard C, C++ or Python on my ownz!!!
They made me learn Java in college! Buaah!
I know absolutely nothing about Lisp, Haskell or Perl but am qualified to express my opinion about them.
Fix'd.
Name:
Anonymous2007-04-03 19:29 ID:aev7jqVM
One word: lisp
Name:
Anonymous2007-04-03 19:31 ID:Dl+AkEKg
One word: jimmyjanga
Name:
Anonymous2007-04-03 19:32 ID:CO2WP+kG
One word: The son of educator Samuel Silas Curry, he was educated at Harvard University and received a Ph.D. from Göttingen in 1930, under the supervision of David Hilbert.
Name:
Anonymous2007-04-03 20:10 ID:MgWuuaRN
Learn whitespace, brainfuck or shakespeare programming language if you want to get anything done. Learn assembly if you need to. Don't bother with C, C++, Python, Java, PHP, Perl, Ruby, Haskell or Lisp.
Fix'd for everyone
Name:
Anonymous2007-04-03 21:33 ID:JVcXkIeU
Best advice in this thread: learn whatever you want to and ignore all the language elitists. Only a very small percentage of the advice actually has some merit and the rest is pure fanboyism.
Believe me, no matter what programming language you learn there will always be someone telling you that you're stupid for taking the time to learn it. If you want to get ahead early don't expend much energy into such arguments, it's futile.
Get really good at one or two languages, then start looking at others. Keep looking at whatever the other language is until you understand why people decided to design it that way. Going from C++ to Java to C# or whatever doesn't count. Mix in prolog, haskell, lisp, microcontroller assembly, whatever, and you can start to consider yourself a decent programmer. Oh, and write a compiler too, it's not that hard especially if you follow a good textbook.
Name:
Anonymous2007-04-04 6:14 ID:+8oeWwoj
>>41
write a compiler? ..
Learn C, and then Assembly.
Then LISP and you can consider yourself an expert programmer
Learn VB.NET, c# and PERL. And whatever shit SAP uses. You'll earn some decent money with the first two, and get some work done with the third. SAP is for any corporate suckers you come across.
The fall-back is to be sufficiently crap enough so that you can make it to CEO without having a heart-attack. Have fun
Name:
Anonymous2007-04-05 3:35 ID:w8ASGiTC
>>16
NO! Lisp is crap! Learn Chicken Scheme. Sure it's a dialect of a dialect of Lisp, but it is just as irritating but it has a fun name.
But there is one good thing about learning on a Lisp based language: you don't need to learn syntax because there hardly is any!
To be honest, it probably would have been easier to adapt to a Lisp language before I became so rooted in OOP.