Anonymous user
User:Rldrenth: Difference between revisions
langs
No edit summary |
(langs) |
||
Line 31:
funky recursion stuff in the Python Prime Decomposition task was started by me, although it's been modified
since.
==What Languages Should You Learn==
Here's what I think and why (Not necessarily in any particular order).
C# - There's lots of organizations that run Microsoft & use their tools. This is the language of choice.
It's a good language too. A bit better than Java IMHO. If you're really not into Microsoft stuff, then learn Java instead.
C - After 35 years, there's still no language that can replace it when you need to do nitty gritty stuff, or if you're working on embeded microcontrollers.
Python - Easy to use and very, very powerful. Applicable to a wide range of applictions. A possible
drawback is that it's not very fast. Lots of C based modules that you import mitigate this drawback.
Look for Python to be the inspiration of future languages. You can also use it to get a taste of Functional programming ala APL and J.
JavaScript - If you're going to do web pages, you'll be learning this one, like it or not. And along with this you'll want to learn about HTML and CSS.
SQL - You won't be using this all the time, but you will do enough with it to need to learn it.
Assembly - At least a little, so you know what happens down at the machine level.
VHDL or Verilog or other Hardware Description Language - It's a different way of viewing the world, where timing and sequencing rule.
===What popular modern language should you not bother to learn?===
Visual Basic or VB.Net. -It's on the way out, being supplanted by C#, Python, and occasionally C.
What about C++? - I still like C++. But I think there are other languages that will provide higher programmer productivity in practice. Try D, Objective-C, Java, or Delphi instead.
| |||