Is SolidJS the better ReactJS?

[@CodeByNumbers]

We use SolidJS for all our projects now in combination with tRPC and Turborepo. It has been really simple to transition from React to SolidJS.

[@jackdanksterdawson112]

Amen brother, I am working with React and this looks like the next big thing. Will start learning this soon.

[@ljupcho3443]

Have i been living under a 🪨? Few months ago i read somewhere that it's not recommended for production use. Has this changed?

[@Cowayger]

​@@ljupcho3443 Even one of maintaners recommended svelte for now. Well, I tried to create production-ready app, and it is pretty solid stable.

[@AveN7ers]

I really hope it takes off. I've already made a project with it and, after the initial wtf of components not rerendering, I found it really enjoyable and easy.

[@SmokeIsInStock]

Do you have series on SolidJS? If not, do you plan creating? I am following your videos from years now and you have the best content !

[@akalrove4834]

I was about the dismiss SolidJS as another one of dozen JS Frameworks but boy I'm sold. This is so much better than React's weird mental model. No more jumping through the hoops for simple things like setting states or timeouts etc.

[@bojanperic1160]

Such a great explanation on both frameworks. Right down to what they are, and so easy to digest. Very informative video. Thanks 🙏

[@MrPlaiedes]

As a frontend dev with 10 years experience, keep your professional tech stack to one side and new tech on the other. Then use your new tech stack in your personal projects.

[@JoRyGu]

I am more excited about this taking off than anything else going on in JavaScript land right now. This is so damn good.

[@quelchx]

Honestly, if your starting from the ground up and your app is a SPA -- use Solid. I had to completely re-write a bunch of code for a company I work for and looking back at this moment I kind of wish our small team used this as a framework. React's ecosystem being massive it's so much easier to find developers with existing skills/familiarity of tools in the React World (eg MUI, React Query, SWR, Zustand, React Tables... I can go on). I'm sure a group of us developers could of designed our own styled components with similar functionality to what we aimed for or another example would be create a system that mimics say Zustands state management, but with clients requests and time being the enemy -- it wouldn't be wise IMO to adapt and adopt (at the time). I think Solid has a bright future and if it comes a time our group has a different project or we say screw what we got lets spend two weeks and rewrite this -- Solid will be my first choice for it's simplicity + additional performance. Im exited to see a metaframework like NextJS stem off Solid (like SvelteKit has evolved too)

[@easy-learning88]

Max, the fact that you have always popularized the React since you started your Academy, and the fact that you have recently written your book about React, I couldn't really understand how you decided to record this video and share your ideas with us about SolidJS and tell us that SolidJS is a better ReactJS. )) but, just wanna tell you that you are really an honest person, in my opinion, actually too much )) God bless you.

[@fahdfuhaid573]

A course is upcoming >

[@rumble1925]

I've played with it a few days, and so far: YES, it is a better React.

[@Viviko]

I’ve been using Solid for like 8 months. Yes. It’s better React.

[@s1nistr433]

Everything is better than React

[@Viviko]

@@s1nistr433 you aren’t wrong. React had a lot of good ideas. Everything else just executes them better.

[@linorabolini]

Its just an amazing tool. Specially because react hooks are hard to test. But signals and stores can be totally tested in isolation. This is also a great feature.

[@iurylippo6636]

Yeah, I was wondering if it is more debugable on browser then react

[@linorabolini]

​@@iurylippo6636 what do you mean with "more debuggable"? SolidJS is closer to what you'd do in plain JS so you can just debug it as any JS code.

[@iurylippo6636]

@@linorabolini I mean, the reactjs is so difficult to debug, you have to add some chrome extension like react webkits and debug the states through this extensions. I was asking if the solid is or not more "debugable" and if you can debug just through the chrome debug itself instead of add extensions like react do

[@linorabolini]

​@@iurylippo6636 oh I see! hmm too my experience, debugging code made with solidJS is way easier than react. The reason being that the code flow seems more predictable, you do not have all these constraints about re-rendering and hooks, its just plain JS code that you can totally test with unit tests because solidJS primitives are not tight to Components. I haven't used SolidJS in a big project yet, but I have made 2 pet projects and the feeling that I got is "things just work". SolidJS was made to just work with the simplest mental model people could find, and that gets clear after some days of usage. Hope this answer helps :)

