Echo JS 0.11.0

What about grouping by multiple properties and with custom sorting? :)

Flutter is a better product technically:
- Dart is a great language
- It compiles to native (perf)
- It's built up from a low level drawing lib (skia), meaning all the components are fully customizable. You also have access to do low level drawing (in React Native you have to go into native code or use a third part lib like react-native-svg)
- Also because of this they can translate the low level drawing commands to HTML canvas in a way that will always be more robust and complete than RN solutions
- It doesn't suffer from async issues, e.g. if you validate the value of an input (e.g. max length) there is a race condition between the user typing and the JS thread validating so the user can type more chars than intended. I've seen companies having to employ native developers to re-do controls like inputs just to be able to move validation to native code and not have that lag.
- It has better built in animations
- It has a much better development experience esp. in VSCode (great dev tools)
- You can use symlinks on NPM packages making developing a UI lib and symlinking into your project possible
- No ambiguity between choosing Expo vs RN CLI
- More officially supported plugins to do things like interfacing with the device

React Native advantages
- Familiar to web and React developers
- Easier to recruit for

Nicely written article, hope Solid gets big it's the best balance between lightweight and incredible performance + the best parts of React

Never understood why people need a library to make a form

Nice work, would be good to see how it stands up on https://github.com/krausest/js-framework-benchmark

I would say use interface unless you have to assign something (=)

It won't be popular since the author dropped official JSX support, people like to code with JSX or template literals

Same can be argued for other serverless products (AWS Lamba, GCP Cloud Functions, Firebase etc)

Yeah never got this bashing JS for things like NaN !== NaN literally there in every language. On this note though I find it irritating that there are 16million NaN values, the author of the spec's reason is that representing NaN only takes a few bits and he had a bunch left over to try and be descriptive of what numbers went in (bit fuzzy on this as you couldn't represent both numbers in that space anyway). Either way no one uses that and yet you get languages like Rust that are obsessed with correctness not implementing any sorting or ordering for floats because NaN !== NaN by spec definition so they can't be ordered.. sigh