I won't be the first to say it, but I will say it nonetheless, 2023 was quite the year for JavaScript frameworks. Between new technologies we've be...
For further actions, you may consider blocking this person and/or reporting abuse
Just drop React, it's just bad as a framework. Messy coding
First of all its not a framework. Secondly, sure.
first of all what is the definition of framework. secondly even if they proclaim themselves as library, the way we using react is like framework (and really opinionated one). we put our code on top of react and their non-sense rule, not the other way around
This stands the same for literally all the libraries out there. Wanna use ffmpeg? Oh opinionated. Wanna use sharp? Oh still opinionated.
React is a library and we have been using it as library. Even if you say we put code in react renderer in a specific way and it "renders". Because that's all it does. It doesn't handle server side rendering for you, if you want to do that you gotta build it. Need internal navigation? Too bad. Build it. Wanna use image optimization? Do it manually, yourself.
OR
Pick a framework that does all those things for you under the hood. Like an abstraction. That glues a lot of libraries and abstracts that away from you. Maybe alongside provide a nodejs runtime too so you can access fs for sharp image optimizations and all the runtime specific globals.
Think about your argument again. You are trying to change the definition of a library by the argument that disproves the very existence of said entity.
Please dont do that. Let the bigshots in science department do the defining.
Over and out.
I can't imagine you're making the comparison between React and ffmpeg. I'd say your take on whether it's a framework isn't taking the subject seriously.
ffmpeg has rules around inputs, and doesn't affect how you use other libraries that might handle its output. You can't say the same for React.
You have to jump through hoops to get React to play nice with non-react libraries that have to deal with its output.
I mean... Thats what i said. You stuck to the ffmpeg's part like a bible?
No that's not what you said. And why include ffmpeg if it had no value to the point you were making.
Alright forget about ffmpeg for a sec. Do you agree to the rest?
If you knew the author, You may wrote some better comment... Ofc he know react is not a fully framework...
First of all, it's not a framework. Secondly, no.
Some people like to suffer I guess
Some as in the majority of web developers? Also, what makes React messy but not other frameworks/libs like Svelte or Solid?
React doesn't guarrantee messy code. Lousy dev does. Just ignore them, they don't understand what they are talking about.
Anyway, check out my good work with ReactJS, open with desktop
quanla.github.io/macos-demo
Agreed, but hooks are part of the problem. Svelte and plain JS at least free you of the necessity of having to deal with the one way data flow. It just works. Hooks and the render cycle exacerbate the problem of lousy devs not organizing code.
Hooks is a clumsy patch, no elegance at all
Framework, library, tomato, tomaato… bad is bad. React has served, deserves a thank you. Time to say bye.
React is a decade framework just drop it. Why developers don't drop it because there is easier solutions out there which means less billable hours or putting longer hours in time-sheets
That's ridiculous. Managers would want to hire people that are productive, not just messing around with React flaws. People don't have their priorities straight
Interesting comment. What framework would you point out its the best out there if its not React? ( Honest question dont take it offensive )
I love the nods and acknowledgements of the other frameworks any pointing out how they are good in their own ways. I started dabbling with Solid, and I do like it a lot, I have been dabbling with Qwik and really really love it, thought being new lacks a lot of the libraries that things like react and stuff have because they have been around for years and years. I still generally work in and grab NextJS as my default, but I really hope that changes soon. Their docs IMO have gotten significantly worse, the DX IMO is also a lot more cumbersome with needing to seperate out client/server components, so hopefully soon, I can just say, hey lets build this new project in Qwik/Solid and just be done with it
Astro + HTMX + Alpine / Qwik (Svelte in Astro Island if one day I need to use Island) I liked Qwik very much and I believe that when Alpine feel the weight, probably Qwik will hold. It would be Qwik or Svelte in Astro Island, with a right configuration I believe that even using Svelte, version 5 now with a new toys Runes (very interesting toy) with Astro still can ve better than go with full (Sveltekit), but I have more tests to do, with Qwik instead Alpine, and Svelte 5 in Astro Islands. I want to test AstroDB too, because Astro is awesome and I want to try its limits, HTMX + .NET 8 has a easy integration too for enterprise projects, and I have to be a middle term to middlewares and other thins that I think would be Golang ;) and I want to get start with Rust to be a better prgrammer and understand things better, Rust and F# a different world for me :)
I encourage everyone to give Nuxt a try.
Great post! 👏👏👏
I'm also doing my best to have some impact on better 2024y for developers by releasing state management library - Awai, where all the events are thennable. What are your thoughts about this approach?
I hope there were improvements in SPA as well.
REST API + SPA (SSG) is simple and intuitive, but it seems like the recent direction in web development is moving towards SSR.
Instead of executing fetch requests for initial data through events like onMount when transitioning between pages, how about having a feature that sends these fetch requests in advance when downloading JavaScript for page transitions?
hey , also check out this new amazing CSS framework (created by me* )
NextGenCSS ( github.com/rudransh61/NextGenCSS- )
Pls tell your feedbacks
Thank you for using it for a day (or an hour)
Docs and guide : nextgencss.gitbook.io/
Thanks to all contributors and stars
Nice article!
Do you have al link to "the TC-39 proposal for bringing Signals into the browser". I would be interested to have a look, but a Duckduck search didn't give me anything.
I just read about that yesterday, you can check it: github.com/webcomponents-cg/commun...
Hey, thanks for the link.
Off topic; I didn't realize the cover image was from Tomorrowland (2015) which also contained this speech from the antagonist:
For which type of project do you think its worth using Qwik for ?
Qwik is cool but the adoption rate is slow. Svelte is very easy to learn but I am not sure about version 5 its very different.
Yeah it looks like SolidJS. Which of course I'm not going to complain about.
In all seriousness it addresses a lot of the shortcomings Svelte had. While not everyone felt those I think this is a big step in it becoming a much more capable framework.
ecommerce for sure
In 2024, I predict Vike (the simplest and most modular solution for Vite + SSR) will at least double in
stars: 3k -> 6k
downloads: 40k -> 80k monthly
Damn too many frameworks, would be good to just stick to the big ones and experiment with the new cool ones, then bring the good stuff into the existing frameworks