[@RolandAyala]

I made the mistake of trying SolidStart and now I'm porting my SvelteKit project over to it -- even with SolidStart being beta, I'm sold on it . Nothing against SvelteKit -- wonderful framework! -- but I prefer the JSX/TSX syntax and not having my routes littered with Page files, and even though requires a little more effort, I prefer Solids state model. Both frameworks (Svelte/Solid) make coding fun again , and more productive.

[@riendlyf]

What is the benefit of using solidjs over sveltekit? Bundle Size, sso, ssr, ssg? I mean sveltekit resolve my business tasks

[@RolandAyala]

@@riendlyf Mostly comes down to personal preference -- they're both great frameworks that will solve just about any business task (as is true for all the other Frameworks as well). While a little more work, I prefer Solid's state model being more transparent and fine grained. I also prefer JSX style to the separation that Svelte provides -- almost to a fault with proliferation of page.svelte files, even though I appreciate the clieint/server separation it reinforces. Solid also packed with super cool capabilities like $server, so you can execute server logic from within page file (essentially like having built-in tRPC), control flow elements like For, Switch, Show working in conjunction w/ state management so collections, etc, are surgically updated. I didn't want to like Solidjs (I tried it out of diligence in evaluating framework for my next project) and I almost gave up on it because so easy to go back to Svelte (or Nextjs), but the more I used it the more I liked it. As an aside, people take about Solid's great perf, and while very good, it's not a reason to choose it over other frameworks IMO. Also, as others have said, Solid is to React as Svelte is to Vue, so depending on where you're coming from, will have a natural affinity to one over the other.

[@shrin210]

​​​@@riendlyf It's not performance difference, even if you use Reactjs, it will performant enough for many projects. After that it comes to developer experience, i also now prefer Reactjs jsx syntax after doing Reactjs projects. I feel while building large projects, code could get Messier in SvelteKit , dev experience will be frustrating. Can you tell me your experience with SvelteKit ?

[@neekawsaur]

Thank you for the concise overview. That was exactly what I needed!

[@jaymartinez311]

I’ve been waiting for you to create a course on it. Won’t touch it more then the basics until you drop a course!😂 maybe wait until ‘solidstart’ is ready to be released.

[@UrbanBDKNY]

I love the lack of infinite loop React Hooks has lol the loading and error utilities are nice too

[@DucaTech]

SolidJS sounds pretty ... solid.

[@shyamvenkatesh6188]

I have a doubt at 4:14, you say that the doubleCount value changes only when the associated signal changes. Then what is the purpose of using a memo method?

[@levinkerschberger2615]

If doubleCount would be very expensive and hard to calculate, you might want to cache the results somewhere. Memo handles that for you. Without it, the expensive calculation would be done very time, even if it was already calculated. Let´s say your user searches for something and the derieved values is based on his search. He searches something else, but decides to search for the first thing again. In this case, you already know the result when using memo, but you would calculate it again using a simple derived signal. I hope this helps someone, even if the comment is pretty old:)

[@albertocastany]

looking forward to this course

[@sanv-5505]

Switched to Svelte, really loving it! Solid JS seems to a great alternative for React!

[@jma42]

bruh solidjs signals are a bliss, no pesky state managers like redux recoil or some shiiit

[@aquaductape]

drag and dropping createSignal/createStore declaration line outside of component scope is wild

[@r.chitector]

I tried to use SolidJS for my projects and I will definitely use it for future ones! It's much easier than ReactJS!

[@niemand2485]

@@nonono9700 you don't say

[@AndiSyafrianda]

How many people on your project? Sometimes it's hard to find people to join projects with less popularity.

[@Cowayger]

@@AndiSyafriandaIt is a hell, even paid third parties prefer to use Angular over some requested tech.

[@lasindunuwanga5292]

I knew the advantages of Solid over React, but I never felt it this deep until this video... Thank you very much... one more thing, am I the only one that rings bell when ur face is seen... king arthur - legend of the sword?

[@nerdcave0]

The "running function code only once"/reactivity system is the superior mental model for sure. So many problems with re-executing component functions that seem absurd once you see a better way.

[@dealloc]

