Stars don't mean usage.

Remix has 21,375 downloads per week according to npm. Next has 6,562,587.

The remix package is no longer used[1]. Remix's central package is @remix-run/router[2], which has 5,627,846 downloads per week.

[1] https://github.com/remix-run/remix/pull/9433 [2] https://www.npmjs.com/package/@remix-run/router

Shameful ad for our own router: https://swan-io.github.io/chicane, with type-safe route consumption and creation (and other goodies).

No weirdness or magic API, the useRoute hook just return a discriminating union with typed params. It's fully-featured and used in prod.

The API is quite simple:

const Router = createRouter({ UserDetail: "/users/:userId" });

Router.UserDetail({ userId: "xxx" }); // safe

1. Stop shipping open source libs for a bit, focus on maintenance of the existing ones

2. Ship a SaaS I started working on

3. Improve my sleep

4. Improve my cooking skills

5. Read more books

6. Watch fewer, but better movies

7. Make a few talks

9. Spend more time with my family / my friends. Spend less with the kind who are not really your friends after all

10. Disconnect even more from social medias

11. Learn something new (could be anything)

No, you are right. Flutter isn't really native since it uses Skia to render native platform look-alike components (as opposed to react-native which really use the platform)

The result is that everything will look and feel slightly off, as the recreation of native elements will never be quite perfect.

More than just off. Especially on iOS there is a ton of functionality in those native controls thats going to be very hard to replicate.

As I’d guess most people spend most of their time in Chromium browsers and electron apps probably a case to make that ‘native’ in the sense you imply is Chromium!

I wrote a lib with a very similar API: https://github.com/zoontek/react-atomic-state

It rely on https://github.com/facebook/react/tree/master/packages/use-s..., which make it safe to use in concurrent mode and the implementation a lot simpler.

Might not be the best, but the ones I use:

For REST API: https://mockoon.com/

For GraphQL: https://github.com/APIs-guru/graphql-faker

This article is wrong about React: it does not generates unreadable CSS class names. CSS in JS libraries do.

By default, using only react + react-dom, you can achieve the exact same output as "handwritten HTML + CSS".

But CSS in JS is not bad either: it generates unique class names by using murmurhash on rules and it makes a lot of sense in a component approach (you can see it like an automatic BEM method).

Even better: The main pain point of this approach (runtime cost) will soon entirely disappear. Linaria already provides a solution, Facebook will soon roll is own (called StyleX for now). It will create a stylesheet file with atomic CSS rules (one rule per class) and replace the classNames directly at compilation time, offering deduplication, eliminates of dead code and maintenability without sacrificing performances. IMHO a huge step in CSS development.