Now, that's a solid introduction. Well done, Atila!
@AtilaDotIO
6 ай бұрын
Thaaaanks, Jesse!! I'm glad you liked it!! 🙌
@johnnyboghean2242
6 ай бұрын
Ideed! A truly impressive intro
@zedespook
9 күн бұрын
While I have nothing against Svelte, I always felt that I had too much free reign. On a larger scale, the solutions I created with the freedom created sub-optimal solutions, which had to be refactored later. Solid, in this sense, feels a lot more ergonomic. The declarative path that Solid has taken has not limited me from progress while also providing my projects with a lot more stability, less weird-looking code, and (of course) performance.
@zedespook
9 күн бұрын
On a side note, Svelte 5 will bring Runes to the table. I would like to see how the new Svelte would compare against SolidJS. Being in the SolidJS and Svelte camps has been the best part of my professional development career. Thanks, Solid, for making web development much easier and more ergonomic.
@daviddibiase4391
7 күн бұрын
@@zedespook Svelte 5 is definitely a huge improvement. As their Svelte 5 release post mentions under the hood it's basically Solid's FGR philosophy and of course signals. It'll ultimately come down to DSL preference. Either way it's great seeing Solid's direction and core philosophy being affirmed by others (Vue Vapor being another) willing to adopt it's ideas. 🙂
@kafelinux
5 ай бұрын
SolidJS best of the best reactive framework, simple to use, unmatch Performance, easy integrated with anothe web component like smarthtmlelement, ❤❤❤
@vicca4671
5 ай бұрын
Great intro to SolidJS. I'll try it for some personal projects and it seems good to push for it's usage at where I work as well.
@joelquiles5339
4 ай бұрын
Thinking out loud: I like that there is a "marker" to indicate when a variable points to a signal, which wraps a reactive value, in contrast with a plain js value. However, as a newcomer I don't particularly enjoy that this marker is a function call. I think I'll write a babel or plaintext parser to change this reactive-signal--parser ala clojure atoms, where unwrapping the signal value is done with @ instead. Then, I can count on count() being a proper function call (on another context; pun intended) and on @count in this context to mean the retrieval of the signal value. I can easily see when a signal in used upon glancing code, and what is meant to be a js function call.
@planesrift
3 ай бұрын
Looks like react without the nasty part.
@dangtu-work
5 ай бұрын
I would like to have more tutorial like this. Especially if it can go deep into explanation of the inside of each solidjs functions. Also, can the next, if possible, tutorial is about how to change a whole html component (add new, remove old, or replacing)?
@vasfvitor
6 ай бұрын
haha while this video was being release I was literally watching the old video and now I reloaded the tab and it's unlisted
@solid_js
6 ай бұрын
So sorry about that! The previous video had a technical error in it and YT doesn't let us change the content once it's uploaded 😞
@AtilaDotIO
6 ай бұрын
Haha, my bad... but it was for a good cause! It's now more accurate and better! 💪
@user-zg2nl3gh1o
4 ай бұрын
3:53 When you transform lines 7,8 into 14 ("createElement, innerText" into "") how does it know to update only innerText later on? Or is it creating element every time when signal changes?
@vjzb3
6 ай бұрын
I'm confused by the example at 1:35. The count should be incrementing by one every 2 seconds, while the multiplier should be incrementing by one every 3 seconds. Yet the logs that are being printed show seemingly random values for count and multiplier that do not abide by that logic. To focus on a specific example: The first two log outputs show "2 x 2 = 4" immediately followed by "8 x 2 = 16". So how and why is the value for count going from 2 to 8?
@vjzb3
6 ай бұрын
I set up this same example in the playground and it worked as expected, so unsure of why we're seeing this in the video
@AtilaDotIO
6 ай бұрын
Hey, @vjzb3 ! I'm the voice there! Thanks for the feedback. the timings may not have been exactly right in the footage because of some cuts and how the playground auto-compiles the code. The logic in the example is correct to the best of my knowledge and I think the start time of each interval is just not synchronized in that case. It's hard to tell because between the playground refreshing and the little cuts I may have done (memory escapes me), it may have gotten a little off.
@asadhshujau1192
5 ай бұрын
what's the font used in HOW IT WORKS part
@Illumynatii
2 ай бұрын
I was wondering this exact same thing
@amcsoftware
Ай бұрын
Seems "Victor Mono", you can find it in Google Fonts
@yapayzeka
5 ай бұрын
this like svelte and react's child but only got the best genes from them. long live the new king.
@pierre-lucgingras4130
5 ай бұрын
Actually svelte 5 upcoming runes seem to make Svelte the child of react and solid. 😊
@yapayzeka
5 ай бұрын
let's say daddy got some behaviours from child :D @@pierre-lucgingras4130
@markokraljevic1590
4 ай бұрын
fix indentation in your code examples for readability
@vjzb3
6 ай бұрын
There is also a clicking in the audio that happens roughly every second from 2:15 - 3:58 and it makes it difficult to watch the content
@bvx89
5 ай бұрын
You mean the background music...?
@kaibe5241
13 күн бұрын
Looks just as awful as React...
@daviddibiase4391
12 күн бұрын
It may not be your cuppa tea but it's good. I promise. ;-)
@kaibe5241
12 күн бұрын
@@daviddibiase4391 Na, too much boot-strapping, lot of code having to be done just to get it to behave properly, when you have other frameworks that do all that automatically for you.
Пікірлер: 30