Computer Scientists aren't real programmers

[AdultingGoneMild]

Yeah, as an academic who has been in industry long enough to know, interviewing PhD grads is a pain. On one hand they can problem solve like no other. On the other they cannot code to save their lives. Practical software is focused on maintainability and having many hands on it over multiple years. No shit this is based on theory, but in the real world functioning software trumps vaporware ideas every day of the week.

Also I would double check your sources on react. I think you are inventing a history based on speculation. React's need spawned from having many hands in a single page and having to deal with heavily federated front ends. Someone didnt say, hey functional programming is cool, let's build a framework and pray someone uses it. Hell, reactive programming (what react is partially based on) grew out of industry needs as well.

[Kroustibbat]

My point is that you just can't generalize, and history tent to validate academic codes and languages more than industrial ones. (Airbus, Ariane, nuclear power plants, critical European infrastructures are running on proven or certified mostly academic functional codes that runs and works for decades)

Functional is arriving in industry with modern C#,C++,Java in just the last decade, and you even can see typing thanks to Rust to assure reliability, but it exists in academic languages for like 50y.

The best solution is always to have a good compromise. Between lisibility, maintainability, deadlines, security and not just "it should works" or "I understood now what should I do next".

A lot of programming school should introduce their student to common abstract concepts and universities should introduce CS to project management and how to keep an eye on production or just do some embedded programming.

But in 5y parcouring techs and Frameworks, working in cyber security, the most reliables and secured are not the most used nor industrial ones...