As someone who have evaluated both approaches on large scale apps, I can say that signals still has problems. In some cases it's even harder to wrap your head around to keep state in sync, where it just works by re-rendering everything. There are also gotchas with signals that can lead to poor performance that is really hard to track if you're not careful. That said I love SolidJS. Its primitives (createResource, For, Show) are my favourite part of it. Signals is nice too, but is not as simple as it may seem on the surface.

[@onça_pintuda999]

@@dealloc After a year, what are your thoughts on it?

[@elson_correia]

This guy is a great explainer 😊

[@CodingAbroad]

As a team lead we’re redoing our cms and website using Angular and since we keep the code consistent for our small team we’re happy with our choice

[@ChristianMoentest]

I'd like to come back to this comment in some years.

[@CodingAbroad]

@@ChristianMoentest how come? :)

[@bloodjopa]

11 days passed...still happy?

[@CodingAbroad]

@@bloodjopa still loving it thanks. No major hiccups. The only difficult aspect has been getting the team trained up

[@stasoline]

It sounds like Svelte but with crappier syntax. :)

[@gkiokan]

@academind can you compare this against vue? Vue is way simpler then React and still Powerfull.

[@maacpiash]

Yes, for the most part, SolidJS _is_ the better ReactJS.

[@lowzyyy]

what are other parts that are worse?

[@ElektrykFlaaj]

@@lowzyyy other parts are just not better, but not worse. Maybe the thing that react has better is the amount of well maintained libraries

[@ajiteshmishra]

@@lowzyyy eco system maybe

[@maacpiash]

@@lowzyyy yeah, the other replies are correct. ReactJS has a vast amount of libraries, which SolidJS lacks. Obviously, this has nothing to do with any merit or demerit of SolidJS.

[@arvi8843]

@@lowzyyy Well maintained libraries e.g I wanted to try svelte and solidjs for graphql but those are "spare time" projects of authors however the react one is built in in Apollo client and maintained by Apollo team. It's a big deal if you're using graphql. 😅

[@HarshalHirve555]

Thank you for this informative video. Solid Js looks really good and performant. Please try to make a full course on Solid JS soon. Eagerly waiting....

[@seananih7609]

Just go through the documentation instead of waiting for his tutorial (assuming you REALLY want to learn Solid)

[@HarshalHirve555]

@@seananih7609 I have already gone through it. But his course helps many others who do not know about it.

[@kostraone]

Looks they're doing what vue does, with a react look-alike syntax

[@marusdod3685]

SolidJs is what I thought React was before learning

[@ekimbangola]

Thanks man. Great work

[@HumairaMaqbool-t2l]

As an AI language model, I don't have personal opinions. The choice between SolidJS and ReactJS depends on your specific requirements and preferences. Both SolidJS and ReactJS are JavaScript libraries used for building user interfaces. They share similarities as they both follow a component-based approach and use a Virtual DOM for efficient rendering. However, they have some differences that might influence your decision: SolidJS: Performance: SolidJS is often touted for its impressive performance. It uses fine-grained reactivity, which means it tracks dependencies at a granular level, leading to fewer unnecessary updates and faster rendering. Bundle Size: SolidJS is known for its small bundle size compared to other frameworks like React. This can be advantageous for applications where reducing load times and optimizing performance are critical. Learning Curve: SolidJS has a smaller API surface compared to React, making it easier to learn and grasp, especially for developers who are new to frontend development. Ecosystem: SolidJS is relatively new compared to React, so its ecosystem and community support might not be as extensive as React's. ReactJS: Mature Ecosystem: React has been around for a longer time and has a large and mature ecosystem with abundant third-party libraries, tools, and community support. Popularity: React is widely adopted in the industry, and there are more job opportunities and resources available for React developers. Community and Documentation: The extensive community around React means that you can find solutions to common problems and access a wealth of documentation and tutorials. JSX: React uses JSX (JavaScript XML) for defining component structures, which many developers find to be a powerful and intuitive way to work with components. Ultimately, the choice between SolidJS and ReactJS depends on your project's specific needs, your team's familiarity with the library, and your preferences regarding performance, bundle size, and ecosystem support. Both libraries are capable of building efficient and powerful user interfaces, so you can't go wrong with either choice. It's essential to try them out and see which one aligns better with your development workflow and project goals.

[@anassnassim]

i was trying to remeber you and then i remember that i learned the angular from you it was a great great course thank you so much for that

[@ravijangir7519]

thanks for valuble suggestions

