Hacker News Reader

Comment by TranquilMarmot | Hacker News Reader

The author of react-query (one of my favorite libraries) also just released the beta of yet another router called React Location: https://react-location.tanstack.com/

I've used Reach Router in the past and it's also pretty nice, but I didn't see a reason to use it over React Router... https://reach.tech/router/

View on HN

Wow, another library (react-location) that shows TypeScript as its primary documentation language. And I see more and more jobs hiring for TypeScript developers.

I see Microsoft's 3 E's campaign strongly in action with TypeScript.

For those who care about Corporate Ethics, please review Microsoft's: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

For that reason, I refuse to touch TypeScript libraries-- out of sheer anti-corporate-oligarchy ethical conviction.

Well, it's open source and they aren't going to extinguish JavaScript anytime soon. So I don't see how it would apply here.

Microsoft are actively hostile towards JavaScript now. I have been monitoring the progress of vscode's support for JavaScript and noticed that it now clearly a second class citizen. The TypeScript compiler now declares valid and working JavaScript as having errors, and these are displayed to the user in vscode. One example is the usePrevious hook as mentioned on the react website. If you mouse over its signature in vscode, you will see it is undefined -> undefined. This is because useRef() has no argument, and the generic type is inferred from this argument, and JavaScript has no way to do useRef<T>();

If you're going to about Microsoft's ethics, it's probably also necessary to complain about Facebook's ethics since they own React.

Vue has an official router library, but react seems to have multiple popular routing libraries. Reinventing the wheel much?

How is anyone supposed to get a job if they don't promote their own fiefdom?

I've definitely found it a little weird how React doesn't have a more official routing library, especially since they are all so similar.

It feels like Next.js is taking over a lot of things that React _should_ have by default but doesn't. Which is fine, but Next.js is also a little too much for a lot of smaller projects I work on.

Reply on news.ycombinator.com