r/ProgrammerHumor 2d ago

Meme ancientTools

Post image
5.8k Upvotes

387 comments sorted by

View all comments

Show parent comments

959

u/Shadowfablie 2d ago

No useEffect infinite loops, no state management crisis, no build step. Just $('#rock').smash() and pure vibes.

96

u/ExtraWorldliness6916 2d ago

In my day veibes didn't exist

50

u/DrBojengles 2d ago

You WERE the vibes

24

u/mankeyless 2d ago

Back when the vibes were the friends you made along the way.

1

u/raja-anbazhagan 1d ago

I only made Jira tickets...

8

u/NeinJuanJuan 2d ago

We were vectors

23

u/Samurai_Mac1 2d ago

Yeah. Although I don't miss having to implement my own state management in every single project.

2

u/renevaessen 2d ago

I wonder if you mean it.

1

u/ShadowfaxSTF 2d ago

Don’t believe him, writing our own state management in every single project is what gets us webdevs up in the morning.

There is actually nothing more pleasurable in web development than setting up Redux actions and reducers then wiring it into the UI.

You wouldn’t believe how hard we get every time we write yet another useDispatch implementation, preferably with async thunks and memoized selectors, then have to write tons of mock structures to make unit testing possible. It’s like pissing blood during a prostate exam, you grow to love it after enough times. Definitely.

1

u/renevaessen 2d ago

Switching from ReactJs to true native WebComponents.. Who knew for great statemanagement you can just use well proven enterprise oo patterns that I learned a long time ago when creating software was still fun.

6

u/Hottage 2d ago

Unique ID on the rock.

That is the rock.

4

u/i_wear_green_pants 2d ago

useEffect is the dumbest thing ever. God damn it causes a lot of problems...

1

u/Shadowfablie 11h ago

i agree 100 percent!

-20

u/[deleted] 2d ago

[removed] — view removed comment

80

u/grimonce 2d ago

This has never been an issue with jQuery lol

19

u/uniqueusername649 2d ago

He means the script is loaded and run before the DOM was rendered. Bit of a stretch calling that hydration, because you usually only would call it that if the HTML was prepared via SSR or SSG, not if its a fully static HTML from the start. And even if it would be applicable, its not about the rock not having been hydrated yet but it not having rendered yet, so the "hydration" fails because of it.

28

u/brqdev 2d ago

We use onload/ready event and put JQuery code inside, so the JQuery code will run when the page is ready

15

u/WHALE_PHYSICIST 2d ago

Kinda crazy to be talking about jQuery in 2026 and not know that

12

u/brqdev 2d ago

Cause they know framework not Javascript itself.

3

u/--TYGER-- 2d ago

I expect that the people coding against a Typescript web framework have less knowledge / no knowledge of how a browser actually runs a web page. Instead, they have spent their time gaining knowledge about the build systems and such that turn ts into js for the browser.

2

u/uniqueusername649 2d ago

Agree. I know that stuff because I started learning web development in the 90s and have seen many changes come and go (most people would remember marquee on almost every website back then - less people might remember XML+XSLT to create websites, which was never fully supported). If I learned web development in the last 10 years, I doubt I would know how the execution works in the browser and all the annoying quirks that come with it. They are fortunately abstracted away. Even back then nobody wanted to deal with it, we just had no choice. Everyone built their own libs to deal with it, until jQuery emerged. That was such a massive step forward.

9

u/heytheretaylor 2d ago

Exactly. jQuery is cool like that. Just waits patiently for everyone to say they’re ready before doing anything.

6

u/yousirnaime 2d ago

Are ya ready, kids!

Aye aye, captain

3

u/theStaircaseProject 2d ago

Oooooh, who lives in a reference inside the <head>?

Ja-Va-Script Tag!

2

u/uniqueusername649 2d ago

Who loads our scripts long before we're rea-dy?

Ja-va-script tag!

5

u/SolideMeinung 2d ago

The funny thing is that these "real js developers" dont even know how to make that onload function on their own.

It war crafted by these old jquery wizards to always work and this knowledge was lost with the introduction of crapjs

1

u/ExtraWorldliness6916 2d ago

It's not lost, .onload or event listener. Of which there are 3 events and some are not "ready"

2

u/SolideMeinung 2d ago

Nope its not just onload or eventlisteners. The ready function of jquery has some corner cases.

Like the first and best one.... when everything is already loaded and ready just fire it.

A lot of people do miss that. Its funny how js developer have so much trouble reimplementing the jquery ready method because they think its easy.

1

u/ExtraWorldliness6916 2d ago

I was referring to DOMContentLoaded. O I was a bit cryptic but I mean that there are multiple ways to match the lifecycle. Still I'm probably, it was a long time ago

1

u/SolideMeinung 2d ago

Even DOMContentLoaded is not a drop in replacement.

→ More replies (0)

2

u/ExtraWorldliness6916 2d ago

Late jQuery at the advant of react we started talking about SSR but it was too late by then, I used to use cherio the server side jQuery quite a bit for "hydration"

9

u/sixtyhurtz 2d ago

Hydration errors are an entirely new class of bugs that occur when you are using JS to render on the server side. They didn't exist before React SSR.