leonardopainter

3 ms·

1.
by leonardopainter 5y ago
Well, I think when they moved away, they also increased the complexity of their applications as well.
2.
by leonardopainter 5y ago
My library (see other comments) has components that are about half the amount of code as react or solid and in pure javascript. The javascript shows exactly was is happening, as opposed to the "simplicity" of react that shows a pr
3.
by leonardopainter 5y ago
In terms of the placeholders in JSX, no they are escaped.
4.
by leonardopainter 5y ago
<img src='x' onerror='alert(1)'> https://developer.mozilla.org/en-US/docs/Web/API/Element/inn...
5.
by leonardopainter 5y ago
One reason is probably that creating UIs programmatically was historically very cumbersome in JavaScript due to various issues that are no longer relevant. That means everything had to be HTML-based hybrids of some sort.
6.
by leonardopainter 5y ago
Using template literals to represent html is a security issue. If the state comes from the user, they can add script tags into the html. People try to solve this with tagged templates, but then if you forget the tag, you have a security iss
7.
by leonardopainter 5y ago
That isn't a solution. Everybody moved away from this approach for web applications for good reasons.
8.
by leonardopainter 5y ago
The problems with knockout were: very hacky syntax embedded into html. Sometimes you had to even use some kind of comment notation because there was no entry point into the html to add data properties or whatever it had. it was slow. the ob
9.
by leonardopainter 5y ago
>If a linter is required to tell me when I'm writing a bug that is not immediately obvious, that is a failing in the framework to round those edges. Lints are not rounded edges! Those linter warnings with React hooks show just how m
10.
by leonardopainter 5y ago
>The reason _why_ React has a virtual DOM is to enable more interesting relationships between your data and your presentation. Anyone can make a framework that makes the source code for an incrementing number look pretty! Actually, that
11.
by leonardopainter 5y ago
This article points out how ridiculous React is. This is just a simple timer, yet there are so many things you can get wrong. This article doesn't seem to even clear the interval so it runs forever. Solid solves some problems, but I do