I don't understand the article. It stresses that you don't need to run code on a Python server any more.
That assumes that the only option for scientists is to interact with the browser. Scientists used to be able to write Fortran and didn't rely on a crappy web interface. That was of course when they did science instead of blogging about tools.
It's not the only option but jupyter notebooks are excellent for (at least) quick prototyping, data visualisation, literate programming and exploring ideas. I write plenty of Fortran and C++ and I still reach for notebooks when appropriate.
In discussing with a non-technical, scientist friend, she pointed out that existing notebooks can be used and edited by folk even if they don't know python that well.
At the very least I see this particular tech as enabling more science by removing the operational challenge of running a jupyter server.
These tools take nothing from those who want to write fortran to do their science but make computation more accessible to those who don't.
I don't understand the article. It stresses that you don't need to run code on a Python server any more.
That assumes that the only option for scientists is to interact with the browser. Scientists used to be able to write Fortran and didn't rely on a crappy web interface. That was of course when they did science instead of blogging about tools.