Code is fun. Code is not work, it's a game. A game of exploration, of logic, of construction. And I love to share that joy of creating something out of thin air and electrons. Be it a website, a React JS or Next JS application, or a mobile native app using Solar 2D or Flutter or React Native. This channel is all about a journey, the journey to becoming a wizard, of bringing ideas to life using only our keyboards and our imaginations.
I definitely agree on your POV regarding use-cases. I left big companies and ESNs a while ago and technically I also shifted from Angular to React. Most startups and small companies use React. I find much more freedom in the React ecosystem. I also find that React is the go-to framework for frontend development newbies. It has lots of good packages and tools you can use. I'm now keeping an eye on the more recent frameworks, such as Vue, SolidJs, Svelte, etc. which bring lots of new features and paradigms to the table. So far, Angular and React try to keep up on the pace by borrowing new concepts from them. Signals are part of this run. We'll see if signals are a game changer, but their adoption plan by ecmascript might make it generic in all frameworks 😁 My two cents would be to stay strong on the basics of frontend development and stay open to any framework.
Well based on salary thing. There is no question that Go makes permormant apps faster to market than Rust. Business more like in the general application realm need this time to market thing. So go is perfecly better than Rust. Rust on the other hand is focused in system programming. Yet there is competition for Rust like Zig, C++ etc in some cases Go. So Rust has big competion on where its focus is.
@@KodapsAcademy Sure it does. It has an extensive FFI to interop with C. I've personally written Rust code that calls into C and C code that calls into Rust.
@@guitargyro I get your point. The difference is that FFIs function on a binary to binary level, whereas Zig's interop is at the code level. But I guess your point still holds :)
I am using Python for my scripting uses. And if I need a GUI program, I will create it in python with ctypes module. Ctypes will help me to call the windows api functions and I can easily make my gui. So this is my use case. Can I move to Lua for this purpose ? Is Lua able to do the same ? EDIT: Please don't mention LuaJit.
So now you use both react and htmx? Isn't that a very unnecessary bloat you claimed to try to avoid? I seriously don't understand your problem with updating these three unconected components when adding something to cart. React is 100% perfectly suited for this job. Just learn how to use context API in instead of throwing in another technology. Seriously react is like the #1 solution for stuff like this and you gave that as a reason to lean for another technology..
No you've misunderstood what I was saying. We don't use React on the page (we use it elsewhere, in the customer area), only HTMX. The rest of the page is rendered statically using PHP / Twig, not React. And React can't encompass those components that don't share a (HTML) parent unless we go via useRef. which would end up being an unnecessary complication. In any case, React was most certainly not the right tool for this use case. I get your point that it would have been in a NextJS context, but it isn't here.
SolidJs can solve so many React/NextJs problems like re-rendering hell, much better DX for fast dev speed, built-in Context for client side states, and built-in server side state management. Very similar syntax to React so I can easily convert React repo into SolidJs repo! I AM SOLD
Most JavaScript coders are like "WordPress coders" -- they don't know how to code anything themselves. All they do is import hundreds of third-party libraries. When I ask, "show me YOUR CODE," all they can show are some simple loops. When I ask, "how would you code an authentication system?" almost all these JavaScript "pro coders" respond, "I would use Clerk." I deny them on the spot. It's the end of the interview. Mindless library users. Nothing more.
Not a web dev, I'm trying to learn a web framework and the way references are handled here go against every fiber of my bone. I prefere to keep my refs scoped and their execution order preserved. It should be 1, 2, 3 not 3, 2, 1. Why would anyone think this is the simplier approach? Also why is an example an impure function? Scope seems way out of place here.
Loved the quality of the video. I didn't learn any of those fancy JS libraries/frameworks yet (except jQuery, lmao). And honestly i am left with more questions than answers. It's a gamble somewhat at least. I consider myself a fresh freelancer and i was thinking about creating my own website and at the same time learn something new alongside that process. I wouldn't generally say this, but in the case of tech stuff i would definitely trust Google more than FB/Meta, even if React is more popular. Even if i am not gonna make banking websites, i think it's better long term to start off with Angular and it's stricter rules and then transition over to learn React. This way i hope i would write less spaghetti :D Anyway, thank you! Writing this comment also somewhat sorted my thoughts, which wasn't really intended. :D
React is somewhat of a mess recently, with it's own documentation pointing you towards full-application-frameworks like nextja and having had no stable release for almost 2 full years from 2022 to 2024. Meanwhile nextjs was using unstable versions of react and introduced massive bugs into their own "stable" releases. How the hell did it become like this? Compare that to Angular. That moves with Lightspeed und will be su much better a year from now with signal-based-components and "zoneless". State of JS does not really represent the market all that well. As you said Angular devs are usually in pretty stable environments and teams and mostly dont participate with other frameworks (or "state of js"). The best indication are job trends imo, which puts React comfortably in front in most regions, though Angular is slightly ahead in Europe.
As amusing as this romanced opinion of both frameworks may be, the fact of the matter is that React does better with simpler applications, where as Angular thrives in enterprise level complexity. If you are dealing with huge complex legacy riddled applications or application suites, Angular keeps its shit together because it offers the structure to do so. You can create your own structure in React as well, but that comes at a cost of time (which equals money, in the real world).
I think the real benefit is that other frameworks will adopt nitro, vinxi, and vite. Hopefully, this will result in a wide ecosystem, so each block will get more users, which means better software for every meta framework, not just solidstart. Tanstack start, for example, is using the same blocks with react instead of solidjs.
