Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@AlmondSauce as far as I remember most of scientific algorithms on this planet use fortran (blas library). This includes weather simulation and prediction, ml frameworks and couple of most complicated programs I don’t remember now.
-
@jurion @vane oh absolutely, legacy stuff is everywhere. It's just rare to see someone go into it as a new language these days - most people I know who live in those languages are nearing retirement.
-
-
@vane mostly just maintenance for old but important projects. Physics students probably don't care about nice code, but really there can be hidden effects when the language doesn't protect you and sometimes results in incorrect implementation.
-
@beegC0de the language not protecting you could also be a plus as you could potentially do some weird shit with it that'd be otherwise not possible.
-
@Parzi true but I prefer to have a layer over the weird stuff and break it when I need it
-
@beegC0de overhead tho
-
@vane Sure, it's still under development. But it's still classed as a legacy language in all circles I've ever been in, and I've yet to meet anyone under the age of 50 who actively uses it (beyond playing around.)
-
@beegC0de @AlmondSauce ok ok I believe you guys 🙂
-
@Parzi use as many zero cost abstractions as you can and use tricks when you can't
So now I’m working with this code that is roughly documented because ”variable names are self-explanatory”.
Yeah, you just forgot that FORTRAN does not support utf-8 variable names...
Why utf-8? Because then if I see:
real :: 座標(3)
I would understand that you mean ”zahyō”, the usual 3D position array ”r(3)”, but no, I need to deal with:
real :: zah(3)
yeah...🙃🔫
rant