[@mfmn6397]

I would really like it if you could make a Udemy course for SolidJS & SolidStart

[@planesrift]

It has the good part of React (love the component functions). I really hope I can use it at work.

[@LearnFrontendNow]

That was an amazing breakdown Max, thank you!

[@johnwalter8024]

Thanks for great explanation by any chance do you plan for a course for solid?

[@nosthrillz]

Sounds a lot like Vue 😁 does it use proxies too?

[@nero1375]

how about reading the docs once and while? hehehe

[@nosthrillz]

@@nero1375 just once maybe. I don't develop at all in the react ecosystem, sooo there's no reason to remind myself later to read about it. I see this videos on the phone and I'd forget if i wouldn't just get a reply here 😁

[@Tszyu01]

Yes it is better but people won’t use it because they can’t just use MUI or similar and refuse to build components themselves. I feel without frameworks like MUI based on comments from Reddit on various frameworks and complaints around “lack of community”, some people would struggle to even make a card component.

[@aquaductape]

There's a SolidJS version of MUI called SUID. Zag, the same author who wrote Chakra UI, has SolidJS support. There's also Kobalte, a UI toolkit with accessibility in mind. Flowbite, a component UI lib with utility classes from Tailwind CSS, supports many frameworks including Solid. Lastly there solid-bootstrap, pretty much React Bootstrap but in SolidJS.

[@Tszyu01]

@@aquaductape SUID seems really solid. I was mostly just teasing people on Reddit who reference “community” or lack of it for newer libraries/frameworks for a reason as not use an objectively better alternative.

[@onça_pintuda999]

You are good damn right! And I was in this same position in the last few days, dont know how to bring solid to the team, but I'm going to make a LP with Solid + Tailwind + Daisyui, dont need too much. Some will say "why didnt u just used react for the other to support in the future" but fuck em, react is shit and they know it, solid is simpler than react and thats what I need.

[@zubayrganiyuseun6387]

Svelte kit next please

[@fintechtelugu6980]

Solid JS is written in Typescript 👍

[@sky_kryst]

Good to hear your voice again :)

[@ishraq95]

Why sveltkit is not getting popularity?

[@josephs1732]

Been trying hard to move away from svelte-kit to solid-start. JSX lets me break UI into as many smaller components within the same file. Its annoying to go back to svelte's single file component model. Solid signal seems interesting although not sure why we should care since we already have RXJS. Its even more confusing now that I hear angular is trying to incorporate signals. What exactly signals solve that RXJS cannot? Hope to see more videos on solidjs.

[@dannydevs]

Check out Ryan Carniato's YT streams. They're super long but he goes into RxJS several times. Not sure how deeply, but he did a whole talk with Misko on Angular.

[@KomarNaWulkanie]

Solidjs is awesome framework and it deserves a course. Also svelte need to be updated quickly...

[@siya.abc123]

So most importantly SolidJS does what you tell it to do. It's intuitive like that

[@haritpatel5001]

Amazing explanation...

[@lcarv20]

When it comes to react alike frameworks solid is great, I love it, but my favorite frontend framework is still svelte.

[@gyorgykovesdi]

Indeed, Vue and Svelte is way more clean and simple than any other framework. SolidJS may be more performant, but I hate JSX spagetti so much, i would never use it...

[@lcarv20]

@@gyorgykovesdi It’s also about developer ergonomics am I right?

[@slmjkdbtl]

@@gyorgykovesdi jsx is optional, you can also use hyperscript or html string

[@naranyala_dev]

waiting for the crash course

[@JeremiahFulbright]

Huge fan of SolidJS

[@codernerd7076]

SolidJS is too new for me still, one solid rule to survive in the Javascript dev world not jump on every framework that comes out, and wait to see of its just hype or really will become the big 4th framework

[@ak-loz]

Is Svelte still too new?

[@georgeokello8620]

I have worked with SolidJS for 8 months on my start up project and so far it's very solid, even more so than react. On my next start up project, me and the team are looking to work on creating some server components that are going to be hydrated for a large scale application using geo location but want as minimal of a JavaScript footprint as possible as the app is going to be performance sensitive. SolidJS seems much more accommodating currently right now with the introduction of SolidStart

[@Daijyobanai]

