I work at a place that writes new Fortran code today. Also c++, Python, Julia. Scientists will choose the least impedance mismatch to a library, some needed data set, or their brain.
About this much more complex -- https://github.com/charlesap/bootpager
(example legacy boot block that jumps into protected mode, enables paging, and pages in and executes arbitrary code, no bios used.)
As mentioned above the trick is what to do once you're there. And it is a UEFI world now, might as well just write 64-bit PE kernel and be done with it.
One or more kicks are over here: http://harvey-os.org/ is taking the open-source Plan 9 code and getting it to compile with GCC and clang, etc. They have a userspace with APE (posix) compatibility and they almost have Google Go ported and they debug it with gdb... very much a work in progress though.
Well crap. Source code reputation is exactly the problem we are trying to solve at http://rputbl.com (sorry, just a splash page for now.)
We are nowhere near close to launch yet and there's a chicken-and-egg problem of having a sufficiently large database of hashes to make an arbitrary source code file reputation check worth your time, but we have some ideas about what to do about that too.
I'm using it to do http traffic analysis on captured packets... about 2.5 million packets a second at peak. This is to provide realtime charts for our web service which didn't have realtime reporting hooks.
I am also using it for HTTP request reconstruction and retransmission in real-time to enable live-data and full load testing of pre-production code.