>yeah bro just learn COBOL and FORTRAN all those old timers

ya
noone use them

>>8334334
>know enough C to implement an assembler/interpreter for a noncomplete ISA
Is FORTRAN really that bad or will it be more of the same?

>>8334700
CFD and FEA is done in FORTRAN

>>8334334
yes, stay far away from COBOL and FORTRAN, there is no money in it, it's a meme, don't fall for it, go for something less saturated like Java or C# instead

>>8335077
I SEE YOUR GAME

>>8334334
It's correct, but they are shit and soulless languages, you would want to shoot yourself in the head after a while

>>8335045
literally what

>>8335154
https://en.wikipedia.org/wiki/Nastran

most of the simulation packages on the market are really just variants of this.

>>8334334
FORTRAN is still in use and has some degree of interoperability with C++ and C.

Dunno, I am doing a thesis in computational chemistry and people I am working with really like FORTRAN, so I guess there is a market.

I still use FORTRAN for numerically solving diff.eq.

I have a programming job that involves web dev, it'd be pretty ok, but there is legacy COBOL to be maintained, and that shit is just straight spaghetti. I am paid no where near that amount, although I do not program exclusively COBOL, it's simply a necessary evil. You are being memed however and I would probably kill myself if I had to do COBOL the entire time.

There was a guy on /biz/ a while ago claiming he made quite a bit of money (from home) writing medical software in a language more obscure and shitty than cobol/fortran, he didnt say what language tho.

>>8334334
If you're going to specialize in high performance computing you're going to need FORTRAN, although give you're probably just a stupid teenager try to be a "coder" I suggest C or C++, then Java and then Python, after that you can specialize in whatever you like.