Home Business Analyst BA Agile Coach My Bleeding Edge Tech Stack for 2025

My Bleeding Edge Tech Stack for 2025

46
41

If you’re building a web or mobile app in 2022 there’s literally a million different ways to get the job done by combining different front-end and back-end libraries along with APIs tooling and infrastructure to form a complete tech stack in today’s video i want to give you a guided tour of my

Tech stack which i plan on using through 2025 assuming the world hasn’t been destroyed by that point not only will i explain my thought process when making these decisions but we’ll also look at a ton of alternatives that you may want to consider for yourself because you definitely shouldn’t just copy some

Random guy on youtube before we get into it as many of you know i recently had a baby i haven’t been uploading quite as many videos but it’s given me time to work on a complete rebuild of fireship io and in the process i’ve analyzed all kinds of different technologies that i

Might want to use for that project now i don’t really need to rebuild fireship but i do it every couple years just because i enjoy the process most of the coding i’ll do with my bare hands but the project will be open source and i will likely collaborate with a couple of

Other engineers to round out the project it’s a small team effort which is an important consideration when choosing your tech stack because many technologies are more well-suited for large teams software engineers love to flex that tech stack gotta be bustin or drippin in other words ridiculously over-engineered the reality is that i

Could build fireship as a wordpress blog add a membership plugin and scale it up to millions of users if i want to make money that would be the smart thing to do but i want to build something a little more special than just a wordpress blog in the next version of

The site courses will have progress tracking that will also include challenges like quizzes and interactive demos powered by stack blitz in my experience the majority of modern web development happens on the front end that being said one of the most important decisions to make is your

Front-end ui library and for that i have chosen svelt i’ve built something with pretty much every ui library on the market they all have their pros and cons but svelte is the one that feels most productive to me and coincidentally just yesterday it debuted at the top of the

Most loved web frameworks on the stack overflow 2022 survey i think developers love it for how natural it makes reactive data feel when a mutable variable changes the ui reacts you don’t have to jump through any weird hoops to make things reactive now the other thing

I really like about spelt is the way you share data across components which is done with stores a store is like a subject in rxjs that can be observed anywhere in the application by simply putting a dollar sign in front of it this pattern is actually very similar to

The way things are done in angular but svelte does it with a lot less boilerplate the current version of fireship is actually built with angular and in my opinion angular is awesome and the most underappreciated framework out there it’s extremely popular in enterprise for a good reason but in 2022

React is definitely still the most popular ui library and it has a huge ecosystem of supporting libraries i think that’s the most compelling argument to use it when it comes down to the ui library itself there are cleaner options out there like solid js that would also provide better performance i

Also seriously considered vue which is not only a great framework but also has a large number of supporting libraries as well but the more important decision is which meta framework do you want to use react has next view as next angular has universal and svelt has kit most

Applications out there need some form of server-side rendering to make their sites visible to search engines and bots spelt kit is the official ssr solution that’s being worked on by rich harris but as of today it’s still in beta using a framework that’s not at a stable

Release is kind of risky you could pour a ton of work into an app then the framework developers decide to pull a feature on the final release that torpedoes your entire business not very likely so that’s a risk i’m willing to take now there are other ways to server

Render spelt another good option is astro it has a lot of awesome features for content driven sites but the reason i prefer spelt kit for this project is because it does client-side routing after the initial page load which becomes important on more interactive sites especially when user authentication is involved but my plan

Is to use astro for my personal portfolio if i ever get around to rebuilding it now the other framework that i would say is my second choice is next js next is already a great framework but it has a bunch of cool stuff coming as well like nested routing

And stuff like that i also recently made a video on next yet another awesome framework that i hope to make a full course on in the future it’s also worth mentioning that there’s a new framework called quick that has an entirely different take on rendering with resumable or replayable applications but

Even that’s a little too bleeding edge for me now when it comes to server rendering you don’t need to use a meta framework that’s tied to some javascript library instead you can use a full stack framework like ruby on rails laravel django or whatever to render all of your

Content on the server these frameworks have advantages for certain types of applications but in my case full-blown server-side rendering is not really necessary because the content on the actual site doesn’t change all that often it’s far more simple to pre-render the entire site upload it to a storage

