Yo, there are so many modern #JavaScript frameworks and workflows!! 😅

I'm extremely fond of @preact, which makes me really excited to use #Fresh and @deno_land (especially now that #Deno supports NPM).

I'm trying my best to keep-up with all the ongoings, but I just learned about #Qwik today and I finally grokked what #Vite and #PartyTown do. 🤪

How does anyone keep all this JavaScript stuff straight? What's current, legacy, upcoming? 😅

@mike I think I always try and go for a balance of great and well-supported - that’s why my current stack of choice for frontend is TypeScript, Vite and React. And Tailwind for quick styling. There’s also loads of other great libraries I use like date-fns and lodash.

@mike It moves way too quickly to keep up with. Use whatever seems best at the time you start a project and stick with it.

I tend to read rants by disgruntled engineers and see what frameworks they like.
https://infrequently.org/2023/02/the-market-for-lemons/

The Market for Lemons

New web services are being built to a self-defeatingly low UX and performance standard, and existing experiences are now pervasively re-developed on unspeakably slow, JS-taxed stacks. At a business level, this is a disaster, raising the question: why are new teams buying into stacks that have failed so often before?

Alex Russell

@mike I just started using TypeScript at the beginning of 2022, and they threw me into the deep end with frameworks and then all of the AWS stuff all at once. It's overwhelming.

Now I'm on like nine newsletters and spend a lot of time reading to keep up.