The Hidden Dangers of Switching Tech Stacks in 2023

Let's be friends: lwj.dev/discord - There are so many options for building websites in 2023. How do you know which is right for you? In most cases, the cost of switching (probably) isn't worth it.
Written version: lwj.dev/blog/switching-tech-s...
Chapters:
0:00 Sneak peak
0:14 The fastest website you can build
0:40 Most used JS framework in 2023
1:16 Social media hype bubbles
1:59 Good news, everybody!
2:16 Rebuilding vs procrastination
2:55 When is it worth it to switch?

[@rohithgilla9492]

The best take 🙌
All the end users care about is them interacting with the web application and not the stack under hood

[@tojeiro_me]

I've just seen two of your videos, and you address subjects that nobody is talking about. Maybe talking about the new thing it's more popular. It's like talking about CSS without mentioning Tailwind or JS without React. I'm always feeling like nobody is making websites, just apps. Thank you for making me feel that I'm not alone ;)

[@bossRODTV]

Nice video, I agree on your take that we can be as practical as much as possible and I totally agree on that especially if you are working on your personal projects and stuff. But I think choosing of tools are still important especially if you're really working on something bigger or in a company. But overall good point!

[@learnwithjason]

I think choosing tools is important, especially on greenfield projects. I worry more that we tend to elevate tool choice in scenarios where it doesn’t make sense because too much of the internet is screaming that you NEED to change to the latest tool or you’re DOOMED 😆

[@bossRODTV]

@@learnwithjason Couldn't agree more!

[@kotimara8711]

I love javascript and the ecosystem. But sorry to say this, the Twitter JS community seems like a circlejerk. I mean, every week a new framework pops out that increase performance by 0.0001% and decrease bundle size by 0.005%. And the community is like, *this is the next big thing for web development* , as if corporates who have millions of lines of codebase actually care about the new shiny framework.

[@faisalabdulkadir9439]

Jason you are a true engineer . Thanks for this

[@anasouardini]

You're awesome bro; keep it rolling.

[@DonovanNagel]

Here I am, rebuilding my site with Astro, after rebuilding it with NextJS a month ago, and Gatsby 6 months before that. It's a straight up addiction.

[@nested9301]

thank you i needed to hear this !

[@fkaspow]

We must start rewriting legacy codebases because the cost of maintaining the same will get higher and higher.

[@learnwithjason]

sometimes. other times it’s far more expensive to try and rebuild years of institutional knowledge and edge cases into a new codebase. as always: it depends and there needs to be a really strong case to justify the time and expense and reduction in velocity

[@fkaspow]

I reckon you have dev experience with writing jquery in 2023

[@TheInfamousAlpha]

well said!

[@josemonge4604]

I guess it's all about what the market needs, not really what technology you like the most, unless you work only for yourself then yeah...pick the tech stack that simplifies your life and try to keep up with your clients expectations.

[@soundrightmusic]

An epic slow clap for you sir.

[@rivershertz5967]

Its all about creating the desired app with minimum amount of dev time.
Thats my take from this

[@learnwithjason]

I think you nailed it. find the tools that minimize friction for getting valuable things into users’ hands

[@nachovc]

Amen

[@nachovc]

This comes from someone addicted to trying the next best thing.

[@ryanlog]

jQuery actually is believable because of WordPress

[@david_chuka]

truer words have never been said

[@fkaspow]

You are talking about websites, which is different than building apps.

[@learnwithjason]

eh, kinda. app website is a gradient and I’d argue most apps have a lot more “website” in them than people like to admit
and even if i’m assuming the whole thing is extremely dynamic and appy, it’s still better to build it using something you know and your team can maintain than to chase the latest trendy framework for fractional perf gains

[@fkaspow]

@@learnwithjason Agree, but its hard for newcomers to tech industry to start with something that its not the standard anymore, thats why we should emphasis on moving legacy to modern architectures

[@learnwithjason]

I don’t know that I fully agree. beginners can learn anything (we did!) and a lot of modern stuff has such high API churn that it can grind teams to a halt, especially if they’re less experienced. I’m not necessarily advocating for starting new projects in COBOL or anything, but using something that’s not established enough to have stable APIs or documentation is an enormous risk

[@user-ec6rf7rd2e]

I yelped at 2:55