How did this got into my mind??
Virtual DOM can be referenced as the thing which just "introduced" me to the title of this post. What if...
For further actions, you may consider blocking this person and/or reporting abuse
And this is why we use compilers and templates on top of this. Challenging implementation to follow for a beginner, but I like the sentiment. I wouldn't worry about it being long. I wrote a similar article and it was a 17 min read with a precursor 15 min read. 5 mins feels breakneck speed for the subject matter. But I always love to see people writing and evangelizing the topic.
Link posted is 404 now, here's the new one angularindepth.com/posts/1289/soli...
Edit:
Ryan, thanks for this beautiful framework first and foremost, but please move the article to somewhere else. First the 301 redirect to their homepage (not even to posts index) and then there's no any information about the article; no author, no date and time, let alone the estimated reading time. IMHO your writings deserves better.
Edit 2:
I'm very well aware that it's been more than 3 years now, but still... the links are still active on some posts.
I think mine is a 5 min read because I haven't spoke much about the concepts revolving around all this. But I'm just starting out in writing posts, so it might take a while for me to improve :)
But virtual DOM has nothing to do with reactivity. Virtual DOM needed for declarative style programing - you don't need to manually change state of each element instead you return new JSX and VDOM will figure out what actually changed and apply the difference to the DOM
@stereobooster Actually, virtual DOM has different meanings that vary with context. So basically, I'm talking about the reconciliation that happens after there is some state change happening in the app. So I basically wanted to remove the extra reconciliation step and to keep states directly in sync. I hope you understand what I mean. So instead of returning a new element each time a state change is triggered, the existing element can be mutated; this will certainly avoid unnecessary logic and speed things up. If you have a good title for this post, please feel free to tell me :)
This is your article you can name it what you want (obviously). Alternatives: "You may not need Virtual DOM" 🤷♀️
I'm just saying that React is not reactive and Virtual DOM is not for reactivity it is to make declarative style (return of the whole JSX) possible.
Shawn Swyx Wang - Why React is not Reactive
Oh, now I get what you want to say, @stereobooster . But anyways, it was just an experiment :)
Hi Pranav,
Thanks for the article.
Could you have a look on meiosis.js.org/ ?
Regards
Hi @artydev , I liked the concept of meiosis.js. Nice one!
Nice😊
Look at this other exemple
dev.to/artydev/meiosis-a-simple-st...
nice from 6 year later, I built it with proper dx