OK... let me ask again...
1. I was suggested (and came to the conclusion) that VBA/Excel are for losers and anyone is better of learning Tradestation or WealthLab (which are also a bunch of useless shit) if they ever have to use that piece of sh*t.
2. If you want to develop high-end execution / models, you're better off with C++/OCaml(Haskel, errlang) on UNIX. There's not much of a choice there (No... not Java or Mono/C#... Java/C# is great for developing front-end apps. And just in case the first sentence in the paragraph... "high end"...)
3. Basically, an "un-official ET prog. language" will be the synonymous to the prototyping language of choice.
Hopefully, everyone can agree with me up to here...
So... which language is best, in your opinion for prototyping?
For starters:
F# - I think it's a bit too immature to use. I would learn OCaml if I had to use this considering the performance benefits and for the fact that your not bound to WinOS.
OCaml - I still suck at thinking functional. It takes me time... but I see the potential once I get used to it.
C# - I love my Visual Studios.
Python - Plenty of well made libs. It's more for the IT-oriented people than the Quant modellers.
R - Stats only. Pure Quant. love them. If my job was only about modelling, then I'll consider...
Matlab - Stats only. Same as R. Pure Quants love them... and learn them in school... If my job was only about modelling, then I'll consider...
Ruby - I have no idea... many people like it, especially the IT people in Quant firms.
Any opinions on prototyping language?
FYI:
http://shootout.alioth.debian.org/u64/benchmark.php?test=all&lang=all&lang2=gpp&box=1