I think we should look at the problems a framework solves. React solved a problem that needed solving.... 5-8 years ago, but now it's more pain than gain. It's been used where it shouldn't be used for projects that could have been done better with other tools. Devs are coming in learning react before they learn JS, or even how the web works, and it's damaged the industry imo. It's time for change.

[@IainSimmons]

That's what people said about React at the beginning (and worse things!). The beauty of Solid is that if you know React, Solid will be easy to learn. Eventually the ecosystem will grow. If it's for work and many devs need to use the codebase, then sure, go the safe route. For anything else, give it a shot!

[@nero1375]

@@Daijyobanai finally a good comment down here..

[@gyorgykovesdi]

Well, the question was: is SolidJS the better than ReactJS? And the clear answer is: YES. The other things mentioned like how smaller community or which company is behind it not matter at all (actually most framework/product made by Google or Facebook is an instant "no-go" for me because they love to build over-bloated non-performant stuff, at least on the frontend side)

[@黄胜-u6h]

It is enough to transplant the best 20% of the react ecosystem to solid

[@mikedev4673]

From what I experienced, if you have been using Angular you would probably like Svelte, and if you worked with React you would probably like more solids, anyways I really hope this two frameworks will replace the current ones in few years. thank you for sharing it!

[@isimvol]

If you are building a prod app in 2023 it's between React and Vue

[@ishraq95]

True

[@ishraq95]

@@isimvol svelt is 20X faster than react mind it..

[@ishraq95]

@@isimvol vue and react are for children.. Angular not for children Developer...

[@PatrickFerreira-id7bd]

@@ishraq95 Grow up.

[@meka4996]

You forgot to mention SolidJs runs only a bit slower than vanilla JS, but faster than all other frameworks!

[@dannydevs]

Vue Vapor will be right there with Solid in a year or so ;)

[@dixztube]

Oh that’s clever how it works

[@fallen_turbo]

Hi Max, what do you think about Qwik

[@fegyi001]

So this is basically the same thing Angular will implement in v16 with Signals, right?

[@rutpshah]

Every new framework comes as a killer of some top tier frameworks and miserably fails due to lack of community. Who wants to keep changing frameworks every now and then for large scale projects??

[@PanzerFaustFurious]

This sounds almost identical to vue 3. Createsignal() = ref() Creatememo() = computed() CreateEffect = watchEffect

[@academind]

It's true - they definitely share key concepts

[@maskman4821]

Thank you for letting us know about this, if this is the case then Vue developers should have no problem trying Solidjs 🥰

[@MMohammadJS]

Max i am ( and i think not just me for sure ) waiting to hear your opinions and explaining about chatGpt 🤔

[@inDefEE]

i’m starting up a new proj and am really considering going with solidjs. Only concern is SSR which I need. SolidStart looks unfinished and wondering if anyone has tried?

[@eleah2665]

Cool. Thanks.

[@mohammadmahdialvansaz8001]

Thanks.

[@beyourahi]

for a mid to large size e-commerce website SolidJS or Qwik will be better?

[@omergronich778]

Yes

[@majdeddinebentahar5434]

hey max, hope you make more videos like the type of this one, have a good day.

[@stefan8857]

From pure Dom to virtual Dom to pure Dom, next up back to virtual dom

[@academind]

Hehe, going in circles!

[@Thorax232]

Basically React with Valtio. Solid has always felt like a novelty framework. They're not the first or only to use signals and proxy objects. They need to do way more than that to be anywhere near where React is.

[@JoRyGu]

The literal only thing React has going for it over Solid is the maturity of the ecosystem. Solid feels essentially like the sequel to React, where it learned all of the lessons from the mistakes they made when developing React and fixed them.

[@dannydevs]

Wait a second, way more than what? Not providing a first party router? Not providing a first party state management library? Not providing a meta framework? React has dropped the ball in so many ways for BOTH devs and product users, but to make it worse they've gaslighted and red herring-ed and misdirected for so long that I'm amazed at the Stockholm syndrome that a lot of React devs have.

[@fyriss_]

What's the point of "createMemo" when component function is executed only once and there are no rerenders of whole component?

[@IainSimmons]

If the signals used in the function you pass to it don't change, it won't recalculate. Useful for more complex or resource intensive calculations. But yeah, it's so fast that if you just use the regular derived functions, you're unlikely to notice many issues.

