Bro really tricked me into thinking I was watching one of those "X in 100 seconds" fireship videos haha Great video none the less keep up the good work !
Solid looks solid It has a set of cool features: return value from "setSignal", dynamic getters, much easier memoization/render optimization one question for anyone using solid: is there feature parity with React's "key"? i want to be able to "re-mount" component and I haven't found anything like that
I'm assuming you are talking about the key prop/attribute that you specify in JSX. SolidJS handles the "key" for you with the `For` component. When rendering a collection you don't use the array `map()` method but you use the `For` or `Index` component. `For` moves the DOM elements representing your component around the list based on the referential identity of the `item` being rendered the moment the positional index of `item` changes. `Index` on the other hand leaves the DOM elements in place while `item` is rewritten in the appropriate position as soon as `item`'s value changes. `For` is considered the keyed list iteration and is recommended when `item` is an object where you render its properties. `Index` is non-keyed list iteration which is an optimization when `item` is a primitive data type (string, number, bigint, boolean) because its faster to rewrite the relevant, corresponding string values into text nodes than moving the DOM elements around.
@@SebastianSastre Hey! Yes - the component hierarchy and data exchange follows the same patterns React does. So you can pass from the parent component to the child component state and behaviour (methods) as properties.
@@awesome-coding I've used react since it's first release and for me svelte is a game changer,it's remove all cognitive complexity of react, animations are simple, store global state is intuitive and that is something that after develop in react we forget, how react has became unintuitive for new developers and how many concepts they need to learn in order to use it and I'm not going to even mention redux...but I can understand that this depend of tastes and habits...solid looks great too
Hey! You should probably have some algorithms knowledge (this is a prerequisite for anything coding related). Then some experience with JS and HTML would help. The advantage of Solid is that it's a fairly small library, and they have great documentation. They are linking to some good reactivity articles as well, which is important to understand since it is the concept that ties everything together.
Ok, you showed that it is somehow different snd somehow dimilar. But what problems that it solve? Is it another member of new wave hype driven development? Or maybe it solves issues which other frameworks csnnot solve?
Hey! I don't think it solves anything new but it is: 1. Smaller than the majority of existing frameworks; 2. Faster than the majority of existing frameworks; 3. A clear improvement over the most popular framework at the moment (React); So the way I see it - A car is a car. It'll take you from point A to point B. But driving the 2022 full option model is way better than a 10 year old second hand car.
Is this something that I can use to create an app using a native web components library? Most components will come from that library. So, I need mostly binding, router, state management, and change management (reactivity) for the most part.
Hey! I don't have enough experience with Solid's web components results to give you an informed response. I successfully used Stencil (stenciljs.com/) in the past for such things though.
Solid works well with web components, it was initially designed to be a web component framework which is why it doesn't have runtime components. Also Solid is a state management / reactivity library first, you don't have to use it for rendering.
I'm going to have to check this video again maybe Monday, but... I need to ask now... can beginners quickly create video games for Android through Solid JS and if so... please show us how.
Creating games for Android is a hard place to start for beginners, although i would first look into Android SDK and app development and learn Java or Kotlin. If you're set on making games I would definitely look into Unity, Godot and Unity. But do know that you're not going to create your dream game right away, learn programming and software engineering first. I recommend using python or JS, then C#.
@@jonasls Long ago... years before AndroidOS had hit the market... I had created about 20 games on my own for the Nokia Smartphones and earned really good money from those which... funny enough... was because of PyS60... a SymbianOS smartphone version of Python super easy to learn... and processes just fast enough. Had spent about 8 years altogether trying to program in Java... JavaScript... and all the C variants, except C#... whereas those kept giving me far too much of a headache, meanwhile... I really enjoyed Python right from the start. Lately... I've been hearing a few people tell me that they made awesome games for Android with just HTML5 alone. Not everybody is focused on creating only AAA games, but... thanks anyway.
@PaulKHeld is right. I find Solid's native store support powerful enough to handle all use cases. Remember that even Facebook came up with Recoil - a very light weight state manager which removes some of the clutter you'd find in Redux. They are also pushing the idea that the Context API can replace a 3rd party state manager most of the time. So, in my opinion, the general new direction is to handle state management without the need for 3rd party support, or with very light weight libraries.
What is the alternative? Building slower websites with wasm? Building websites with Flutter Web, a technology that can't even get scrollbars right and is also very slow?
Hey! This is an interesting perspective. The way I see it is that SolidSJ is actually only competing with Svelte. Their approaches and results are visibly different compared to Angular, React and others - way smaller bundler sizes, x times faster performance, no virtual DOM, real reactivity. It feels to me like another generational change, just like when we got away from Angular 1 and Backbone. PS: I am excluding ANgular form this. They have their own market and niche they are addressing, I doubt anything will change in that enterprise environment.
@@awesome-coding Svelte is probably Solid's primary competition because people think that they are similar. Vue is faster in the js framework benchmark right now than Svelte and will become even faster without a V-DOM. Also Vue's reactivity is almost the same as Solid's, traditional pull based reactivity. Svelte is not necessarily what people usually call true reactivity, it kinda is reactive cause it gives you an API that looks similar to Solid and Vue but it compiles to reactivity that is more similar to React.
Hey! Most of my Vue experience is based on version 2. I can't make a fair comparison since I'm not familiar with some of the new things Vue 3 is offering. However, I think that Solid has a smaller API, and overall less code is needed to reach the same results.
Solid and Vue are very similar in their core reactivity. The templating is obviously different, also Vue has a V-DOM and is generally a bit slower. They also have different learning curves, Vue tries to be simple to begin with but overall is a bit more complex than Solid, Solid tries to have little overall complexity and minimal API and the idea is that you don't have to learn a lot of things to master the framework and even understand how it works. Also there are some differences in philosophy, Solid's philosophy is more similar to React's, and it supports concurrent rendering and time slicing.
Thanx for Solid intro, interesting, but, honestly, real game changer is Flutter with Dart. One langwidge and one framework to rule Android, iOs, Win & Web. I lazy and I like it :)
I don't know how good flutter is for native but for web (websites not web games) it's one of the worst technologies you can pick if you care at all about quality. Also you can do native with Solid.
@@orenelbaum1487 as developer I completely agree (also it's so stupid - G develop Chrome with all of web thing's, but here they said "oh crap, just get canvas and WebAssembly"). On the other hand - it works, and business may have one command for any kind of task and save money. I see it's our future. Not shiny, but acceptable.
Hey! I think that once you make a decision about a framework, that echosystem is pretty much complete. Think of React where you have tons of libraries to cover any needs, you have Next.js to bring it all together, and seamless deployments with Vercel. Not to mention Vercel offers edge functions now. The benefit of new libraries and pioneering work in the space, in my opinion, is that it pushes everybody to do better. You don't have to switch every time a new framework comes out, but by studying it, it helps you understand what's possible, and what can be improved in your workflow.
@@awesome-coding I was jokingly mentioning the 3 different configuration files for one project. As a Full stack dev what hurts me the most is configuration mess and setting up environments. The progress is there, I wouldn't call it "Pioneering" - There's nothing new about high performance HTML renderers. It doesn't add any new concept, just reuses concepts in a new implementation. I don't say it's bad, but I want to point out the complexities of simply rendering html and making an interactive application. We need more unification alongside complicated tool chains. (Here I recognize Node+Typescript+React+Vite+Scss). As a developer I find it really interesting (Good video btw) but at the same time I want simpler technologies and that's why we work so hard to give people simple efficient systems.
I completely agree it's weird to jump through so many hoops with configuration. I was doing React pre CreateReactApp, and I remember what a nightmare that was. Maybe that's why now, as long as the config files are there but I don't really need to worry about them, I'm completely fine :))
@@awesome-coding not for any production applications yet. Fundamentally it's completely different from existing SSR frameworks. Instead of being built using rehydration fundamentals, they've implemented fine grained lazy loading using resumability
I've tried everything out there that claims to compete with React. Yet I find myself always back at React. I've yet to find anything that comes close to beating it, and the support is great. React is really very simple, so why try to simplify that even more? The only contender to React is Elm imho.
I agree with you to some extent. I also face the same issues when leaving the React ecosystem - I'm missing all the 3rd party support and the known flows. However, I can't deny the fact that some of these newer tools such as Solid, and Qwik more specifically, improved a lot of the performance and the dev experience. The only issue right now is their small adoption, but if any of those will gain more traction and a larger ecosystem, I believe they'll become a real alternative to React.
I think a couple of larger component libraries already started porting their work in Solid as well. They have routing, state management solutions, SSR and various utilities. Do you think it lacks some other core features?
There are component libraries for Solid. The ecosystem is not nearly as big as React or Angular but it's not like there isn't an ecosystem. For the most part it will have most of the things you need and the one big thing that is still not 100% ready is the SSR solution Solid Start but it should become stable soon.
It uses JSX, and follows the same hooks API, which are approaches pretty popular in the space these days. It takes what React has best to offer and builds on top of it.
JSX is definitely not for everyone. As a fun fact, I just found out today that the creator of Qwik is Misko Hevery, the guy who came up with both Angular JS and Angular. With all his Angular background he still decided to use JSX for Qwik which, to some extent, is a testimony that JSX is pretty neat.
@@awesome-coding there are two different ideologies. One is embracing the mix of two different types of languages since there is a lot of coupling (html-js) and the other is separating markup from logic. Since both are equally valid, there will always be people and frameworks to support them. I like nuxt 3's approach where it supports both jsx and template style but svelte's absence of vdom and whatever client runtime on client has won me over
@@Yorgarazgreece I completely agree with you on the vdom aspect. With this new wave of frameworks it looks like we are going back to good old DOM updates. jQuery V4 will probably win all of us back :))
You can use Solid without JSX, it supports template literals and hyperscript syntax (what React JSX compiles to). Technically you can even integrate it with Svelte's and Vue's DSL. Also Other than the DSL and different philosophies Solid is way more similar to Vue than Svelte. Svelte is a bit more similar to React. Vue and Solid are already a bit like different versions of the same framework and with Vue Vapor they will be even more similar.
The main benefit of using show is that you get the fallback property, which makes the entire clause more concise. You can also use the ternary, since it is JSX after all. You can Solid without TypeScript. I added TS in because I find it useful in both smaller and larger projects.
Hey! Thanks for the feedback! Indeed, Fireship is a major influence for me, mostly because I like this quick tight format. I'm still experimenting with all this - I guess I'll develop a more unique style with time.
Hey! To some extent you could say that. However, the API is more straight forward and you have everything under one small (~8kb gziped) library which is way faster than react.
Hey! It’s not really my intention to copy Fireship, but I am mostly resonating with that fast paced style of his. I’m pretty new at this, and I’m still working my way through all of it. With time I hope I’ll be able to find my own style :)
@Tyrone may. Dude... calm down. This is great content delivered in a great way. There's a difference between copying and being inspired by someone's approach. This is new and cool content delivered in a familiar style that works well. I like it.
Can you speak faster and less clearly please? Don't forget, zoom out more while rambling we don't need to see and understand the actual code you're typing.
Hey! I'm working on the voice overs - I know things can be improved. :) The video is fairly fast-paced because I'm trying to squeeze in as much information as possible in under 10 minutes. Clearly this is not the best format if you are interested to follow along with my coding. I'm considering doing such videos as well, but they might be closer to 25-30 mins, and I don't know if they'll spark the same interest.
@@awesome-coding I appreciate the effort and I know it's not easy but I was kinda disappointed I wanted to learn something but I'm sure a lot of people did find it useful and got something from it. Best of luck!
@@awesome-coding stay like you are, I much prefer fast video that covers all I need to know without spending 30mins on a vid I'm in my toilet taking a shit rn and it's specifically because your video is < 10mins that I'm here It's true that it's fast, but I can pause whenever I want if needed. But I'm an experienced dev (mainly with React) so maybe for begginers it's harder to follow But the video itself is clean, good job
@@commecestbizarre Thanks for the feedback! I know that me talking is not always that clear - hopefully it get better with time:)) Other than that I'm planning to stick with the fast phased format for certain. You are completely right - the video is intended to give you a quick overview of what Solid has to offer, and it helps if you are to some extend an experienced developer. Thanks again for the kind words!
Solid core team member here: thank you so much for covering us! What an Awesome video
Hey! That's cool - glad you enjoyed it!
@@awesome-coding he also does Astro. You know what to do next :-) stable release is going to be there in a few weeks
Thanks for the suggestion!
It's just another js framework... one of the gazilion js frameworks.
"How long does it take to change a lightbulb? Around 3 new js frameworks"
That's a pretty funny joke! :))
You deserve more views
Good Quality Content Right There!
Thanks! It means a lot!
Bro really tricked me into thinking I was watching one of those "X in 100 seconds" fireship videos haha
Great video none the less
keep up the good work !
Haha! The eastern european, low cost fireship version.. 🥲
Thanks for the kind words!
Solid looks solid
It has a set of cool features: return value from "setSignal", dynamic getters, much easier memoization/render optimization
one question for anyone using solid: is there feature parity with React's "key"?
i want to be able to "re-mount" component
and I haven't found anything like that
I'm assuming you are talking about the key prop/attribute that you specify in JSX.
SolidJS handles the "key" for you with the `For` component.
When rendering a collection you don't use the array `map()` method but you use the `For` or `Index` component.
`For` moves the DOM elements representing your component around the list based on the referential identity of the `item` being rendered the moment the positional index of `item` changes.
`Index` on the other hand leaves the DOM elements in place while `item` is rewritten in the appropriate position as soon as `item`'s value changes.
`For` is considered the keyed list iteration and is recommended when `item` is an object where you render its properties.
`Index` is non-keyed list iteration which is an optimization when `item` is a primitive data type (string, number, bigint, boolean) because its faster to rewrite the relevant, corresponding string values into text nodes than moving the DOM elements around.
Such versatile videos! Can not wait to see what you are showing next
Solid intro to Solid ;) Not much of a game changer if you are using Svelte.
I have a couple of videos on Svelte as well. Between the two of them, I must admit I like Solid more - probably because of my React background.
@@awesome-coding Can Solid have children component inheriting from parent components? child using a parent method?
@@SebastianSastre Hey! Yes - the component hierarchy and data exchange follows the same patterns React does. So you can pass from the parent component to the child component state and behaviour (methods) as properties.
@@awesome-coding I've used react since it's first release and for me svelte is a game changer,it's remove all cognitive complexity of react, animations are simple, store global state is intuitive and that is something that after develop in react we forget, how react has became unintuitive for new developers and how many concepts they need to learn in order to use it and I'm not going to even mention redux...but I can understand that this depend of tastes and habits...solid looks great too
Awesome breakdown of this Awesome tool
Thank you! I am glad you liked it!
What should I know before picking up this framework?
Hey! You should probably have some algorithms knowledge (this is a prerequisite for anything coding related). Then some experience with JS and HTML would help. The advantage of Solid is that it's a fairly small library, and they have great documentation. They are linking to some good reactivity articles as well, which is important to understand since it is the concept that ties everything together.
@@awesome-coding oh then I’m set!
Thank you for sharing!
Ok, you showed that it is somehow different snd somehow dimilar. But what problems that it solve? Is it another member of new wave hype driven development? Or maybe it solves issues which other frameworks csnnot solve?
Hey!
I don't think it solves anything new but it is:
1. Smaller than the majority of existing frameworks;
2. Faster than the majority of existing frameworks;
3. A clear improvement over the most popular framework at the moment (React);
So the way I see it - A car is a car. It'll take you from point A to point B. But driving the 2022 full option model is way better than a 10 year old second hand car.
Is this something that I can use to create an app using a native web components library? Most components will come from that library. So, I need mostly binding, router, state management, and change management (reactivity) for the most part.
Hey! I don't have enough experience with Solid's web components results to give you an informed response. I successfully used Stencil (stenciljs.com/) in the past for such things though.
Solid works well with web components, it was initially designed to be a web component framework which is why it doesn't have runtime components. Also Solid is a state management / reactivity library first, you don't have to use it for rendering.
That's some FireShip level content ❤
This means a lot - Fireship is a major inspiration for me :)
Thanks for the kind words!
@@awesome-coding ❤
I'm going to have to check this video again maybe Monday, but... I need to ask now... can beginners quickly create video games for Android through Solid JS and if so... please show us how.
Hey, I doubt Solid is what you are looking for if you are interested in creating video games. You should probably take a look at Unity.
Creating games for Android is a hard place to start for beginners, although i would first look into Android SDK and app development and learn Java or Kotlin.
If you're set on making games I would definitely look into Unity, Godot and Unity.
But do know that you're not going to create your dream game right away, learn programming and software engineering first. I recommend using python or JS, then C#.
@@jonasls Long ago... years before AndroidOS had hit the market... I had created about 20 games on my own for the Nokia Smartphones and earned really good money from those which... funny enough... was because of PyS60... a SymbianOS smartphone version of Python super easy to learn... and processes just fast enough. Had spent about 8 years altogether trying to program in Java... JavaScript... and all the C variants, except C#... whereas those kept giving me far too much of a headache, meanwhile... I really enjoyed Python right from the start. Lately... I've been hearing a few people tell me that they made awesome games for Android with just HTML5 alone. Not everybody is focused on creating only AAA games, but... thanks anyway.
We can install Redux (Toolkit) or MobX to deal with state on solid JS?
From what was covered here I understand that store is integrated in this framework
@PaulKHeld is right. I find Solid's native store support powerful enough to handle all use cases. Remember that even Facebook came up with Recoil - a very light weight state manager which removes some of the clutter you'd find in Redux. They are also pushing the idea that the Context API can replace a 3rd party state manager most of the time. So, in my opinion, the general new direction is to handle state management without the need for 3rd party support, or with very light weight libraries.
Nothing which has a js in name is a game changer.
That's why Qwik doesn't have JS in it ;)
Screaming Yes, in nodejs...
😅
php dev triggered
What is the alternative? Building slower websites with wasm? Building websites with Flutter Web, a technology that can't even get scrollbars right and is also very slow?
so its vying for javascript's 4th ui spot with React/Next, Angular, and Vue...Solidjs is up against Remix, Svelte, Aurelia, and Hydrogen
Hey!
This is an interesting perspective. The way I see it is that SolidSJ is actually only competing with Svelte.
Their approaches and results are visibly different compared to Angular, React and others - way smaller bundler sizes, x times faster performance, no virtual DOM, real reactivity. It feels to me like another generational change, just like when we got away from Angular 1 and Backbone.
PS: I am excluding ANgular form this. They have their own market and niche they are addressing, I doubt anything will change in that enterprise environment.
@@awesome-coding Svelte is probably Solid's primary competition because people think that they are similar. Vue is faster in the js framework benchmark right now than Svelte and will become even faster without a V-DOM. Also Vue's reactivity is almost the same as Solid's, traditional pull based reactivity. Svelte is not necessarily what people usually call true reactivity, it kinda is reactive cause it gives you an API that looks similar to Solid and Vue but it compiles to reactivity that is more similar to React.
How does it compare to vue 3?
Hey! Most of my Vue experience is based on version 2. I can't make a fair comparison since I'm not familiar with some of the new things Vue 3 is offering. However, I think that Solid has a smaller API, and overall less code is needed to reach the same results.
Solid and Vue are very similar in their core reactivity. The templating is obviously different, also Vue has a V-DOM and is generally a bit slower. They also have different learning curves, Vue tries to be simple to begin with but overall is a bit more complex than Solid, Solid tries to have little overall complexity and minimal API and the idea is that you don't have to learn a lot of things to master the framework and even understand how it works. Also there are some differences in philosophy, Solid's philosophy is more similar to React's, and it supports concurrent rendering and time slicing.
Pace was a little fast but content and sequence was great.
Thank you!
I created a frontend for my social network, in nextJS, I am thinking to redo it is Solid now.
.. but I don't like type script.
You don't need TS to use Solid.
You don't need it, but you should probably use it! 😅
Planning to build mobile apps with solidjs and capacitor
I'm your 1,000th subscriber.
Haha! Thanks!
I'm going to stick with Vanilla just to piss every body else off
Good intro to solid JS
Thanks!
Thanx for Solid intro, interesting, but, honestly, real game changer is Flutter with Dart. One langwidge and one framework to rule Android, iOs, Win & Web. I lazy and I like it :)
I looked at Dart a few years back but it didn't feel smooth and mature enough. Did things change in the meantime?
@@awesome-coding for sure, last version mature and fils solid. I cant spend a lot of time on it, but have zero problem at Hello World.
Thank you for the suggestion! I'll give it another look.
I don't know how good flutter is for native but for web (websites not web games) it's one of the worst technologies you can pick if you care at all about quality. Also you can do native with Solid.
@@orenelbaum1487 as developer I completely agree (also it's so stupid - G develop Chrome with all of web thing's, but here they said "oh crap, just get canvas and WebAssembly"). On the other hand - it works, and business may have one command for any kind of task and save money. I see it's our future. Not shiny, but acceptable.
Solidjs is react but good
Sums it up pretty well :)
Nice. You should try VueJs 3 too as its pretty easy to learn and adapt.
Thanks for the tip! I have some experience with Vue 1 and 2, but never got the chance to check out V3. I only heard good things about it.
@@awesome-coding Ohh you will switch to Vue 3 for sure after finding how more simplified, faster development and clean it is.
@@Jewelsonn Will definitely give it a try, maybe I'll get a video out of it 😅 Thanks again!
How many frameworks do I need to know before I can call myself a Javascript developer?
42 🌈
@@awesome-coding 69
@@awesome-coding Totally works as the question and the answer. (To life, the universe and everything)
I’m glad somebody got that reference!
I sincerely hope this will gain mass adoption or maybe Facebook acquired the team and SolidJS can be rebrand to next version of React (ala Angular 2)
Haha that's an interesting idea.
We want unified configuration, Not another js framework.
Hey! I think that once you make a decision about a framework, that echosystem is pretty much complete. Think of React where you have tons of libraries to cover any needs, you have Next.js to bring it all together, and seamless deployments with Vercel. Not to mention Vercel offers edge functions now.
The benefit of new libraries and pioneering work in the space, in my opinion, is that it pushes everybody to do better. You don't have to switch every time a new framework comes out, but by studying it, it helps you understand what's possible, and what can be improved in your workflow.
@@awesome-coding
I was jokingly mentioning the 3 different configuration files for one project.
As a Full stack dev what hurts me the most is configuration mess and setting up environments.
The progress is there, I wouldn't call it "Pioneering" - There's nothing new about high performance HTML renderers.
It doesn't add any new concept, just reuses concepts in a new implementation.
I don't say it's bad, but I want to point out the complexities of simply rendering html and making an interactive application.
We need more unification alongside complicated tool chains. (Here I recognize Node+Typescript+React+Vite+Scss).
As a developer I find it really interesting (Good video btw) but at the same time I want simpler technologies and that's why we work so hard to give people simple efficient systems.
I completely agree it's weird to jump through so many hoops with configuration. I was doing React pre CreateReactApp, and I remember what a nightmare that was. Maybe that's why now, as long as the config files are there but I don't really need to worry about them, I'm completely fine :))
fireship enjoyer
That I am! :)
👍
come on people! it's time to throw react into the garbage!!!!! as a programmer, you don't want to suffer based on these techs!!!!!!!
Solid to the moon let's goo!
bgm song name?
th-cam.com/video/pTOVmsPJIBY/w-d-xo.html - Caballero - Ofshane from the YT free library.
no,no
Mr. Superman no home
Qwik?
Never looked at it. Would you recommend it?
@@awesome-coding not for any production applications yet. Fundamentally it's completely different from existing SSR frameworks.
Instead of being built using rehydration fundamentals, they've implemented fine grained lazy loading using resumability
Very interesting. Thank you for your suggestion! I'll take a look on it, and maybe I can come up with another first impressions video for it.
The problem is that the Javascript game changes weekly maybe daily.
I'm so sick and tired.
I feel you. My take on it is that the changes are not that major, and it is pretty easy to stay up to date with the new stuff.
I've tried everything out there that claims to compete with React. Yet I find myself always back at React. I've yet to find anything that comes close to beating it, and the support is great. React is really very simple, so why try to simplify that even more? The only contender to React is Elm imho.
I agree with you to some extent. I also face the same issues when leaving the React ecosystem - I'm missing all the 3rd party support and the known flows. However, I can't deny the fact that some of these newer tools such as Solid, and Qwik more specifically, improved a lot of the performance and the dev experience.
The only issue right now is their small adoption, but if any of those will gain more traction and a larger ecosystem, I believe they'll become a real alternative to React.
Very interesting if you want to build components from scratch. So not for me thanks. Maybe within 5 years.
I think a couple of larger component libraries already started porting their work in Solid as well. They have routing, state management solutions, SSR and various utilities. Do you think it lacks some other core features?
@@awesome-coding yes something like primeng for Angular or primereact for react.
There are component libraries for Solid. The ecosystem is not nearly as big as React or Angular but it's not like there isn't an ecosystem. For the most part it will have most of the things you need and the one big thing that is still not 100% ready is the SSR solution Solid Start but it should become stable soon.
@@orenelbaum1487 I was talking about UI components like a breadcrumb, a menu component, form elements, a table component, a carousel etc.
@@paulholsters7932 yeah I was talking about ui components as well.
it seems to me that it opens another hell gate TT
:)) Why do you think that?
@@awesome-coding no issue with your nice video as well as solid.js. I just got tired of frameworks
I'll use Svelte then. I hate typescript. It is like putting handcuffs on JavaScript.
typescript is not necessary in solid, you can use javascript aswell. i have been writing solid with javascript for about a month now and i love it!
Yep! TypeScript is not a prerequisite.
Looks like a React-Copy.
It uses JSX, and follows the same hooks API, which are approaches pretty popular in the space these days. It takes what React has best to offer and builds on top of it.
@@awesome-coding a new copy of react then... Great
We don’t need more JS frameworks!
Out of curiosity - what framework are you using?
Oh god, not another one
Well...😅
meh. I mean it's nice and all but i just don't like JSX (coming from vue background). So I'll take svelte over it
JSX is definitely not for everyone. As a fun fact, I just found out today that the creator of Qwik is Misko Hevery, the guy who came up with both Angular JS and Angular. With all his Angular background he still decided to use JSX for Qwik which, to some extent, is a testimony that JSX is pretty neat.
@@awesome-coding there are two different ideologies.
One is embracing the mix of two different types of languages since there is a lot of coupling (html-js) and the other is separating markup from logic.
Since both are equally valid, there will always be people and frameworks to support them.
I like nuxt 3's approach where it supports both jsx and template style but svelte's absence of vdom and whatever client runtime on client has won me over
@@Yorgarazgreece I completely agree with you on the vdom aspect. With this new wave of frameworks it looks like we are going back to good old DOM updates. jQuery V4 will probably win all of us back :))
You can use Solid without JSX, it supports template literals and hyperscript syntax (what React JSX compiles to). Technically you can even integrate it with Svelte's and Vue's DSL. Also Other than the DSL and different philosophies Solid is way more similar to Vue than Svelte. Svelte is a bit more similar to React. Vue and Solid are already a bit like different versions of the same framework and with Vue Vapor they will be even more similar.
I use to think the same, coming from angular n Vue. But when I tried jsx, really liked it alot. Simpler and very flexible
I hope the show element is optional and you can just use ternary operator. They shouldn't support typescript because it's dumb.
The main benefit of using show is that you get the fallback property, which makes the entire clause more concise. You can also use the ternary, since it is JSX after all.
You can Solid without TypeScript. I added TS in because I find it useful in both smaller and larger projects.
@@awesome-coding ok
Good on you for making videos but you seem to be copying Fireship too much. Maybe try to be a bit more different?
Hey! Thanks for the feedback!
Indeed, Fireship is a major influence for me, mostly because I like this quick tight format. I'm still experimenting with all this - I guess I'll develop a more unique style with time.
Not compo-nents, com-po-nents
got it 😅
So it’s basically React + MobX
Hey! To some extent you could say that. However, the API is more straight forward and you have everything under one small (~8kb gziped) library which is way faster than react.
So basically JSX === React to you
🙄
STOP COPYING FIRESHIP. It's just sad that you can't think of creating your own original video's.
Hey! It’s not really my intention to copy Fireship, but I am mostly resonating with that fast paced style of his. I’m pretty new at this, and I’m still working my way through all of it. With time I hope I’ll be able to find my own style :)
@Tyrone may. Dude... calm down. This is great content delivered in a great way. There's a difference between copying and being inspired by someone's approach. This is new and cool content delivered in a familiar style that works well. I like it.
Thank you so much for the kind words!
Solid good 👍 sass bad 👎
what do you prefer instead of sass?
toomany js
I agree. We need to keep up with the space though.
Vuejs > react
People that use react praise solid and svelte
It's debatable 😅
syntax looks ugly. svelte is still more cute
I guess you are not a JSX fan then? :))
Can you speak faster and less clearly please? Don't forget, zoom out more while rambling we don't need to see and understand the actual code you're typing.
Hey!
I'm working on the voice overs - I know things can be improved. :)
The video is fairly fast-paced because I'm trying to squeeze in as much information as possible in under 10 minutes. Clearly this is not the best format if you are interested to follow along with my coding.
I'm considering doing such videos as well, but they might be closer to 25-30 mins, and I don't know if they'll spark the same interest.
@@awesome-coding I appreciate the effort and I know it's not easy but I was kinda disappointed I wanted to learn something but I'm sure a lot of people did find it useful and got something from it. Best of luck!
Hey! I'll keep in mind your feedback. Will work on some more slow paced, detailed videos for certain. Thanks again!
Terrible, hardly to understand voice. Much too fast to follow. Bad quaility. A redesign is urgently needed.
Thanks for the feedback! I'll work on improving things.
@@awesome-coding stay like you are, I much prefer fast video that covers all I need to know without spending 30mins on a vid
I'm in my toilet taking a shit rn and it's specifically because your video is < 10mins that I'm here
It's true that it's fast, but I can pause whenever I want if needed. But I'm an experienced dev (mainly with React) so maybe for begginers it's harder to follow
But the video itself is clean, good job
@@commecestbizarre Thanks for the feedback!
I know that me talking is not always that clear - hopefully it get better with time:))
Other than that I'm planning to stick with the fast phased format for certain.
You are completely right - the video is intended to give you a quick overview of what Solid has to offer, and it helps if you are to some extend an experienced developer.
Thanks again for the kind words!