I've used it for some intensive computational applications, it's really quite nice (and fast) when you get the hang of it. Coming from Python it was quite the shock for me at first, however.
How does it compares to C? I’m a math’s student and I currently know Python and a bit of C. So I don’t know if it’s a good idea to also learn Fortran while learning C
@@MrCentrax I haven't done much work in C, so I can't really tell you. From what I have done, array operations are far, far better in Fortran. I've heard speed is roughly comparable between the two. Realistically though, just learn a single low-level language well and stick to it. No use in having sparse knowledge in multiple languages.
@@MrCentrax The gist of the Fotran vs C speed thing is that Fortran does not have aliasing by default, so the CPU internals don't have to check whether a value has changed in the meantime, this gives Fotran a slight edge over C that you can also get in C by using restrict keyword.
Was glad to see this. A few years back, I had to make some updates to some very old stats code written in Fortran and your experience here was about what I went through.
Tsoding: Does my program compile and call to Raylib and initializes the Raylib correctly? It fucking does! 1:49:25 Meanwhile, the Raylib log: Screen size:645031064 x 645031068 Explanation: Fortran passes its arguments by reference but C passes by value. Therefore, the C code receives the addresses for width, height, and fps as values. This also explains why the values for width and height differ by 4, it's the size of an integer. To correctly pass an integer from Fortran to C, you have to specify it like this: `integer(kind=c_int), value :: width, heigth`. BTW: 800 is an integer literal even in Fortran.
fortran is a very interesting language, because even after all these decades people still really care about it and is actively trying to keep up with the rest of the "new" "cool" "languages" like java and c++
I remember cloning the full repo of GCC from a house lost in France's countryside with a VERY SLOW wifi conexion during a holiday. It took me more than an hour
About the implicit typing in minute 16:00. I suppose that comes from really old languages like B where types didn't exist and you only had data that you treated however you wanted, so people started doing things like I_number to specify an integer or c_word to specify a character. I'm pretty sure that that was the only way to type data in older versions of Fortran too, and that would also explain why you put first the type and then the name.
@@maartenofbelgium I would bet on reducing the compiler's functionality: cards were cheap and could be provided (and wasted) in industrial amounts, but memory, where the compiler should reside, was totally not. Wikipedia says that on IBM 1401, the compiler lived completely in the core memory, the whole whooping 8000 x 6 = 48,000 bits. This required 2200 cards.
@@JinskuKripta actually starting from a million i think you do something like "eine Million zweitausenddreiundzwanzig" for 1002023, but for integers in [0, 1000000) you are right
Very nice video. As someone who has done a bit of work in fortran 77 this was very entertaining. I would love to see more fortran content in the future!
The main times I had to know about implicit variables when I studied Fortran in the mid 70s were when I used the fact that the letters “i” through “n” were reserved for integer values. This made them the default for loop variables. If you had a counting loop, you usually wrote “ do i = 1, 10” as opposed to using “c” or “d” or whatever and if there were nested loops you go to “j” as your variable and so on through the alphabet.
i,j,k etc are implicitly integers for loops. Given most of the work I did was matrix calculations you do a lot of nested loops and those are the conventions for loop counters anyway
In punch cards, one line = one card. "PROGRAM program" is the title card for the program, and each card is 80 characters long, so it really doesn't matter how long the name is
1. Initial star is like format in printf in C - except star means 'please compiler deduce the format on your own' 2. You've got implicit typing completely wrong xDDD 3. Procedures and functions are 2 different things in fortran 4. Several times in the video you want to have complete example but you DO have it at the same page - just a few lines lower XD like with the c/fortran bindings xD
For those playing at home, the * for print tells it that it is List-Directed I/O. For the read (*,*), the first star means read from stdin, the second star means you are reading list-directed IO
Oh wow that's timely I recently started being interested in Fortran, because of Exercism (a platform for programming exercises in deferent languages), the theme of this month on there is old languages, including Fortran Thanks, this will help me with learning about this cool language
for hexa you can use Z so like... integer(c_int32_t), parameter :: COLOR_RED = int(Z'FF0000FF', c_int32_t) and then pass COLOR_RED to clear_background.
i remember when i was in university i took pride on how many languages i "knew". then, like you, i realized knowing languages was useless and understanding fundamentals was universal. and now, i can't even remember all of the languages i used to boast about knowing proudly 😂
You should do something like Mandelbrot's set in Fortran. I think with such a task you can see where the language shines... Intrinsic COMPLEX type and easy vector/matrix operations
On my physics course i had to learn fortran, it is pretty solid for scientifc stuff, not gonna lie. But doing on python simoler stuff is much better, depends on the project honestly, maybe both. Good language
Honestly thanks to this video I sat down and wrote a program to ASCII plot the mandelbrot set, which is probably the furthest I've ever gotten with any programming language despite on and off dilettantism.
The part where you compiled empty files reminded me of a submission to IOCCC of a quine that was an empty file: there was a bug/feature in one particular C compiler that caused it to compile and link an empty file to create a program that outputs nothing (its source code!) when run.
The problem here is not Fortran, but the professor who requires you to learn such an outdated version of the language. It's absolutely nonsense, as if you were forced to learn the original K&R version of C.
@@davideferrara6274 OK, that's really nonsense... Even if the guy was a god in numerical analysis there would be no excuse for teaching with such outdated tools. The university should not let him continue like this.
I did my Bachelor's thesis in a research group which did numerical research on quantum physics. Most people in the group used python, some C++ and only the prof / group leader used fortran. Everyone admired him for mastering fortran.
i learned this in my math uni programme, i could do it all but i failed the paper exam where i had to cross a 2d array diagonally, broke my brain and i dropped out
I remember working with a IBM AS400 back in 2000 and you would have engineers trying to update code and forgetting that for certain languages you had to explicitly state the version for the compiler to work lol.
I dont know if you r into that stuff but it would be interesting to see you doing something with distributed systems, like message queues or actor systems for example
Your speed and concentration are amazing but of course your experience programming weights. Question if you don't mind: Did you go to college to study CS, Software development... ? or are you self-taught?
@@hedlund Many core linear algebra libraries are still in Fortran, even when they have a C API. So, numpy is maybe written in C, but it very likely calls some Fortran code at some point (and this is granted for scipy or Matlab)
These know it alls that know nothing really piss me off. I was once asked by a leading footwear company to make their overnight run go faster. It took so long that the customers could not buy anything in the stores until ten o'clock in the morning. So I looked at the job and realised that their "best practice" sql coding was hugely inefficient and I used some old fashioned DP tricks. I reduced the runtime by seven hours as my code ran 10 times faster. These arrogant SQL experts told me that even though my code worked perfectly and was ten times faster than theirs I had still done it "wrong".
Did you know that Python's `**` exponentiation takes an absolute value of exponent? I did not tested is this happens before exponentiation or after, but it does this. And it is slower than calling pow()
Mister, I know you're so frustrated. Let me help you. Fortran IV came out in the 1960s, and it was a vast improvement over prior versions. Then in 1977, the quintessential FORTRAN77 was released. That was what FORTRAN was. Then in 1990 Fortran 90 was released, and many people say this was the start of Fortran not becoming FORTRAN. It was now taking on characteristics of C and Pascal. So, yes, that space that gets added in front of a printed line is some6i have no idea why Fortran compiler does that. But I do know about IMPLICIT. You see integers used to be automatically typed (implicitly typed) if the variable name began with a letter from I to N as in I--->Ntegrer. If the variable began with any other letter then it was of REAL type. So if you add implicit none, then the programmer doesn't have to worry / think about whether all the integer type variables are beginning with letters i, j, k, l, m, or n. Now about why your program didn't compile when it had the .f extension. You are right that the extension tells the compiler what "Fortran" it is. Prior to Fortran 90, the language worked still like it did with punch cards. Column 1 is reserved for or C. If C were in Column 1, then that line would be a comment. Columns 2 through 6 were reserved for numeral labels just like you were thinking. And, finally code had to be in Column 7 onward, but I think only out to Column seventy-something or eighty. You didn't have the code starting in Column 7 when you were using .f as the extension. The compiler was trying to compile the code as FORTRAN77 code.
Now I remember what is special about Column 6 and why the presenter noticed his Gnu EMACS editor colorizing the 'e' that he had type in that column. Column 6 took a non-zero, non-blank character to indicate continuation of the code typed in the line above, because as I mentioned, FORTRAN77 and prior versions, had fixed formatting that came from the days of punch cards. Column 1 was for the letter 'C' if a comment was desired; Columns 2-6 were used for numeric labels that could be any numeral, allowing for that crazy GOTO statement to find where to go, and Columns 7-72 were reserved for code. Any characters written in Columns 73 onward would be ignored by the compiler and thus comments or annotations could be placed in this field if so desired.
yes ! modern software lives off its users unpatiently awaiting the next update/bugfixes.... the more frequent they get their fix the better :) "ohhh A was broken now they fixed A but there is a new bug in B cant wait for next patch and hope they include fix" ... vs. "what ? you are telling me this program runs perfectly bug free? boring ... it must be malware... i will find a better one!"
I'm not sure if this was meant to be only joke but I experienced this literally with Apple. 2 or 3 years ago they demanded that ALL iphone apps must be updated, but my app already work perfectly as it was so I ask them 'what do you want me change?' they told me it was not necessary that I change anything but I must increase the version number! In the version release notes I put 'new in this version: absolutely nothing except version number'. Apple actually phoned me up to tell me this is not 'appropriate'
Seeing an arrogant young programmer bad mouth Fortran shows how utterly ignorant modern people have become. If you look around you at Supersonic aircraft, Nuclear Power Stations, Space Rockets, High Performance cars, Trains nearly all of the modern high tech world was developed using Fortran. It is also the most efficient programming language for calculations because it most closely resembles machine code and has to be used in large complex calculations like weather prediction.
_"Who uses FTP in 2023"_
- THE MAN LEARNING FORTRAN IN 2023
(great stuff, appreciate your content)
To be fair, you have to give a seed to the rng, so harvesting the random number makes sense since it sprouted from seeds
Yes! I am a physics student and I know many Phd Students that still use Fortran! It is actually very nice for scientific programming
I've used it for some intensive computational applications, it's really quite nice (and fast) when you get the hang of it. Coming from Python it was quite the shock for me at first, however.
How does it compares to C? I’m a math’s student and I currently know Python and a bit of C. So I don’t know if it’s a good idea to also learn Fortran while learning C
@@MrCentrax I haven't done much work in C, so I can't really tell you. From what I have done, array operations are far, far better in Fortran. I've heard speed is roughly comparable between the two. Realistically though, just learn a single low-level language well and stick to it. No use in having sparse knowledge in multiple languages.
@@MrCentrax
C is more useful in a wide variety of applications. If I had to choose one I would choose C for it's flexibility advantage.
@@MrCentrax The gist of the Fotran vs C speed thing is that Fortran does not have aliasing by default, so the CPU internals don't have to check whether a value has changed in the meantime, this gives Fotran a slight edge over C that you can also get in C by using restrict keyword.
Was glad to see this. A few years back, I had to make some updates to some very old stats code written in Fortran and your experience here was about what I went through.
I hope you managed to get the shit done anyway 🫂
Tsoding: Does my program compile and call to Raylib and initializes the Raylib correctly? It fucking does! 1:49:25
Meanwhile, the Raylib log: Screen size:645031064 x 645031068
Explanation: Fortran passes its arguments by reference but C passes by value. Therefore, the C code receives the addresses for width, height, and fps as values. This also explains why the values for width and height differ by 4, it's the size of an integer. To correctly pass an integer from Fortran to C, you have to specify it like this: `integer(kind=c_int), value :: width, heigth`. BTW: 800 is an integer literal even in Fortran.
Loved the confusion caused by the fact he was passing ints by pointers
Zozzin, thank you for the Fortran session! Please also consider Standard ML. It is a lot of fun.
OCAML is even better, but id love to see him code in either
@@philstanton8912 He's done a few videos in OCaml before, including one recently that was more of a joke
@@philstanton8912 Standard ML is unique, OCaml does not have such a powerful module system, it had to compromise a lot.
fortran is a very interesting language, because even after all these decades people still really care about it and is actively trying to keep up with the rest of the "new" "cool" "languages" like java and c++
I remember cloning the full repo of GCC from a house lost in France's countryside with a VERY SLOW wifi conexion during a holiday. It took me more than an hour
About the implicit typing in minute 16:00. I suppose that comes from really old languages like B where types didn't exist and you only had data that you treated however you wanted, so people started doing things like I_number to specify an integer or c_word to specify a character.
I'm pretty sure that that was the only way to type data in older versions of Fortran too, and that would also explain why you put first the type and then the name.
Fortran _is_ that old language. Since it catered to numerical computations, it had integer and float variables from the start.
Implicitly typing/defining a variable made sense in the 70ies: you saved a punch card.
@@maartenofbelgium I would bet on reducing the compiler's functionality: cards were cheap and could be provided (and wasted) in industrial amounts, but memory, where the compiler should reside, was totally not. Wikipedia says that on IBM 1401, the compiler lived completely in the core memory, the whole whooping 8000 x 6 = 48,000 bits. This required 2200 cards.
"Learning german in 2023" when?
nie
In 2023
@@andrewdunbar828in German the numbers are written all together, not in separated words, like this: Zweitausenddreiundzwanzig
@@JinskuKripta fucked up.
@@JinskuKripta actually starting from a million i think you do something like "eine Million zweitausenddreiundzwanzig" for 1002023, but for integers in [0, 1000000) you are right
Very nice video. As someone who has done a bit of work in fortran 77 this was very entertaining. I would love to see more fortran content in the future!
The main times I had to know about implicit variables when I studied Fortran in the mid 70s were when I used the fact that the letters
“i” through “n” were reserved for integer values. This made them the default for loop variables. If you had a counting loop, you usually wrote “ do i = 1, 10” as opposed to using “c” or “d” or whatever and if there were nested loops you go to “j” as your variable and so on through the alphabet.
I learned to program in Fortran. I really loved it. Lots of matrix operations and computational methods
i,j,k etc are implicitly integers for loops. Given most of the work I did was matrix calculations you do a lot of nested loops and those are the conventions for loop counters anyway
I recently decided to learn Fortran. I’m glad I saw you learn it as I was.
Fuck it, learning Simula in 2023. I would enjoy that one haha
In punch cards, one line = one card. "PROGRAM program" is the title card for the program, and each card is 80 characters long, so it really doesn't matter how long the name is
1. Initial star is like format in printf in C - except star means 'please compiler deduce the format on your own'
2. You've got implicit typing completely wrong xDDD
3. Procedures and functions are 2 different things in fortran
4. Several times in the video you want to have complete example but you DO have it at the same page - just a few lines lower XD like with the c/fortran bindings xD
I think he figured out 1 somewhere at the 1:20:00 mark. When he was looking at the bindings
Can you explain point 2?
For those playing at home, the * for print tells it that it is List-Directed I/O. For the read (*,*), the first star means read from stdin, the second star means you are reading list-directed IO
This is hilarious, one of the funniest streams, and that's saying something!
Hey CZcams! I really enjoyed watching Fortran series live. Hope you enjoy it as well. Make tea and grab cookies - Zozzin's struggling incoming.
Oh wow that's timely
I recently started being interested in Fortran, because of Exercism (a platform for programming exercises in deferent languages), the theme of this month on there is old languages, including Fortran
Thanks, this will help me with learning about this cool language
I liked Fortran, especially matrices multiplication 🥰🥰🥰😘😘😘
for hexa you can use Z so like... integer(c_int32_t), parameter :: COLOR_RED = int(Z'FF0000FF', c_int32_t) and then pass COLOR_RED to clear_background.
"it's just like people from 70s and 50s decided so" - best answer to all questions.
That was fun, I would love to see you exploring other jurassic languages as well.
Learning perfocards in 2023
REAL MEN scratch bits onto the plates with a needle.
Fortran is a modern language, with OOP and other nice features :)
at my uni they teach fortran 77 along with C and year later they changed to fortran 90
Cutting edge technology pog
"GOD" is real, unless declared as an integer
i remember when i was in university i took pride on how many languages i "knew". then, like you, i realized knowing languages was useless and understanding fundamentals was universal. and now, i can't even remember all of the languages i used to boast about knowing proudly 😂
Older versions of fortran needs a 7 lines of space to run properly, the thing is that old fortran works on new versions of fortran
Personally I never use print i use write(*,*) star is to format it and the other star is for the screen
Спасибо за стрим, и за подкачку моего английского!!!
16:16 there was a practice of having the type in front seems handy if you have to type panchcards
Will you ever do a Tcl stream? The syntax is so simple it's actually insane
You should do something like Mandelbrot's set in Fortran. I think with such a task you can see where the language shines... Intrinsic COMPLEX type and easy vector/matrix operations
In fact the R programming language is partly written in Fortran
It's really fun to see you struggle with my favorite language :)
I actually started using Fortran this year just for the meme and have to say for the little things I do its actually not bad
That Emacs magic with transpose is legit awesome 28:05
31:23 you can refer to program:
program yepp;
procedure hello;
begin
writeln('yepp');
end;
begin
yepp.hello;
end.
On my physics course i had to learn fortran, it is pretty solid for scientifc stuff, not gonna lie. But doing on python simoler stuff is much better, depends on the project honestly, maybe both. Good language
Honestly thanks to this video I sat down and wrote a program to ASCII plot the mandelbrot set, which is probably the furthest I've ever gotten with any programming language despite on and off dilettantism.
The part where you compiled empty files reminded me of a submission to IOCCC of a quine that was an empty file: there was a bug/feature in one particular C compiler that caused it to compile and link an empty file to create a program that outputs nothing (its source code!) when run.
I had to learn this language for my Numeric Analysis exam and it was a nightmare! I learned F77 not even F90 inside a WIN95 IDE application.
The problem here is not Fortran, but the professor who requires you to learn such an outdated version of the language. It's absolutely nonsense, as if you were forced to learn the original K&R version of C.
@@pehache2 The professor is 73 years old that's why.
@@davideferrara6274 It's an explanation. Still, it's not acceptable. But it also depends on when it was, actually.
@@pehache2 it was about 4 months ago
@@davideferrara6274 OK, that's really nonsense... Even if the guy was a god in numerical analysis there would be no excuse for teaching with such outdated tools. The university should not let him continue like this.
15:50 Hence "GOD is REAL, unless declared INTEGER"
the first letter being the type comes from Hungarian notation
I did my Bachelor's thesis in a research group which did numerical research on quantum physics. Most people in the group used python, some C++ and only the prof / group leader used fortran. Everyone admired him for mastering fortran.
i learned this in my math uni programme, i could do it all but i failed the paper exam where i had to cross a 2d array diagonally, broke my brain and i dropped out
15:52, 18:54 ;) really interesting session, would like to see more old stuff 👍
Fortran is very old. In early versions the format of the lines are very strict fixed. There are Variables, that are handled special,
15:55 I LOVE HOW HE BREAKS DOWN LOL
01:08:52 [i for i in range(1,6)] == [1,2,3,4,5]
How many more years until you make your own OS in HolyFortran
preferably without going insane
I remember working with a IBM AS400 back in 2000 and you would have engineers trying to update code and forgetting that for certain languages you had to explicitly state the version for the compiler to work lol.
Based Chad Fortran
Do Julia please.
He's lost a crazy amount of weight in only two years
I’m curious to know if llvm flang produces better error messages.
submissive and allocatable 🥵
NASA preferred language after Assembly language for Voyager software update
Yeah i learn it 27 year ago; it for numerical analysis, nothing with system programming or other stuff like c and c++ ;
I dont know if you r into that stuff but it would be interesting to see you doing something with distributed systems, like message queues or actor systems for example
15:42 -> 21:00
yay, F is cool lang btw
That would be interesting to see more of that
could you post the rest of the series now that its gone on twitch. thanks man, I appreciate your content.
Thank you.....
please tell more for your hyper-focused programming state
Your speed and concentration are amazing but of course your experience programming weights. Question if you don't mind: Did you go to college to study CS, Software development... ? or are you self-taught?
i think he went to college to study a branch of chemestry. i found this info on his first machine learning video
@@caiodavi9829 Thanks for the hint. Regardless where he learned from, he's a very brilliant programmer.
Rust is bad language but still better than C or C++ 😎😎😎 We need new language that really replace C++ and be much better than Rust
Nim ? Odin ?
But Zozzin when will we have an Oberon stream?
You should do a vid where you program in INTERCAL for a few hours
Thank you for making Fortran learning videos. Is it possible to use Fortran compiler in Visual Studio?
The Intel Fortran Compiler can be used in VS
YOU BOUGHT A NEW KEYBOARD
Last time I used Fortran we used punchcards.
The actual joke is that a lot of scientific software and libraries (like matlab, ansys, numpy ) are written entirely in fortran
Isn't numpy written in C?
@@TheMelopeus nope numpy is written in fortran
@@francescotomba1350lol wtf stop lying
Wait, what? No idea about Matlab and ansys, byt Numpy is C (and Python, obv.), and always has been, as far as I know.
@@hedlund Many core linear algebra libraries are still in Fortran, even when they have a C API. So, numpy is maybe written in C, but it very likely calls some Fortran code at some point (and this is granted for scipy or Matlab)
supposedly something like `integer width, height, fps` should work
works on my machine :P
These know it alls that know nothing really piss me off. I was once asked by a leading footwear company to make their overnight run go faster. It took so long that the customers could not buy anything in the stores until ten o'clock in the morning. So I looked at the job and realised that their "best practice" sql coding was hugely inefficient and I used some old fashioned DP tricks. I reduced the runtime by seven hours as my code ran 10 times faster. These arrogant SQL experts told me that even though my code worked perfectly and was ten times faster than theirs I had still done it "wrong".
Why @12:13 we have star *? Because for C++ we end line by ;
теперь изучай cobol
raylib prints the window size but you kept ignoring it lolol i was like oh no his window dimensions are fucked
Did you know that Python's `**` exponentiation takes an absolute value of exponent? I did not tested is this happens before exponentiation or after, but it does this. And it is slower than calling pow()
Exponentiation takes precedence over unary minus, so you need to use parentheses like this: (-5)**3
@@user-ni2we7kl1j (-5) there would be the base though, not the exponent?
Mister, I know you're so frustrated. Let me help you. Fortran IV came out in the 1960s, and it was a vast improvement over prior versions. Then in 1977, the quintessential FORTRAN77 was released. That was what FORTRAN was. Then in 1990 Fortran 90 was released, and many people say this was the start of Fortran not becoming FORTRAN. It was now taking on characteristics of C and Pascal.
So, yes, that space that gets added in front of a printed line is some6i have no idea why Fortran compiler does that.
But I do know about IMPLICIT. You see integers used to be automatically typed (implicitly typed) if the variable name began with a letter from I to N as in I--->Ntegrer. If the variable began with any other letter then it was of REAL type. So if you add implicit none, then the programmer doesn't have to worry / think about whether all the integer type variables are beginning with letters i, j, k, l, m, or n.
Now about why your program didn't compile when it had the .f extension. You are right that the extension tells the compiler what "Fortran" it is. Prior to Fortran 90, the language worked still like it did with punch cards. Column 1 is reserved for or C. If C were in Column 1, then that line would be a comment. Columns 2 through 6 were reserved for numeral labels just like you were thinking. And, finally code had to be in Column 7 onward, but I think only out to Column seventy-something or eighty. You didn't have the code starting in Column 7 when you were using .f as the extension. The compiler was trying to compile the code as FORTRAN77 code.
Now I remember what is special about Column 6 and why the presenter noticed his Gnu EMACS editor colorizing the 'e' that he had type in that column. Column 6 took a non-zero, non-blank character to indicate continuation of the code typed in the line above, because as I mentioned, FORTRAN77 and prior versions, had fixed formatting that came from the days of punch cards. Column 1 was for the letter 'C' if a comment was desired; Columns 2-6 were used for numeric labels that could be any numeral, allowing for that crazy GOTO statement to find where to go, and Columns 7-72 were reserved for code. Any characters written in Columns 73 onward would be ignored by the compiler and thus comments or annotations could be placed in this field if so desired.
hey mate I know this might be an odd question but - were you at minecon in 2015?
yes ! modern software lives off its users unpatiently awaiting the next update/bugfixes.... the more frequent they get their fix the better :)
"ohhh A was broken now they fixed A but there is a new bug in B cant wait for next patch and hope they include fix" ... vs.
"what ? you are telling me this program runs perfectly bug free? boring ... it must be malware... i will find a better one!"
I'm not sure if this was meant to be only joke but I experienced this literally with Apple. 2 or 3 years ago they demanded that ALL iphone apps must be updated, but my app already work perfectly as it was so I ask them 'what do you want me change?' they told me it was not necessary that I change anything but I must increase the version number! In the version release notes I put 'new in this version: absolutely nothing except version number'. Apple actually phoned me up to tell me this is not 'appropriate'
@@MikeHunt-fr7coBRUHH😂😂😂
What keyboard are you using, or did you build it yourself?
They did NOT give a damn about usability back then 😂
but why?
still waiting for the continuation
Five spaces has meaning?
Is fortran also memory safe before Rust
Seeing an arrogant young programmer bad mouth Fortran shows how utterly ignorant modern people have become. If you look around you at Supersonic aircraft, Nuclear Power Stations, Space Rockets, High Performance cars, Trains nearly all of the modern high tech world was developed using Fortran. It is also the most efficient programming language for calculations because it most closely resembles machine code and has to be used in large complex calculations like weather prediction.
ok boomer
depth one moment
1:14:16 bruh it didn't print the "!"
dude, they just was saving memory by typing with first letter...
❤
you're cool!
Do a video with R please! :D
1:02:54 You can feel Volker Strassen's hiccups here :D
Want more video on Fortran
You cant be mad at language that was designed to be written on punch cards
Why would this library’s website block your IP?
There is a lot of dangerous hackers in the place where I live. Who knows maybe they may try to use the library to hack somebody. ;)