[@fyriss_]

@@IainSimmons Yes but the same way it works like that right? const dogAge = Math.floor(age / 7) Where age is signal getter function

[@PRATAPSINGHSHEKHAWAT]

Please give some opinion of qwik framework.

[@AllenZWalker]

will take a look, I find remix like the next big framework, maybe in the long run solidstart will be a good alternative.

[@IainSimmons]

I think it would be in Remix's best interests to switch to something like Preact (core team members of both frameworks are employed by Shopify). Remix has had a big impact on a lot of other frameworks in the space right now, but I don't think they are seeing the growth they hoped for.

[@dannydevs]

Remix is going nowhere with Next JS in the room, and overall the React ship is slowly going down in flames.

[@AERNIGH]

This is pretty good!

[@mello1016]

Svelte and Solid are the best frameworks in the market. Sadly the ecosystem effect will continue to force developers to choose inferior solutions.

[@SilvestreVivo]

Totally agree

[@dannydevs]

Nope, Vue 3 is awesome, Nuxt 3 has some amazing features. Vue 3 is as fast as Svelte according to a benchmark I saw (Evan You acknowledged that after optimization Svelte will probably be faster, but Vue Vapor will mean Vue will eventually be as fast as Solid, which is faster than Svelte). Vue is battle-tested and has a huge community and ecosystem compared to Svelte and Solid. Vue 3 Composition API looks very much like React hooks/Solid, and is SFC like Svelte/Angular. The Vue team is on fire right now. The Golden Era of Vue is just beginning ;).

[@mello1016]

​@@dannydevs Vue awesomeness cannot be denied. It also has quasar which provides fully packaged multiplatform developer experience

[@yokowasis]

So it's basically a react sibling that is loved by everyone ? as a first born, I can relate.

[@dragotti]

3:14 you can do that in React, lifting up the setState function from children component to father, or am I wrong?

[@IainSimmons]

No, you need a useEffect and you need the setState call to be in the function form. Otherwise it's basically creating a new interval function on every render, which is every time the state is set, etc etc into infinity. I think in dev mode React will stop and tell you that you broke it though.

[@dragotti]

@@IainSimmons Thanks!

[@nyambe]

How does it compare to Vue3 ? how does Vue 3 use the virtual doom?

[@rudinandrey]

is Preact better then React ?

[@tinmank]

I wonder how it works with chrome extensions, or in-browser translate tools. They directly inject on DOM. So could any outside dom injection could break it?

[@aashiqahmed5273]

love diving nito solid js

[@jhadesdev9576]

Does SolidJs really give the guarantee that the component function will never get called again? Or it still needs to call them again occasionally on the client? So no need for hook-style APIs on it, right?

[@IainSimmons]

Yes, because it's just like a regular JavaScript function would work. The JSX turns into template strings and then into actual DOM elements rendered on the page. You can't "call" DOM element functions like div(). It's actually React that is doing really weird things by having React.createElement and then having to call component functions again and again that makes it the unpredictable one.

[@oriongalactic]

when will come a js framework that were WASM base? That would be worthy to learn since using that technology would speed up the performance and also render smaller bundles

[@subham11]

Looking forward for something same as Solid Native :)

[@nero1375]

Nativescript could solve this

[@walidlezzar2357]

Doesn’t preact signals (also usable within react) provide exactly the same functionality in react?🤔

[@codokit]

What about solid native? React Native is huge, but do we have any answer from SolidJS team on this topic?

[@icarusgk]

Vue has been doing this since long ago, sad to see it doesn't get the recognition these other frameworks get.

[@damjanstojanovski3144]

yep i was thinking the same...Vue runs the component functions once as well. And also i think VUE does get recognition and its used in more and more places

[@arden6725]

True, but svelte takes one step further by letting you write component code that looks like vue, with even less pitfalls,. and a way smaller bundle size. That's why svelte is taking vue's popularity right now

[@icarusgk]

@@damjanstojanovski3144 Yes, what I meant by recognition is that "Signals" are being announced as this breaking new feature in the world of JS while Vue did it with ref() and reactive()

[@icarusgk]

@@arden6725 The smaller bundle size is true for small apps, it has been shown that as the app continues to grow it generates a bigger bundle size than the ones from Vue or Solid

[@ryansolid]

