5 Dev Trends to Follow in 2024

Looking at possible dev trends in 2024.
💬 Topics:
- WASM as a JS replacement ;
- Rust & Leptos;
- Meta Frameworks;
- AI Impact on the dev world;
- Backend as a Service solutions;
- Edge deployments with Deno and Turso;
- Efficient web with Solid and Qwik.
📖 Blog Article - www.awesome.club/blog/2024/5-...
Patreon - / awesomeclub

[@rodjenihm]

The best advice for 2024 is: "Learn to ignore the noise"

[@MikeNugget]

and be an ostrich - learn to stick your head in the sand 😂

[@awesome-coding]

Fair enough :)) It's pretty hard to figure out what's noise and what isn't though 😅

[@ayoubkrt5018]

@@awesome-coding im personally very interested in stuff thats even noise cause its always cool to see something new that the other players didnt think about, u could ignore it and keep using the old reliable stuff but this could very well be the same case in the medical feild, after becoming a doctor you never stop keeping up with new discoveries and tools that change the way you would "doctor" stuff

[@awesome-coding]

@@ayoubkrt5018 I agree! That's my take on it as well - you should always be up to date with the industry trends (even though you might not agree with some of them).

[@ayoubkrt5018]

@@awesome-coding YES! even if you agree with them you can share you insight on such topics, that what I live about web technologies, it's also a cure to my imposter syndrome when I'm able to engage in topics with ppl who are far more advanced than me in the web development industry and it's never bad to not know something cause you can learn it by reading

[@ayoubkrt5018]

qwik 2.0 possibily coming in 2024, there's even a video by misko talking about it, thats a big thing i want to follow, as well as how other frameworks could implement something similar to qwik in them, svelte already did with runes and how they are similar to qwik's $

[@bear458ziif-s]

appreciate the rust/wasm fullstack mention. i could see it becoming the future elm when it gets more stable. most likely bigger than elm because wasm is supported in the browser and rust has a much larger community with more use cases. web specific languages outside of javascript and typescript don't have a future anymore.

[@justahumanwithamask4089]

I might just learn qwik since I'm learning react atm, some carry over with jsx plus the other frameworks change stuff so often that you might be learning a new framework entirely when a new version is out.

[@awesome-coding]

It's a pretty smooth transition from React to Qwik. There are just a handful of concepts you need to understand to start with Qwik (Resumability, QRLs, JS Streaming).

[@mateusbraga1960]

Appreciate!

[@EmmanuelLambertCanada]

Also to be noted: 5 eyes NSA are moving everything to Rust.

[@awesome-coding]

Didn't know that 😂 Funny and SUSPICIOUS at the same time

[@bullet3349]

SolidJS is slowly getting market share. I guess it's popularity would explode this year or next year as a replacement for React/NextJS. WebAssembly is interesting but it's probably a niche use-case.

[@azulamazigh2789]

naah Solid Start is not even production ready yet

[@ulrich-tonmoy]

i guess we should limit the js uses and use wasm and only use js only for UX as needed

[@MaxSvid]

HTMX mentioned bois

[@awesome-coding]

riding that hype train

[@MuStevenPlay]

You forgot to mention Bun, as they want it to be the new JS runtime, finally replacing Node 👌

[@awesome-coding]

You are right. I'm not sure if they'll be able to move the needle though

[@TechBuddy_]

Hmmm IDK man!! we'll see what happens Nice video tho

[@awesome-coding]

We shall see. Thank you!

[@kernellpanic]

HTMX feels like the return of Java Server Faces.

[@awesome-coding]

😂😂 just terrible.. I have a lot of bad memories related to JSF and Prime Faces in particular...

[@kernellpanic]

@@awesome-coding I know... it was like blackbox server faces

[@fryc.dominik]

I'm personally now on the web components hype train 🚂

[@awesome-coding]

Interesting. How come?

[@fryc.dominik]

@@awesome-coding I've been working on my diploma thesis focused on web components, and I've discovered the power of it. It's fantastic to work with Lit; the whole web components ecosystem has significantly improved in the past few years.

[@krokenstiv8777]

It looks like all the languages will eventually merge into one language.

[@awesome-coding]

Yes -> JavaScript ✌️

[@truth-12345.]

This is more just to influence beginners. Most companies require you to actually be skilled in problem solving and most of them require you to do it in C++.

[@awesome-coding]

Most of them require you to do it in JavaScript / TypeScript, Python, Java or C#. C++ is used in predominant in some industries for certain, but it's far from being the go to language for development.

[@truth-12345.]

@@awesome-coding In my country if it's not web development, writing code in C++ is really a high requirement.

[@artieschmidt3039]

​@@truth-12345.where are you from?

