Solid.js Just Got WAY Better 

lmao

Yea been quite negative about bext past few vids .... imagine if he change t3 lol

@@darkoplax7688 I don't think the time has yet come, he still loves next, especially the server components. Let's see what happens next...

People are aloud to change their mind and grow holy fuck

Thank God, Vercel is the worst thing that could have happen to the frontend development space.

just discovered unjs universe and it's amazing

Maybe they add something like Qwik, they have a function to allow use any React component just by wraping it.

We have a Solid Discord with a support channel that is quite active. Support for Start however is minimal because it's a a beta product, I expect support to increase as we hit 1.0. :)

@@daviddibiase4727 I'm in it! I don't chat there, but it's been useful.

Yeah not really fan of using "use server"; in beta 2. I find clear front and backend better so you dont leak secrets.

​@@anonAcc575 I think with good architeture you don't need to worry about it, most cases just moving it to other file is enough. RSC make me prefer having server and client code in separated files, maybe Sveltekit was right all along.

SSR gets really interesting in an enterprise setting - especially in this era of hybrid cloud environments; making the sessions work is mind numbing. Stay away from it as long as you can. But if you need OAuth2 OpenID JWT auth ... better get ready for what is coming. It really is better where it is needed.

Also not super into SSR. Wanna try out the server functions and actions with client side routing tho. Could be nice alternative over writing express server.

@@klmcwhirter auth is the only thing keeping me away from Go + HTMX

Imagine getting a new job with Elm, it will be hard for sure, but yeah Next.js is pure madness... I stick with Rails and React(CSR), works nice.

And it's back-bone is hanging on the Vue community.

I wonder it will scale, but agreed most of the part u said

Qwik looks better to me

Apparently there is a huge react update. Does that change your view? Please explain

@@asemyamak3984 Nothing has changed. React is still going in the same direction.

Solid feels like it's not trying to "kill" React, but to be a lightweight alternative that makes sense and makes progress. I love that; it's website literally credits React as one of the "giants" that it stands upon.

Some time ago I was working on a WYSIWYG editor in Angular, a quite complex application with a lot of reactivity everywhere. We ended up with some pretty sloppy code with ugly solutions to prefomance problems. With Svelte5 and deep reactivity you're talking about it would be much much lighter, faster with the code much easier, shorter and streightforward.

Right!

I took a look at Next.js and I was reading about the Routing.... a complete mess all I could think was WHY? Gatsby.js has the most straightforward routing out there it just works... Frontend development is cringy@@dixztube

What about Inferno.js, seems crazy to rewrite stuff like this...

@@victor95pc oh thanks for showing me this! i‘ll take a closer look

please bro - this isnt nice its noice

noiiice@@Chaaos2

"That is why BE developers are seeking something like JQuery, for example ... Alpinejs" - BE developers don't use javascript for backend. We already have way better solutions. You can write be in js only if your app is really small.

I mean BE developers who want to do some full-stack tasks@@RaZziaN1

Way better? Lol

@@RaZziaN1 Plenty of large backends are in javascript.

​@@Lexaire or python

Svelte 5 is basically Solid internals with Svelte DSL. I'm not sure what a hybrid beyond that would look like. Do you mean mixing syntax ideas?

I had same confusion but if you are comfortable with react moving to solid js will be easy

Yeah! I have already started to experiment with with htmx and and Go, some teams have already built products with that combo. I will never trust js for anything backends.

Then don’t? SolidStart is great for client-only stuff

then just don’t? use anything you want for the task you are facing. rendering on server usually just results in smaller network bandwidth, better seo, allows you to write code for both parts of your app in one place and opens ways for other rendering techniques, but if you don’t need that, that’s absolutely okay, just use plain solid or react, or vanilla js

Not really. Solid is fundamentally different philosophy and rendering ability. You might however be interested in Preact Signals which is interesting.

I prefer to pronounce it "vinki", like Da Vinki twins

I wouldn't call Solid just a think tank. Our goal is to develop and sustain the project with the support of the broader community in a sustainable way. Many frameworks take time to evolve and land their official APIs, many went through years of iteration before they landed officially. The criteria and goal for 1.0 has been discussed a few times on stream and there is an internal goal, however it doesn't make sense to publish what that might be if the target is changing. This isn't a matter of PM skills it's a matter of R&D and exploration. We're as excited as you are to have new groundbreaking tech, but we have to give the effort the time it needs to mature. :)

@@daviddibiase4727 it is a lack of PM skills or maybe just fear of commitment. Your dissertation above confirms my thinking. The constant changing directions every 6 months to "play with new toys" or "R&D" as you call it is getting old. I am currently sold; but am losing patience. I hope SolidJS finds a Solid direction soon ... But here we go around again ...

React replaced something before it in the work place. It's smart to adopt new stacks carefully, to learn from them, in an environment that doesn't risk any business objectives if it fails. Of course companies can't blindly pick up every stack that turns up in the JS community, but that doesn't mean that frameworks like Svelte and Solid can't get a foothold, I know for a fact that plenty companies are already using these frameworks on large scale projects.

@@jnevercast when smth new come out generally there is a first race to it but once things settle whatever is left at the top just stays there unless they selfsabotage React just won imo and so many ppl and companies learned and committed to rely on react ... its hard to change that Its the same as OSs , Microsoft won the initial race and they became the default despite linux or mac are better these days or google winning the web race or samsung winning the phone manu race Its hard to see these techs fall after they get that 1st spot ... React will only not be the dominant option if smth AI wise displace it but just current js frameworks can never do it (same way bun deno vs node)

The company I work uses Nuxt 3 and it's perfect. I've never been so happy coding for a company lol. I'm truly glad we don't use React and don't plan to move to React.

Not long ago Angular was by far the most popular framework.

@@IvanRandomDude in the initial race yea but after things setlled nothing has moved which's my point

I understand, but man solid start is legit an exception. It’s truly amazing.

​​@@st-jn2gk I know, especially if you have worked with React for so long. It feels like everything React should've been.

@@st-jn2gk may I know why it's an exception? I'm really interested in learning solid but I'm just waiting for start to hit 1.0.0

That's the idea, making code wonderful, not boring. Every framework learn from each other and get better and eventually native techs get better as well, so those frameworks and libs become obsolete, just like jQuery. More frameworks push tech forward. It's like an open lab.

@@ojvribeiro Awe... Wait till you've done this bitch 30 years youngster.. And you've had to re-write the same web pages in 90 different flavors... And all ya want to do.. Is go home so you don't have a divorce. That's the thing.. They don't improve on themselves. The limitation is HTTP and the browser. What framework is... Somebody dipping some chocolate into some peanut butter and calling it resus peanut butter cup.. I mean.. HTMX. The reality of what Ive seen sense coding in 1992, the year the internet was released as a technology and the entire time Ive done full stack sense the internet has existed... We could have all just used C++... And applied it in variation of need. Script engine, compiled, Virtual Machine Runtime etc... When you've seen them all one after another a copy of a copy of a copy. A red dress is just a red dress...