Bucket and then cache it on a cdn around the world when you have a dedicated server you then need to think about how to scale it with either Serverless functions or if you want a really complicated tech stack something like Kubernetes the next thing i want to talk

About is typescript if you’re building a big complicated project you should use it in the end a more complicated question you’ll have to ask is how am i going to manage my css when i work on a solo project i spend more time around with the css than i do writing

Javascript it’s depressing man i’ve only got so much time left to hold fortran 3. life goes by much faster than we think yet here i am wasting hours of this precious time trying to figure out why this navbar won’t be sticky that being said a tool that makes css much easier

Is tailwind most importantly it makes prototyping and the implementation of your designs go much faster i like to have a lot of control over my designs because for me it’s a creative process tailwind won’t magically make your website look good but it does provide enough of a framework to get things done

Way quicker the current version of fireship is 100 custom with sas with tailwind i feel like i have the same amount of control but things just get done much more rapidly and another huge benefit is that it will automatically purge styles to keep the css bundle as small as possible that’s important

Because the initial page load speed for my site is critical if you like the utility class approach another option to check out is windy css or if you don’t care about having that much control you can use something like bootstrap in addition to many other css frameworks

Out there and you’ve also got tons of framework-specific ui libraries to analyze as well and if you’re using tailwind you should definitely check out daisy ui but i’m just doing everything from scratch myself because i’m an idiot that’s enough for the front end now i

Want to talk about the back end as you know i’m a big fan of firebase and it’s been the foundation of this channel from day one but as i’ve grown older and wiser i’ve come to realize something about firebase this may be shocking to some of you but firebase is still

Awesome and i plan on using it until the day i die or at least until google decides to kill it whichever comes first firebase will do 90 of what most apps need on the back end the main drawback is that you’re tightly locked into google cloud platform and you may run

Into edge cases that it just doesn’t support like advanced authentication features or complex database queries and that can be a deal breaker for certain types of apps what you could do is architect your entire backend from scratch by picking and choosing different services in the cloud but then

The complexity of your code base is going to explode luckily in 2022 there are quite a few alternatives to firebase you’ve got big ones like AWS amplify and mongodb realm and then smaller startups like enho superbase and app right i recently compared all of them and each

One has its own set of unique trade-offs expect a full video on that soon the most important thing is the database firebase uses firestore which is a document database similar to mongodb which can get the job done for most apps but does have some limitations that can

Be kind of annoying at times a traditional sql database is probably the safest bet for most people but they’re generally harder to work with although there are some services out there like planet scale and cockroachdb that have made things a lot easier in recent years especially when used with an orm like

Prisma in addition you might consider other nosql databases like redis and cassandra which can actually be used as a primary app database now in addition to the back end there are a lot of other smaller tools in the stack when it comes to testing i find that i need to keep

Things very simple otherwise i’m not going to test anything at all and my preferred way to do that is with cyprus which is basically an all-in-one package that can do everything from end-to-end tests to individual unit tests and everything in between if you’re not into cyprus another good option for

End-to-end testing as playwright and if you just want to do unit tests another framework i’ve really been wanting to try out is v-test which is based on vee the build tool that powers spelt kit my tech stack also uses a variety of apis to do things that i can’t do on my own

One of which is send transactional email i currently use sendgrid and will continue doing so in the future but i wish firebase or google cloud would come out with its own email service in addition a content driven site needs to have really good full text search to handle that i’m using algolia algolia

Can get pretty expensive on very large sites but for me it’s pretty inexpensive and very easy to use this is yet another feature i wish would be implemented into firebase but i’m not going to hold my breath and finally i’ll be using stripe and paypal to manage payments because to

Be honest i haven’t looked at any alternatives in a long time the end result is a pretty simple tech stack with the main components being spelt kit and firebase the only major problem is that it doesn’t form an obvious acronym we could go with the fist stack or maybe

Fire kit or perhaps it but i don’t know man let me know if you have a better idea thanks for watching and i will see you in the next one
Choosing a modern tech stack is difficult because of the sheer number of tools available. Let’s look at 8 important decisions you’ll need to make when building a web or mobile app today

#learntocode #programming #tech

Resources

Svelte Kit
Firebase
Stack overflow survey
Tech Stacks Explained
Svelte in 100 Seconds

Get More Content – Upgrade to PRO