[@awesome-coding]

@@truth-12345. Fair enough - it might be because your country's IT sector is focused on a specific industry?

[@truth-12345.]

@@awesome-coding A lot of them are focused in embedded and platforms that maybe built with C++.

[@ivanmaglica264]

WASM is not replacement for JS, it's a compile target. Nobody will program in WASM.

[@awesome-coding]

Right - this is why I mentioned Rust and Leptos :D

[@Luxalpa]

I guess JS is also a compile target for Typescript though

[@QueeeeenZ]

I always find it funny that people think Solid invented signals when signals have been part of Vue since the beginning.

[@awesome-coding]

Were they in Vue 1.0 - I can't honestly remember. I know Knockout is acknowledged as the first framework to bring Signals into the web dev space. However, I feel like Solid did a way better job to integrate them in a seamless manner in a DX we were already familiar with.

[@crab-cake]

vue didn't have *fine-grained* reactivity like solid until vue 3 with ref(). they were inspired by solid's reactivity model. there is a massive difference.

[@QueeeeenZ]

@@crab-cake but Solid came after Vue 3

[@crab-cake]

@@QueeeeenZ no it did not. vue 3 came out in 2020. solid has been around since 2018. solid officially released in 2021 but it was around before that. knockout had signals in 2010 before all of the frameworks.

[@ReedoTV]

Ask AI to make a good JS framework and it will never bother you again

[@awesome-coding]

fact.

[@medilies]

Never follow trends

[@awesome-coding]

Don't follow them but still keep an eye out for what's happening in the industry. React was a "new trend" at some point. Svelte was a "trend". Go was a "trend". Rust is a "trend".

[@MikeNugget]

Why is this diction so difficult to perceive by ear? 😢

[@awesome-coding]

That's my Eastern European accent - sorry about it :))

[@TechBuddy_]

@@awesome-coding whyy sorry ??

[@andrewforrester6713]

Took me about 1.25 videos to get used to an accent I don't hear very often. Now I find it almost melodic and I love it

[@awesome-coding]

@@TechBuddy_ Well I'm trying to improve the quality of the sound. I know it must be frustrating for some of you guys when things are difficult to understand

[@awesome-coding]

@@andrewforrester6713 Thank you!

[@o_glethorpe]

"Things are going back to the server" really? Now more than ever users have the most powerful devices, faster internet etc..., if wasn't vercel "simplifying" the development for devs, this would not be a thing, this is all build upon laziness of developers.

[@sadunozer2241]

Servers do have authority built in… but I don’t understand the lack of gpu trends for web. Native gpu performance is 1 context away…

[@o_glethorpe]

Its all very simple, if it is a requirement (security for instance), then it should go on the server, if it can be done on the client, it should be done on the client, why pay for servers if you can ship and host for free on the client? People who advocate something like vercel probably doest not pays the bills @@sadunozer2241

[@mouhamedbourouba3637]

You don't get it, yes users have powerful devices, but the only point you can fully control is the server, for example: lets say you need to format user input, should you do it in the server or the client, doing it on the server ensures that every input is formated because you have full control on your service unlike your clients.

[@ayoubkrt5018]

i mean you can try it yourself, build a large app with lots of javascript code, events and such and make it fully client side rendered and see the result, look how much frameworks like qwik can shave off performance problems by completely taking away the hydration process from the client side, but what you're saying is to double down on a solution even worst than hydration?

[@mma93067]

The data is always on the backend anyway. So client devices don’t matter as much. If you’re doing intensive calculations that doesn’t involve a local sandbox (which is most of the web).. going server-first makes logical sense. Besides dev laziness can also be framed as efficiency for the product

[@notu483]

Is this supposed to be a FireShip ripoff?

[@awesome-coding]

Hey! Out of curiosity - what do you think is a ripoff in this video?

[@JBuchmann]

Influenced, yes. Rip off, no

[@awesome-coding]

​@@JBuchmann Yep - Fireship's video editing style is a big influence for me (especially since you have little good options with faceless YT channels). However, I believe that calling my videos rip offs is a bit too much, but I might be missing something. This is why I'm genuinely curious to understand the reasoning behind such comments.

[@kjbhappy123]

Before I even clicked the video, I thought this was a fireship clone. Just the thumbnail alone told me that. The opening style of the video was also exactly the same as fireship. Open with some joke about AI or current world affairs. The video reads as though you saw fireships video and copied everything but then changed the topics. Structure and style are still a part of plagiarism. If you're really trying to stand out you're going to have to find your unique style that doesn't mimic other popular users in the space.

[@andyengle]

This video lost me in the first 7 seconds.

[@NewTypeStarling]

Why?

[@awesome-coding]

I need to work on my jokes then :))