netcommentator
netcommentator on Hacker News
Here's another JSX with Web Components:
https://github.com/wisercoder/uibuilderUnlike React etc this lib used W3 Components which are far superior because of Shadow DOM, which is already implemented in Chrome.
I am not familiar with the type of mistakes you are talking about. I have used both React and UIBuilder and find them to be comparable.
Would you be willing to share an example of the type of mistake that developers frequently make?
You don't do manual HTML manipulation with this lib either. You can just see your page as being composed of components and replace components in order to update screen.
You can divide your page into multiple components, then to update the screen replace the components that contain stale data. You do not have to deal with elements--you only have to deal with components.
Regardless of which library you use there is nothing preventing you from injecting DOM elements from everywhere. Only discipline can prevent that.
If you use Typescript you can get most of the benefits of React from this little library:
https://github.com/wisercoder/uibuilderIt doesn't support fine-grained screen update but you get support for Web Components (Polymer) which React doesn't support.
Facebook is being arrogant by not supporting the Web Components W3 standard.
XmlHttpRequest is an awesome innovation from the point of view of the software development community as a whole.
But from a Microsoft shareholder's point of view it was a disaster. XmlHttpRequest and ContentEditableDiv (known back then as DesignMode) ushered in Web 2.0 and Web 2.0 ended Microsoft's dominance of the software industry by making Windows irrelevant.
Given national security interests, we need new laws: 1. IOT devices should not ship with default passwords. 2. Internet infrastructure companies should not be allowed to get "too big to fail".