41–50 of 70 posts
Also, those performance benchmarks for esbuild are highly misleading. Parcel has a much faster update speed but they're comparing startup speed. Also, why disable caching? It seems highly contrived.
It even has enough stars to place it in the middle of the top 5 in the compiler category, despite not even being distributed/developed via github. And it gained them in just 3 months.
No QuickJS? That surely has to be a one of the more interesting new/rising projects in the compiler category last year. It even has enough stars to place it in the middle of the top 5 in the compiler category, despite not even being distributed/developed via github. And it gained them in just 3 months. https://github.com/bellard/quickjs
I come from a JVM/Python background, so not familiar with JS ecosystem at all. How do people decide what to use when there are 5 most popular libraries/frameworks in each category. Not saying the diversity is a bad thing. Just wondering how people make these choices when starting a new project.
1) Surrounding ecosystem. This is one of the reason React is so popular. The community and ecosystem of React packages is extremely large.
2) Personal preference. There really isn't much difference between React/Vue/Angular in terms of getting the job done (Same with most good libraries), so either you pick a library because you need a very specific piece of functionality from it, or you pick it because you/your team/your org prefers it.
As a somewhat fad averse engineer who has more or less settled into his own preferred toolchain for FE and BE JavaScript, I plan to invest some time in next.js, tailwind and emotion soon ish. Great to see the state of the art still being pushed. Might see how feasible porting my existing nodejs projects to deno is too.
I'd also recommend looking into https://chakra-ui.com/
Anyone using React Query in production? I've got ongoing projects using redux+axios, apollo client, and roll-your-own data fetch hooks. No clear winner in my book. React Query looks neat but have yet to try it.
Meanwhile, we in the Redux team recently published an alpha library that we've dubbed "RTK Query" [0]. It takes inspiration from data fetching libraries like React Query, SWR, Apollo, and Urql, and provides similar sophisticated data fetching and caching capabilities. But, it's built on top of Redux Toolkit, which enables integration with the rest of the Redux addon ecosystem and the Redux DevTools. Once we've finalized the design of the new APIs, we're going to merge them back into Redux Toolkit itself, so that they'll just be additional exports from Redux Toolkit. I'm really excited about how this will let Redux users simplify their code, and wrote a comment over on Reddit today about how RTK Query changes things for Redux users [1].
[0] https://rtk-query-docs.netlify.app
[1] https://www.reddit.com/r/reactjs/comments/kw9cr3/recently_pi...
The JavaScript community has a huge problem with hype and churning libraries unnecessarily. Using a metric like "number of new stars" just exacerbates that problem. It neither tells you about libraries are undiscovered gems, or libraries which are proven, stable and reliable. It's simply a measure of which libraries are well into their hype curve.
Some call them brogrammers. For their hipster-like approach to programming.
Believe it or not, a lot of them are on hackernews so they'll probably get super offended by this post.
I’m currently organizing a roadmap for improving my full-stack skills. I work in JS with Node and React. Does anyone have any opinion on whether I should spend time learning Deno and Typescript instead of digging deeper into what I already know? I find it hard to tell if Deno will start showing up in job descriptions in a few years, or if Node is so entrenched that it would only distract me from building on my curren…
Learn how to use Typescript, it's pervasive in the JS ecosystem and very easy to learn now.
As a somewhat fad averse engineer who has more or less settled into his own preferred toolchain for FE and BE JavaScript, I plan to invest some time in next.js, tailwind and emotion soon ish. Great to see the state of the art still being pushed. Might see how feasible porting my existing nodejs projects to deno is too.
When using Tailwind, don't forget that it is not only to be used as a utility-like CSS framework, but is also intended to build your own CSS systems. You can customize it and build your own classes using the `@apply` directive and other tools so that you don't copy/paste the same utility classes all over the place, but instead use CSS as we used to back in the good ol' days, with custom classes. :)
No QuickJS? That surely has to be a one of the more interesting new/rising projects in the compiler category last year. It even has enough stars to place it in the middle of the top 5 in the compiler category, despite not even being distributed/developed via github. And it gained them in just 3 months. https://github.com/bellard/quickjs