Reactive Java.

I actually rather like it, I really do. But the shift in mindset required, and the limited advantages (especially with fibres under heavy development) both mean I think it's incredibly unlikely to last.

Well idk, it's been around for a while already :) and the mindset is not that off.. I think it's gonna last. And evolve further.

Today I tried to explain the shift in mindset required to use React with more performance in mind, including JSX, opposed to Vue. Fortunately, this frameworks hive is not as major as general usage language, like Java. Choosing between programming languages makes you think about learning curves and getting right people in project, concentrating skills on product itself rather than shallow routines. And in that sense, trade-offs exist everywhere, even in my beloved Node.js, which isn't so popular to be installed on average person's PC, and its version number grows too fast, language is being interpreted by binary. But I liked it immediately, solely just because of learning curve :)

Stream based programming in general is only going to get hotter at good companies. Reactive programming and functional logic produce code that is infinitely less likely to have entropic issues.

At shitty companies that copy and paste from stack overflow, I agree and would even say it's a nonstarter.

@SortOfTested I hope so. This is one area that I really *want* to grow - the functional stream based programming model (so long as it's done properly, with immutable objects etc.) is great at reducing side effects, and the reactive libraries obviously capitalise on that.

My worry is that "shitty companies that c/p from Stackoverflow", in reality, is most companies.

Your critique applies equally well to ReactJS in front and development.