@EduardKaresli
Programming is a trap.. you become a slave to the tools. The tools change constantly, you can barely catch up, and when some of the tools (libraries, languages) become obsolete then you're screwed and you have to move on and learn another set of tools. IMHO, programming is rewarding only if you're doing it for your own personal projects not as part of a corporate structure. 🤷
@konstantin-bifert
I honestly care only about a few things: - no corporate BS pulling ropes, I don't like rug-pulls - no v-DOM because having wrappers etc is just a PITA - possible to run without a build step (because this is where legacy comes from) - no need to update the thing every X weeks because of some reinvent-the-wheel random decisions - no bizillion abstraction with lackluster documentation Hence I think that using Fresh by Deno (Preact behind the curtain) sounds like the most healthy way of dealing with all of this mess while caring about Web Standards. Hopefully Vue3 with Vapor gonna remove the need for the v-DOM too. The rest don't really check any interesting box to me. Qwik sounds nice. I see the appeal for Solid too. While Astro is dope as usual.
@emaayan
as a java developer front end framework make me think frontenders lost a few screws from the amount of subframework one needs to build a single hello world.
@AliceFlorence-k7j
This JS frameworks discussion is incredibly insightful and timely for 2025!
@karlisgertmanis
been using angular at large enterprise for years. works fine. we cannot jump around and switch frameworks based on trends so we need something with structure to ensure all teams have at least minimal alignment. latest&greatest not worth it.
@ankur67678
I have been using solid for few projects... And it made wonders... Now trying solidstart and it has been ok so far .. but now I think it just doesn't matter which framework you choose as long as you are aware of the nuances it provides... Still I hope that the solid ecosystem flourish...
@danny3man
That was a very long and informative add to Scrimba. Well done !
@ashleyfreebush
I really like scrimba! its nice to see them here <3
@im_chris_ai
Clear and well-made video. Bravo! 🎉
@tesla1772
Have you tries phoenix with elixir?
@zlendy_
8:44 "Frameork" fluent, oops!
@ismailhossain964
Do we really need a js framework for large applications?
@sergeyd2199
Angular is far better than anything else, but it comes with a price of mastering architecture, proper decomposition and state management.
@px-d.2k
Nice Video, one question; how do you create those code snippets like in 4:00? Those VScode minimap like style?
@browaruspierogus2182
Just silently wait until new cybersecurity teams say that all those JS based reactive junkyard is no longer safe and webassembly is preferred
@haaxor1689
Anyone saying that React RSCs are more complex than the old SSR models doesn't understand them yet. Switching to RSCs using NextJs app router made everything in the stack so much easier. Instead of using 5 libraries for managing different complex steps of getting and syncing data between FE and BE, you can now write it all yourself using very few primitives. And I've used app router with RSCs in basically all of it's "versions" (and yes it's still very much changing and evolving) and it just keeps getting simpler with every major update (such as the "use cache" with PPR and dynamicIO).
@parthdeshwal4419
i thought it was a fireship video
@gold-junge91
So you are saying no one use nextjs??
@patricknelson
7:00 Thankfully, Svelte 4 to 5 had relatively few breaking changes that weren’t backward compatible. For example, you don’t have to use the $effect rune, you can stick with v4 syntax if you want. The backward incompatible changes that did occur of course make sense, considering it’s a major version. If you’re doing things under the hood like I was with my library, there might be some minor differences. Like, how you and instantiate a component is a little different. Everything is pretty well documented though, so transition should hopefully be pretty smooth!
@kushagrashuklaietlucknowst5642