alt Hacker NewsSad. I thought Meta did a lot of things right when it came to using engineers, especially compared to Google. If I had a choice between React (Facebook) and Kubernetes (Google) I would pick the former anyday.
Kubernetes has held back cluster technology for the last decade and prevented a better alternative for smaller companies or companies that can't piss away monopoly profits on unwieldy technology and process. It would have been much better had somebody tried to make an open source product based on IBM's old Parallel Sysplex but there gotta be patents in there (now expired though!)
As much as people like to complain, React has come out on top in a highly competitive market. I've looked at a lot of systems for building UI objects which look superficially similar like Microsoft's XAML and Oracle's FXML and React's system is by far the most simple and flexible... An example that shows you can apply the ideas in On Lisp to any language which has basic functional programming practices with just a tiny compiler tweak on top to make it fluent.
Replies
Why would you compare React to Kubernetes instead of comparing React to Vue.js?
How do you decide to use useContext, useReducer, useState, or a third party management tool to manage state?
(I know useContext isn't great for state management, but I've worked on a web application where useContext was used to store complex global state).
> If I had a choice between React (Facebook) and Kubernetes (Google) I would pick the former anyday.
Can you elaborate on why these are at all comparable techs to use as a developer?
React seems to be the frontrunner in FE, but what do you see the BE equivalent to be?