Upgrade to Fireship PRO at
Use code lORhwXd2 for 25% off your first payment.

My Editor Settings

– Atom One Dark
– vscode-icons
– Fira Code Font

Topics Covered

– Best tools to build web apps
– What is a Tech Stack
– 2022 Developer roadmap
– Web framework comparison
– Top Web Technologies
00:00 if you’re building a web or mobile app
00:01 in 2022 there’s literally a million
00:03 different ways to get the job done by
00:05 combining different front-end and
00:06 back-end libraries along with apis
00:08 tooling and infrastructure to form a
00:10 complete tech stack in today’s video i
00:12 want to give you a guided tour of my
00:14 tech stack which i plan on using through
00:16 2025 assuming the world hasn’t been
00:17 destroyed by that point not only will i
00:19 explain my thought process when making
00:20 these decisions but we’ll also look at a
00:22 ton of alternatives that you may want to
00:24 consider for yourself because you
00:25 definitely shouldn’t just copy some
00:27 random guy on youtube before we get into
00:28 it as many of you know i recently had a
00:30 baby i haven’t been uploading quite as
00:32 many videos but it’s given me time to
00:33 work on a complete rebuild of fireship
00:35 io and in the process i’ve analyzed all
00:37 kinds of different technologies that i
00:39 might want to use for that project now i
00:41 don’t really need to rebuild fireship
00:43 but i do it every couple years just
00:44 because i enjoy the process most of the
00:46 coding i’ll do with my bare hands but
00:48 the project will be open source and i
00:49 will likely collaborate with a couple of
00:51 other engineers to round out the project
00:53 it’s a small team effort which is an
00:54 important consideration when choosing
00:56 your tech stack because many
00:57 technologies are more well-suited for
00:59 large teams software engineers love to
01:01 flex that tech stack gotta be bustin or
01:03 drippin in other words ridiculously
01:05 over-engineered the reality is that i
01:06 could build fireship as a wordpress blog
01:08 add a membership plugin and scale it up
01:11 to millions of users if i want to make
01:12 money that would be the smart thing to
01:14 do but i want to build something a
01:15 little more special than just a
01:16 wordpress blog in the next version of
01:18 the site courses will have progress
01:20 tracking that will also include
01:21 challenges like quizzes and interactive
01:23 demos powered by stack blitz in my
01:25 experience the majority of modern web
01:27 development happens on the front end
01:28 that being said one of the most
01:30 important decisions to make is your
01:31 front-end ui library and for that i have
01:33 chosen svelt i’ve built something with
01:35 pretty much every ui library on the
01:37 market they all have their pros and cons
01:39 but svelte is the one that feels most
01:40 productive to me and coincidentally just
01:42 yesterday it debuted at the top of the
01:44 most loved web frameworks on the stack
01:46 overflow 2022 survey i think developers
01:48 love it for how natural it makes
01:50 reactive data feel when a mutable
01:51 variable changes the ui reacts you don’t
01:54 have to jump through any weird hoops to
01:55 make things reactive now the other thing
01:57 i really like about spelt is the way you
01:58 share data across components which is
02:00 done with stores a store is like a
02:02 subject in rxjs that can be observed
02:04 anywhere in the application by simply
02:06 putting a dollar sign in front of it
02:07 this pattern is actually very similar to
02:09 the way things are done in angular but
02:11 svelte does it with a lot less
02:12 boilerplate the current version of
02:13 fireship is actually built with angular
02:15 and in my opinion angular is awesome and
02:17 the most underappreciated framework out
02:19 there it’s extremely popular in
02:20 enterprise for a good reason but in 2022
02:23 react is definitely still the most
02:25 popular ui library and it has a huge
02:27 ecosystem of supporting libraries i
02:29 think that’s the most compelling
02:30 argument to use it when it comes down to
02:31 the ui library itself there are cleaner
02:33 options out there like solid js that
02:35 would also provide better performance i
02:37 also seriously considered vue which is
02:39 not only a great framework but also has
02:41 a large number of supporting libraries
02:42 as well but the more important decision
02:44 is which meta framework do you want to
02:46 use react has next view as next angular
02:48 has universal and svelt has kit most
02:51 applications out there need some form of
02:52 server-side rendering to make their
02:54 sites visible to search engines and bots
02:56 spelt kit is the official ssr solution
02:58 that’s being worked on by rich harris
03:00 but as of today it’s still in beta using
03:02 a framework that’s not at a stable
03:04 release is kind of risky you could pour
03:05 a ton of work into an app then the
03:07 framework developers decide to pull a
03:08 feature on the final release that
03:10 torpedoes your entire business not very
03:12 likely so that’s a risk i’m willing to
03:13 take now there are other ways to server
03:15 render spelt another good option is
03:17 astro it has a lot of awesome features
03:19 for content driven sites but the reason
03:21 i prefer spelt kit for this project is
03:23 because it does client-side routing
03:24 after the initial page load which
03:26 becomes important on more interactive
03:28 sites especially when user
03:29 authentication is involved but my plan
03:31 is to use astro for my personal
03:32 portfolio if i ever get around to
03:34 rebuilding it now the other framework
03:35 that i would say is my second choice is
03:37 next js next is already a great
03:39 framework but it has a bunch of cool
03:40 stuff coming as well like nested routing
03:42 and stuff like that i also recently made
03:44 a video on next yet another awesome
03:46 framework that i hope to make a full
03:47 course on in the future it’s also worth
03:49 mentioning that there’s a new framework
03:50 called quick that has an entirely
03:52 different take on rendering with
03:53 resumable or replayable applications but
03:55 even that’s a little too bleeding edge
03:57 for me now when it comes to server
03:58 rendering you don’t need to use a meta
04:00 framework that’s tied to some javascript
04:02 library instead you can use a full stack
04:04 framework like ruby on rails laravel
04:06 django or whatever to render all of your
04:08 content on the server these frameworks
04:10 have advantages for certain types of
04:12 applications but in my case full-blown
04:14 server-side rendering is not really
04:15 necessary because the content on the
04:17 actual site doesn’t change all that
04:18 often it’s far more simple to pre-render
04:20 the entire site upload it to a storage
04:22 bucket and then cache it on a cdn around
04:24 the world when you have a dedicated
04:26 server you then need to think about how
04:27 to scale it with either serverless
04:29 functions or if you want a really
04:30 complicated tech stack something like
04:32 kubernetes the next thing i want to talk
04:33 about is typescript if you’re building a
04:35 big complicated project you should use
04:37 it in the end a more complicated
04:39 question you’ll have to ask is how am i
04:40 going to manage my css when i work on a
04:43 solo project i spend more time
04:45 around with the css than i do writing
04:46 javascript it’s depressing man i’ve only
04:48 got so much time left to hold fortran 3.
04:51 life goes by much faster than we think
04:53 yet here i am wasting hours of this
04:54 precious time trying to figure out why
04:56 this navbar won’t be sticky that being
04:58 said a tool that makes css much easier
05:00 is tailwind most importantly it makes
05:02 prototyping and the implementation of
05:04 your designs go much faster i like to
05:06 have a lot of control over my designs
05:08 because for me it’s a creative process
05:10 tailwind won’t magically make your
05:11 website look good but it does provide
05:13 enough of a framework to get things done
05:15 way quicker the current version of
05:16 fireship is 100 custom with sas with
05:19 tailwind i feel like i have the same
05:20 amount of control but things just get
05:22 done much more rapidly and another huge
05:24 benefit is that it will automatically
05:25 purge styles to keep the css bundle as
05:28 small as possible that’s important
05:30 because the initial page load speed for
05:31 my site is critical if you like the
05:33 utility class approach another option to
05:35 check out is windy css or if you don’t
05:37 care about having that much control you
05:39 can use something like bootstrap in
05:40 addition to many other css frameworks
05:42 out there and you’ve also got tons of
05:44 framework-specific ui libraries to
05:46 analyze as well and if you’re using
05:47 tailwind you should definitely check out
05:49 daisy ui but i’m just doing everything
05:51 from scratch myself because i’m an idiot
05:53 that’s enough for the front end now i
05:55 want to talk about the back end as you
05:56 know i’m a big fan of firebase and it’s
05:58 been the foundation of this channel from
06:00 day one but as i’ve grown older and
06:02 wiser i’ve come to realize something
06:03 about firebase this may be shocking to
06:05 some of you but firebase is still
06:07 awesome and i plan on using it until the
06:09 day i die or at least until google
06:11 decides to kill it whichever comes first
06:12 firebase will do 90 of what most apps
06:15 need on the back end the main drawback
06:17 is that you’re tightly locked into
06:18 google cloud platform and you may run
06:20 into edge cases that it just doesn’t
06:22 support like advanced authentication
06:24 features or complex database queries and
06:26 that can be a deal breaker for certain
06:28 types of apps what you could do is
06:29 architect your entire backend from
06:31 scratch by picking and choosing
06:32 different services in the cloud but then
06:34 the complexity of your code base is
06:35 going to explode luckily in 2022 there
06:38 are quite a few alternatives to firebase
06:40 you’ve got big ones like aws amplify and
06:43 mongodb realm and then smaller startups
06:45 like enho superbase and app right i
06:47 recently compared all of them and each
06:49 one has its own set of unique trade-offs
06:51 expect a full video on that soon the
06:52 most important thing is the database
06:54 firebase uses firestore which is a
06:56 document database similar to mongodb
06:58 which can get the job done for most apps
07:00 but does have some limitations that can
07:02 be kind of annoying at times a
07:03 traditional sql database is probably the
07:05 safest bet for most people but they’re
07:07 generally harder to work with although
07:08 there are some services out there like
07:10 planet scale and cockroachdb that have
07:12 made things a lot easier in recent years
07:14 especially when used with an orm like
07:16 prisma in addition you might consider
07:18 other nosql databases like redis and
07:20 cassandra which can actually be used as
07:22 a primary app database now in addition
07:24 to the back end there are a lot of other
07:25 smaller tools in the stack when it comes
07:27 to testing i find that i need to keep
07:29 things very simple otherwise i’m not
07:30 going to test anything at all and my
07:32 preferred way to do that is with cyprus
07:34 which is basically an all-in-one package
07:36 that can do everything from end-to-end
07:37 tests to individual unit tests and
07:39 everything in between if you’re not into
07:41 cyprus another good option for
07:42 end-to-end testing as playwright and if
07:44 you just want to do unit tests another
07:46 framework i’ve really been wanting to
07:47 try out is v-test which is based on vee
07:49 the build tool that powers spelt kit my
07:51 tech stack also uses a variety of apis
07:54 to do things that i can’t do on my own
07:56 one of which is send transactional email
07:58 i currently use sendgrid and will
07:59 continue doing so in the future but i
08:01 wish firebase or google cloud would come
08:03 out with its own email service in
08:04 addition a content driven site needs to
08:06 have really good full text search to
08:08 handle that i’m using algolia algolia
08:10 can get pretty expensive on very large
08:12 sites but for me it’s pretty inexpensive
08:14 and very easy to use this is yet another
08:16 feature i wish would be implemented into
08:17 firebase but i’m not going to hold my
08:19 breath and finally i’ll be using stripe
08:21 and paypal to manage payments because to
08:23 be honest i haven’t looked at any
08:24 alternatives in a long time the end
08:26 result is a pretty simple tech stack
08:28 with the main components being spelt kit
08:29 and firebase the only major problem is
08:31 that it doesn’t form an obvious acronym
08:33 we could go with the fist stack or maybe
08:35 fire kit or perhaps it but i don’t
08:38 know man let me know if you have a
08:39 better idea thanks for watching and i
08:41 will see you in the next one

YouTubeTechStack

41 COMMENTS

  1. WordPress only ACF plugin and GETUIKIT framework, vanilla js & php, done. The problem is we jump through 500 hoops to serve html. Just write html templates upload with sftp.

  2. In regard to Stripe: how do you handle tax collection and remittance? Not a shill, but I'm leaning toward using Paddle so I don't have to worry about any of that. Coming from being a successful iOS indie dev where the App Store takes care of those issues which is NICEEE

  3. I hate programming now because it's no longer about being smart , it's about being a nerd woth no life, there's no algorithmic thinking anymore it's about knowing the pop culture of millions of frameworks, i'm only a web developer to get out of the 3rd world , when that happens, i will stay away from this field and have a life !!!

  4. As someone who is learning to code and currently working on small projects HTML CSS JS , that CSS part is so relatable like I spent 3 or 4 hours working on sth the majority of that time I spend dealing with CSS

LEAVE A REPLY

Please enter your comment!
Please enter your name here