Who said they don't? This project is about porting existing stuff, for interoperability, etc. Not as a way to "avoid learning C".
>Don't you want to be closer to the underlying OS?
No, why would I want to do that unless I have a specific need for that?
At least if you're using a Unix-like system, then understanding POSIX is essential for knowing how things work starting on an intermediate level.
Anyway, C is a horrible language. Between Fortran and Ada it's unclear to me why C should be chosen for anything, inertia and herdthink aside.
All the infrastructure you're using goes through C/POSIX in one way or another. When things go haywire, you can only get by fixing it on the higher levels or just blindly restarting for so long.
EDIT: Only true if you use the implicit-none flag when compiling Fortran.
But the approach is to get the correct translation first, and then - if needed - bottlenecks can be removed manually. This should lead to a better migration/upgrading experience.
Why do young students no longer learn C? Don't you want to be closer to the underlying OS?