@@icarusgk I was mostly going to not respond here. But this is worth clarifying. "Signals" have been around since 2010 and KnockoutJS. I've never claimed they were new. Solid has been using them in the primitive composable way since I first created the library in 2016. Vue has had this reactivity under the hood from the start but only went to composables in 2020 when they introduced ref and reactive. The world I created Solid into was nothing like it is today. It was a world before Hooks and Composables and suddenly when the world did change I found myself in the eye of the storm. Also Vue setup functions run once, but their templates rerun every time as they are a VDOM library under the hood. So the similar constructing virtual nodes and then diffing and patching as React happens. Solid's DOM is updated granularly as if individual expressions were written with `watchEffect`. This is more of a technical detail but accounts for the difference in performance. That being said I think Vue gets a worse rap than it deserves especially compared to Svelte given it scales better and generally is more performant (when optimized). And Svelte is still a component lifecycle re-run model even without its Virtual DOM so it isn't all that different. Interestingly Solid is probably the most different from React but I don't think that is well understood. Vue is working on a new compiler to generate Solid like code called Vue Vapor. So you may be able to experience the benefits of Solid in your Vue applications before you know it.

[@sobrevivendo-no-front]

I did a small project with Solid and some experiments. It's really amazing, but I still don't think it's distinctive enough to make me switch from React, giving up everything that already exists and the entire ecosystem.

[@akj3344]

finally a sane comment. I think its literally "just another framework". React is a better choice because of ecosystem and and its very well tested.

[@IainSimmons]

People used to say the same about jQuery. Eventually, every need you have that can be achieved in React, would also be achieved in Solid. It will just take time. Also, if you have vanilla JS libraries, they are way easier to integrate with Solid because it's closer to regular JS (the code outside the JSX is mainly unchanged in the compiled output)

[@adeleke5140]

@@IainSimmons let’s wait and aee

[@MahadyHasan]

Although I haven't used SoildJS yet, the features I loved that I've seen about SolidJS so far. SolidJS will definitely give a more comfort development experience than ReactJS in near future.

[@matthewbecker2387]

I'll definitely be sticking with Vue. HTML in JavaScript functions is just wrong.

[@yourivanmill]

I don’t like JSX either, just give me plain html and I’m happy

[@dannydevs]

Actually it isn't, as Vue itself allows users to use JSX. JSX is sometimes needed when adding logic to the template reaches its limits, and JSX allows the full expressive power of Javascript to be used along with HTML.

[@laughingvampire7555]

is there a solid.native?

I hate that react is worst of them all, but not bad enough to make people going away from it. And there is no JS framework could replace react native anytime soon :)

[@kidbrave_7673]

Solid Js looks solid, but if you want something straight out the box that’s very developer friendly, powerful and less complex than react and solid is pick up alpine js. That’s the game changing framework we need to all be talking about! 😀🙌🏾

[@shimadabr]

Alpine js seems great on small to medium projects. They even advertise themselves as the modern Jquery, so it seems appropriate when the app doesn't need too many components and state management (so, most of the projects).

[@kidbrave_7673]

@@shimadabr Man you completely nailed it with that message! You’re exactly right! I honestly think it really depends on the individual when it comes down to it. Are they looking to get a job in the industry. React and vue are the 2 to use. But, if you’re trying to build an application as a freelancer or build a startup something like alpine or hell even vanilla JavaScript would be a very solid approach because you don’t have to worry another your JavaScript needing to compile. Which in my opinion UX approach of things I think vanilla js is better than any of these frameworks because of the page loading time. But, these are my personal opinions and my Bias opinion.😏

[@AmodeusR]

Why does destructuring breaks SolidJS reactivity system?

[@aashiqahmed5273]

thats the part of the process

[@AmodeusR]

@@aashiqahmed5273 Well, that part I got. I wanted to know what happens that it does so it breaks the process...

[@dannydevs]

Evan You just recently said that you can preserve reactivity with destructuring in Vue 3. Not sure if it's in development or has been released. If Vue does it, probably Solid can do it too...

[@s_mehta]

Please make in depth laravel courses. Thanks.

[@martijn3151]

Just switched to solid and when I now look at the react state mess, I hope I won’t switch back

[@HariKrishna-mi6is]

What about qwik

[@tejasshekar]

So, are you saying its better than react and does not have any shortcomings ?🤔