You know that feeling when you meet an old friend you haven’t seen in years? You used to be so close but …
“Long time huh …”
“Yeah time flies … how’s the wife?”
“Girlfriend. She’s good, just started a new job …”
“Nice nice … you still at that startup?”
“Yeah … it’s okay … you?”
“Nah, new gig last year. Think I told you, dunno”
“Maybe you did, hard to keep track … liking it?”
A beer or two later and you’re back to being best buds. Suddenly it’s 1am and a long yawn reminds you that you’re not quite so young anymore.
That’s what messing around with jQuery felt like after all these years.
I was bored Monday night and decided to see if I still know how to build with jQuery. Nothing better to do, no pressing ideas, a bit of fun.
Also a favor for a friend who’s preparing to talk about React to a bunch of people who’ve never seen it before 😛
It’s funny, jQuery is so old now (2 years since new versions stopped coming) I feel like I almost have to introduce the darn thing. Used to be the backbone of the web, now it’s in the dustbin of history.
Pushed web development forward for its entire 10 year run. Oh the memories …
So, how does jQuery stack up to React and how does React stack up to Svelte? Let’s see 👇
Started with a React app. It’s what I’m most familiar with right now.
We built a cat app. Fetches 5 cats from thecatapi, shows first cat. Click a button, get more cats.
When app runs out of cats, it fetches more.
fetchCats returns a promise with a bunch of cats. Pagination works based on current count of cats we’ve got.
Rendering a list of cats happens in a
<Kitties /> component. ’tis but a loop
Take list of
count how many the user wants to see,
slice the array, render each cat as an image. 👌
Driving this logic with React Hooks isn’t bad. React’s ergonomics are getting real good.
useState for the count of cats, and a
useEffect to deal with fetching. Fetches on first load and makes sure to fetch more when
showCount is bigger than the current amount of cats.
React handles the rest.
No seriously, I struggled, tried a bunch of things, and ended up with a good old script tag and a public CDN.
People don’t do that in real life anymore. It’s all import this import that.
For the app itself we used a naive unoptimized approach much like many jQuery apps of old 👉 find div, empty div, render everything from scratch every time.
Notice the mess with creating a small component tree of
<div><img></div>? Painful. JSX improved this a lot. Almost can’t believe we used to build complex apps like this.
You can see it’s slow too.
Open the CodeSandbox, add a couple cats. You’ll see the more cats there are the slower the app gets.
Not so with React because React avoids re-rendering components that don’t change.
PS: check out this mess of attaching a button click handler and driving the cat fetching logic.
I like hooks.
The Svelte version wins in the immense straightforward simplicity of it all. I’m pretty blown away.
Check out the
<Kitty /> component
id and a
url, has some
style, and renders a div with an image. Pretty slick, looks almost like pure HTML.
Then you got the component that drives state and renders a bunch of kitties with a button.
The script looks similar to React Hooks. You got some variables with state and you got a
moreCats method that drives it.
Repeating that array merging logic twice is a little less elegant than the
useEffect hook, but probably easier to understand how it works 🤔
Rendering is neat too
Similar to React, but we used
.map. Still not sure how I feel about that but it’s pretty readable you gotta admit.
Between you and me I think React wins this one. Maybe it’s because I’m used to it.
What do you think?
Learned something new? Want to improve your skills?
Join over 10,000 engineers just like you already improving their skills!
Here's how it works 👇
PS: You should also follow me on twitter 👉 here.
It's where I go to shoot the shit about programming.