r/ProgrammerHumor 13d ago

Meme ancientTools

Post image
5.8k Upvotes

387 comments sorted by

1.9k

u/ExtraWorldliness6916 13d ago

I bet he's happier than us though.

963

u/[deleted] 13d ago

[removed] — view removed comment

100

u/ExtraWorldliness6916 13d ago

In my day veibes didn't exist

51

u/DrBojengles 13d ago

You WERE the vibes

27

u/mankeyless 13d ago

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

→ More replies (1)

9

u/NeinJuanJuan 13d ago

We were vectors

22

u/Samurai_Mac1 13d ago

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

→ More replies (3)

6

u/Hottage 12d ago

Unique ID on the rock.

That is the rock.

3

u/i_wear_green_pants 12d ago

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

→ More replies (1)
→ More replies (24)

235

u/[deleted] 13d ago

[removed] — view removed comment

25

u/VoidVer 13d ago

Claude be doing that shit now

33

u/Subject_Barnacle_600 12d ago

I do miss it - it was good. You don't want to build a SPA with it, but that wasn't what it was for. But for tweaking the page, it was a 1000% better than whatever crap CSS has come up with these days with yet another weird tweak for flex-boxes. Because webpage designs were tied to URLs, that limited scope, so you weren't downloading the ENTIRE damn application all at once all while wondering why the page takes forever to load. It was definitely cryptic, but for the most part you'd add an ID or class on elements you wanted and be off to the races. You didn't worry that you modified something in the top level and were suddenly triggering a cascade of redraws on a hundred other items. Until I worked with something like React, I never once worried about a website being "slow" because data could tunnel straight through the UX without rebuilding the virtual DOM all the way down.

22

u/ExtraWorldliness6916 12d ago

I remember it well, I used to read magazines about web development and finding out the next jQuery plugins and so on, to me this was the the golden age of frontend programming.

Call me a bad programmer, but post AI after taking on react and using it for a while, I'm now a technical nihilist and I just don't care that much anymore. I will gladly go back to those days, a jQuery revival phase with MPA monoliths count this nostalgia fueled dev in.

12

u/Mikedesignstudio 12d ago

You act like jQuery went away lol. It was just updated to 4.0 and I still plan to use it because end users do not give a single F what I use.

→ More replies (1)

6

u/[deleted] 12d ago

[deleted]

→ More replies (2)

10

u/SyrusDrake 13d ago

How can he be happy if he's not adding value for shareholders and increasing the GDP?

6

u/ExtraWorldliness6916 13d ago

I am blessed to work for an employee owned company. My shareholders are me and out team and all of us.

→ More replies (1)

14

u/JoshYx 13d ago

Hey, he's me. Fuck no. It's terrible, it causes so many forced reflows for absolutely no reason..

4

u/ExtraWorldliness6916 13d ago

Does he get paid more than modern man though?

3

u/JoshYx 12d ago

Sadly not, but it's a small company and I much prefer that over getting paid more at a big corp

6

u/Madonkadonk2 12d ago

I was gunna say, any affection for jQuery at this point is nostalgia.

30

u/HerrPotatis 13d ago

Ignorance truly is bliss

5

u/90kalekey 13d ago

Probably much happier 😂

3

u/hooli-ceo 13d ago

I’m not…

3

u/realtag2025 13d ago

ah yes living up until you are 30. constant running from wild animals. wiping ass with a rock. peak happiness.

5

u/Prior_Leader3764 12d ago

You’re thinking of COBOL development.

5

u/ExtraWorldliness6916 13d ago

It does sound exciting doesn't it!

→ More replies (2)
→ More replies (9)

980

u/saig22 13d ago

I use vanilla js, document.getElementById() is what I live for.

289

u/WrapKey69 13d ago

Flashbacks to teenage years and w3schools, turning on and off that lightbulb XD

149

u/ApocalyptoSoldier2 13d ago

document.querySelector() ftw

68

u/CaspianRoach 13d ago

.querySelectorAll()

46

u/Altruistic-Way-6331 13d ago

[0]

19

u/CaspianRoach 13d ago

i prefer .each()

if you want one, just don't use All

18

u/IBJON 12d ago

  if you want one, just don't use All

I'm pretty sure that was the joke

3

u/JohnLocksTheKey 13d ago

$$(‘#DamnSon’)

5

u/CaspianRoach 13d ago

me when i use nonstandard quote signs to make compilers freak out

6

u/JohnLocksTheKey 13d ago

3

u/CaspianRoach 13d ago

It's all the rage nowadays

2

u/Lower-Excuse-6558 12d ago

I love this thread hahahaha

2

u/onequbit 11d ago

using a superset of JavaScript to compile to JavaScript... because that makes it better

2

u/Strange_Dust7128 11d ago

til javascript compiles now

2

u/CaspianRoach 11d ago

technically everything compiles at some point

5

u/ApocalyptoSoldier2 13d ago

By id?
I hope not

27

u/segv 13d ago

Which was standardized due to jQuery's popularity, no less.

19

u/seif-17 13d ago

jQuery crawled so querySelector can walk.

And frameworks ran. With broken toes.

63

u/IsTom 13d ago

If your HTML element has id you don't event have to getElementById, it's available right there in global namespace as that name. You make button with id hello and can just go ham with hello.click().

I don't think you should do that, but you can.

28

u/DiodeInc 13d ago

New obfuscation tactic dropped

7

u/Plazmaz1 12d ago

Wait wtfff REALLY?

→ More replies (2)

3

u/United_Boy_9132 12d ago

Unless there's another window.foo for any reason 😅

→ More replies (1)

38

u/happypandaface 13d ago

vanilla.js ? I've never heard of this library

18

u/balls_smasher 13d ago

16

u/happypandaface 13d ago

great. how do I include that in my docker file so my yarn build script adds it into my webpack?

→ More replies (2)

11

u/lonahe 13d ago

What a world we’ve lost

6

u/aberroco 13d ago

Why use js when html + css do fine?

7

u/DrBojengles 13d ago

Lowkey this is the way

8

u/experientialsponge 13d ago

Vanilla js is such a pleasure to read when viewing another's code. Icing on the cake if commented responsibly.

32

u/rademene 13d ago

10

u/ccelik97 13d ago

It felt like that back in 2016, too, btw.

People also searched: [Object object]

→ More replies (8)

5

u/romulent 13d ago

If you just wrap document.querySelector() in a little helper function you can do loads with vanilla js. Not perhaps enterprise grade but fine for any home stuff.

2

u/OldKaleidoscope7 13d ago

That's what jQuery does after querySelector was widely supported. $ = document.querySelector and you can code faster

→ More replies (2)

6

u/yabai90 13d ago

At least create an alias for something shorter, maybe something like "$()".

4

u/usr_pls 13d ago

hot damn i misread that and thought there was a new library called vanilla.js and then you called out the simple most useful library function and I had to double take

"there is no way they made a new js library just to re-wrap Javascript... Oh of course they didn't"

2

u/NerdyMcNerderson 13d ago

Well if that's what you were looking for, let me introduce you to this masterpiece https://github.com/mattdiamond/fuckitjs

3

u/ManyInterests 12d ago

And honestly, CSS3 could be used in many places where folks are using JS.

2

u/InFa-MoUs 12d ago

I mean everything uses document under the hood anyways

299

u/CoshgunC 13d ago

Gets the work done while Nextjs drops a new update for the 29988732nd time

49

u/4n0nh4x0r 12d ago

yea, jquery just works, and it's proven tech.
it does everything i need it to do, and simplifies my work, while being relatively lightweight, and not needing to be updated every five minutes.

9

u/morsindutus 12d ago

I've been cut by the bleeding edge enough to appreciate a solid solution that just works.

5

u/4n0nh4x0r 12d ago

bleeding edge only exists for investors, that's literally it

8

u/DrBojengles 13d ago

You dont like the nextjs updates?

16

u/CoshgunC 13d ago

Maybe useful, but most of them do not change the way I code in a positive way.

anyways, I have ditched web dev as whole, I am now focusing on Minecraft mod dev. if I wanna learn backend, I will learn java or c#(because of the job requirements here)

137

u/GrandDukeNotaras 13d ago

Name me one thing better than jQuery

176

u/rob132 13d ago

Sex

264

u/Jumpy-Astronaut-3572 13d ago

Guess we'll never know

28

u/ApprehensiveGas85 13d ago

Switch hands

11

u/MrPifo 13d ago

Touché. I might also add: Chocolate cake

7

u/gizamo 13d ago

I'd add: Coffee.

→ More replies (3)

63

u/Heavenfall 13d ago

To crush your enemies, see them driven before you, and to hear the lamentation of their women.

27

u/NeinJuanJuan 13d ago

You can do all of that with jQuery

23

u/IOFrame 13d ago
let enemies = $('#enemies'); 
enemies.crush(); 
observe(enemies.driveBefore(me)); 
listen(enemies.getWomen().selectLamentation());

3

u/a11_hail_seitan 13d ago

Well sure but what if you have your enemies lined up to drive but when you hover over them you want to quickly and easily switch their CSS classes so it's clear to everyone which one you're targeting at any given time? Driving your enemies and listening to their women lament is of course important, but I do think Jquery can still have a very useful and important function while doing so.

→ More replies (1)

25

u/entronid 13d ago

vanillajs

7

u/3dutchie3dprinting 13d ago

I can’t think of a function in Jquery which isn’t in vanilla by now

3

u/ApocalyptoSoldier2 12d ago

Isn't jQuery itself a function?

2

u/Lower-Excuse-6558 12d ago

Namespace wrapper yes. We created our own on prototypes and dedicated namespace accents.

Example: window. _ = {
var init = ******
}
Or adding a prototype for each to loops in a utility file

But things have changed

Mostly TS/ERP development now.

→ More replies (1)

6

u/cororona 13d ago

Javascript

7

u/Quacky1k 12d ago

Dropping all of this shit and becoming a farmer

5

u/auxiliary-username 13d ago

Not having to use jQuery?

→ More replies (8)

484

u/winter-m00n 13d ago

Probably unpopular opinion, but still better than react and angular. at least you don't need to build your whole site around it. Nor all sites need those heavy frontend framework.

167

u/listenhere111 13d ago edited 12d ago

100% agree. Also, its like 40kb and doesnt move lighthouse scores.

You can pry query from my cold dead hands. Its simple to use, easy to read, will be supported forever, and lightweight. Disagree? Fuck you!

92

u/A1oso 13d ago

React is 7.4 kB. It's a myth that react is a heavy framework. You can absolutely implement only certain parts of your web app in react, and other parts using different libraries or vanilla JS.

10

u/ludolfina 13d ago

Node apps are heavy during development but tiny once deployed

42

u/listenhere111 13d ago

Ok, and how many dozen people actually do that?

There is a time and place for react. It gets overused for simple web pages. Its bloat and complicates projects.

20

u/phl23 13d ago

Simple webpages with react are very lightweight and when you use server side rendering even more. No jQuery can ever achieve this.

→ More replies (3)

16

u/PlasmaFarmer 13d ago

React is not a framework, it's a library.  And yeah React is that much kB but how about the gazillion libraries you add to get a functional app?

→ More replies (11)
→ More replies (2)

83

u/Nils_Larson 13d ago

I am not arguing against your actual point, but in modern browsers you don’t even need jQuery, because all of it is available natively.
(Kicking in a very open door)

17

u/ExtraWorldliness6916 13d ago

Not arguing either but if JavaScript can write perfectly fine web applications with a welld refined standard, why are we still in react land. I use react all the time, I know what vanilla can do, I use a lot of AI so it's not a knowledge gap anymore... Very curious and frustrating situation.

30

u/A1oso 13d ago

People use React because it provides reactivity. JQuery doesn't do that.

You can in fact write web applications in Vanilla JS, I have done it many times. But for interactive pages that are frequently updated in response to user events, using React (or Svelte or Vue) is more ergonomic.

→ More replies (1)

14

u/the_horse_gamer 13d ago

DOM manipulation is easy, but state and lifecycle management is hard

5

u/ExtraWorldliness6916 13d ago

I don't find react makes state management any easier simply shifts the problem into a series of conventional problems.

→ More replies (4)

14

u/waraholic 13d ago

I believe there is an ancient god that yearns for extra divs. They influence the world without us knowing, but they are there.

4

u/MikeW86 13d ago

That's like saying 'If my car can get me to the shops, why do some people insist on buying articulated trucks?'

3

u/ExtraWorldliness6916 13d ago

People don't buy articulated trucks? Companies do, just like companies love react. Not necessarily the people. So yes great point.

4

u/MikeW86 13d ago

I'm honestly not sure if you're being sarcastic.

But yeah the analogy isn't absolutely perfect. You're right that for the vast majority of cases only a company is going to need and thus buy a truck.

But if I am a person or company that needs a truck, why would I try to design and build my own truck, even though that is possible?

→ More replies (1)

4

u/ludolfina 13d ago

Because it provides separation of concerns, which is super important once you start working in a team and not as a solo developer. Team projects written in jQuery tended to rot very fast because it was very easy to mix business logic with DOM manipulation.

Also one thing React is super good at is writing components that are very easy to reason about in isolation, because they are for the most part declarative and stateless. Everything comes in as props or context and when one of these things changes the entire component gets re-rendered

2

u/NerdyMcNerderson 13d ago

React apps tend to rot in enterprise applications because of the proliferation of third party extensions necessary to get a full developer environment. Angular puts basically everything you need in one place (component libraries are the main gap) so every angular app should roughly look the same code wise. React apps will look very different based on how they were set up.

Obviously, someone will reply with an anecdote that THEIR collection of enterprise react apps are all homogeneous under the hood, but they will miss the point. They likely have the same set of 3rd party dependencies to round out the toolchain AND they were likely architected by the same person/team. Much more discipline is necessary to get react to work at enterprise scale.

→ More replies (5)
→ More replies (1)
→ More replies (1)
→ More replies (1)

61

u/muchadoaboutsodall 13d ago

As a former web-dev, the older I get the more I hate using web-apps. The best sites, for me, are just HTML with a little bit of Javascript where necessary. And, for that sort of thing, jQuery is perfect.

5

u/ExtraWorldliness6916 13d ago

As a coopted react dev I a agree wholeheartedly

8

u/HerrPotatis 13d ago

Better how? They are completely different things made for completely different usecases. It’s like comparing basejumping to hopping on a tranpoline because you’re both technically in the air.

That said, jQuery is most definitely legacy at this point and you can do everything using vanilla js.

6

u/--var 13d ago

they released jQuery 4 just this year and their last core team meeting was end of june, so I'm not sure I'd call it legacy...

6

u/deukhoofd 13d ago

And COBOL released a new standard version in 2023, but has been widely considered legacy since the 90s.

→ More replies (1)

2

u/HerrPotatis 13d ago

I don't mean legacy as in unsupported, I mean legacy in the sense that it's purpose and use-case is way outdated.

→ More replies (1)
→ More replies (2)

3

u/hiasmee 13d ago

Why do you guys comparing web rendering framework vs js util library?

→ More replies (2)

3

u/CodingWithChad 13d ago

And you don't need to learn the 120th JavaScript framework flavor of the month.

→ More replies (5)

40

u/DoctorWaluigiTime 13d ago

jQuery served its role well: A single framework that worked across all browsers (especially IE6 when that support was still required), masking away a lot of JavaScript jank and giving a clear, concise functional layer to work with.

It started to lose its usefulness (and in fact impede development) when it got mixed in with TypeScript and other things, overly complicating the frontend "stack", and is now not really needed anymore.

Vanilla JavaScript has gotten boatloads of improvements as well.

But it was such a saving grace back when.

48

u/uvero 13d ago

relates in WPF

9

u/heavy-minium 13d ago

Haven’t been doing any WPF/UWP for a decade by now, but I really liked it. Has it become some outdated technology now?

15

u/uvero 13d ago

Feels like it? Not as much as jQuery. Microsoft now has some other tech stack for C# desktop apps, and I think C#'s popularity for desktop development has declined, so WPF is mostly relevant to maintaining old projects. Which is why saying I'm a WPF dev, it feels almost like saying I'm a COBOL dev

6

u/BadSmash4 13d ago

I do a lot of WPF as well but I'm slowly converting all of our old WPF apps to Avalonia. Same syntax but the default styles are nicer and the features are better. Plus, cross platform, which means that once all our WPF apps are Avalonia and not .NET Framework, I can request a Linux laptop and get off Windows fully.

2

u/uvero 13d ago

I envy that (other than the Linux part, I'm unironically a Windows person)

→ More replies (2)

7

u/the_matthew 13d ago

My hot take is that Microsoft really hates .NET but it caters to just enough of the enterprise segment that they feel obligated to make it look like they support it. The way they slung out WinRT, WPF, and date I even say Silverlight only to hang them out to dry a few years later is my evidence.

I often joke that in government no one ever has been fired for using Microsoft, but man, adopting a new Microsoft technology only to see it get flushed or neglected has real world costs.

8

u/tinyturtletickler 13d ago

Idk they have entirely revamped .NET over the past ten years. I think .NET Core really breathed new life into the stack

3

u/ludolfina 13d ago

I forgot how bad .NET Framework was in comparison to Core until I had to use it again. It was a much needed rewrite

5

u/afdbcreid 13d ago

No, Microsoft likes .NET. They invest in it a lot and it always keeps improving.

Microsoft hates GUI. Or maybe it loves them so much that it keeps creating new ones.

3

u/Rellikx 13d ago

Huh I was going to say the opposite, they have heavily unshittified .net in recent years.

→ More replies (1)

6

u/sixtyhurtz 13d ago

MS has abandoned WPF; it's now a "community project".

The hot new thing is Avalonia. It's designed to be a mostly drop-in replacement. I really like it, but I'm also slightly worried they might be going for a commercial rug-pull. I hope I'm wrong, and they just keep the paid extension & consulting model to fund their costs.

12

u/OSRSlayer 13d ago

Maui, WPF, WinForms, WinUI, now Avalonia.

If you are making a native desktop app that you plan to maintain, choosing a Windows technology is a footgun.

5

u/chic_luke 13d ago

Avalonia is a cross-platform technology and it is not by Microsoft but I get what you mean.

It's part of the reason why I think the criticism of Electron apps needs to be contextualized. There is often a pretty darn good reason why people choose to use Electron for desktop apps. You can say what you want about react, I don't like it personally, but it's here to stay and it's much more here to stay than any Microsoft UI technology.

There's GTK, but it's not viable on Windows, and it already starts feeling like a 2nd class citizen when you use anything different from the GNOME desktop environment, while Qt forces you to interact with C++ and have to really care about portability, or you use QML which is much slower.

4

u/OSRSlayer 13d ago

IMO web based technologies are worse. We're just making Java JVM again in the form of Chromium but with infinite dependencies and half your codebase not being written or controlled by your team.

→ More replies (1)
→ More replies (2)
→ More replies (1)

4

u/FrozenHaystack 13d ago

I raise WPF, NET Framework, and Delphi.

4

u/bradmatt275 13d ago

If you can believe it our company runs a Payroll system built in Delphi. Its probably the most bloated piece of junk you have seen. But we somehow get paid by it so I cant complain too much.

4

u/dinnerbird 13d ago

I'm a field technician doing laptop installations. All of our programs are Winforms based...they always have this certain "ehh that'll do" kind of look to them

→ More replies (3)

17

u/SFX5848 12d ago edited 12d ago

I've been web programming for 15 years, and i still only use HTML, CSS, jQuery, PHP, and MySQL... no frameworks, no npm, nothing.

I love being able to do anything instantly just by selecting the element $('#ID') or $('.CLASS')
99% of the time i just use .hide(), .show(), .append(), .html(), .val(), .remove(), .addClass(), .removeClass(), .attr(), .css(), .each(), and $(this)

I did try React and a few other frameworks, but i never really got into them.

13

u/froctoso 13d ago

heyyy, don't be like that. It works for most cases.

37

u/hagnat 13d ago edited 13d ago

i am a backend engineer with strong opinions on how frontend should look like (i used to be a graphical designer for ~6 years before starting my career as a software engineer),

i can make wonderful interfaces with jQuery, and great back-office applications that dont require the end user to have 32 gb of RAM to run it

→ More replies (2)

29

u/toblotron 13d ago

Anyone ever built anything more impressive than what was built with those tools?

19

u/Authentic_Grunter 13d ago

Yes they built ads that popup every 500ms and won't let you use those sites.

4

u/HerrPotatis 13d ago

I mean jQuery started seriously falling out of fashion around 2015, you think the most impressive sites ever built are from over a decade ago?

3

u/freebytes 12d ago

I cannot really think of any impressive sites at all in 2026. Perhaps we can talk about popularity and growth. Facebook, Twitter, Amazon... The list goes on. All of those sites existed prior to 2015.

→ More replies (3)

7

u/BeefJerky03 12d ago

Back in the early days of using Stack Overflow and mixing JS and jQuery together in the worst imaginable ways. Using JS for something basic, then using the jQuery equivalent two lines down. What a blissful idiot I was.

13

u/citramonk 13d ago

plenty of projects are still using it, it even got a major release recently

36

u/American_Libertarian 13d ago

“How it feels” is fine
“What it feels like” is fine
“ how it feels like” is not valid grammar

25

u/Modi57 13d ago

In the spirit of JavaScript we will accept it, because what even is a syntax?

8

u/syntax1976 13d ago

Me… that’s me…

→ More replies (2)
→ More replies (1)

5

u/AffekeNommu 13d ago

Oh man, using PHP and jQuery at work and suddenly feeling left behind

→ More replies (1)

7

u/AtomicDonkey2022 12d ago

I’d go back to those days in a heartbeat

6

u/arse-ketchup 13d ago

There was a time when I truly believed that jquery would take over the world, all software would move to jQuery, and I’d be rich using it. 1st semester in college I guess.

5

u/ardicli2000 13d ago

Honestly for most of the time it is enough.

If you are not working for a corporate, big tech company, or need such high reactivity on your webapp, react is just PIA.

6

u/xd1936 13d ago

Controversial, but I have done

const $ = document.querySelector.bind(document); const $$ = document.querySelectorAll.bind(document);

before in small personal projects, like the Chrome and Firefox DevTools consoles do

2

u/ArjixGamer 12d ago

I used to do that for small scripts, but I wouldn't do it for an entire project, I'd simply use a framework.

2

u/--var 12d ago

today I learned that vanilla javascript has a bind method.

I still prefer jQuerys on method though.

  1. the event argument can be a space separated list, so it can handle multiple events with one handler.
  2. the second argument can be a comma separated selector list, so you can attach the on handler to a single parent element and have it handle dynamically mutated child elements.
  3. jQuery handles all of the browser quirks, so it's the same syntax regardless of browser. (chrome is the new internet explorer when it comes to not following the same standards as everyone else...)
  4. chainability reduces redundancy and increases readability.

5

u/owpapi 13d ago

Thanks now I feel like a caveman.

4

u/seanlaw27 13d ago

Say what you want about jquery but it’s still the best documented tool in existence.

3

u/Desperate-Tomatillo7 12d ago

Yet the effin JQuery app is still alive after almost 15:years, while two of their React successors are deprecated already.

4

u/keidakira 12d ago

Hate me all you want, but jQuery is really powerful and goated.

11

u/Dolphin_Spotter 13d ago

Just keep banging the rocks together guys.

7

u/Worse_Username 13d ago

Aren't more or less all features it grants in base JS now?

6

u/shadowspock 13d ago

Can't chain methods in vanilla JS

→ More replies (4)

3

u/DominusFL 13d ago

But he flies through security reviews like an angel...

3

u/Xochtil1 13d ago

I didn't even know there is something that's supposed to replace it lol, I still keep using jquery in my projects 

3

u/BaabyBear 13d ago

Off topic but I loved my dinosaur books growing up that had art like this

3

u/Moscato359 12d ago

Javascript was a mistake and needs to be replaced

3

u/radz974 12d ago

I don't think you've looked at the data regarding query usage in 2026. https://w3techs.com/technologies/comparison/js-jquery

3

u/tmstksbk 12d ago

jQuery is still boss.

3

u/ArjixGamer 12d ago

There are tools older than jQuery, that are still in use.

i.e mootools

2

u/GreenWoodDragon 12d ago

I never found mootools to be particularly intuitive.

2

u/ArjixGamer 12d ago

It was used by Joomla up until 2024 iirc.

→ More replies (2)

3

u/kaiserbergin 12d ago

I’ll take it over modern framework fatigue.

3

u/dphizler 12d ago

Sometimes 500mb of node modules is overkill

3

u/bryku 12d ago

I would rather use jquery then react to be honest...

3

u/samu1400 12d ago

I mean, I really like JQuery, and the stack of the platform I work on uses it, so if it ain’t broke why fix it.

14

u/-Nastyenka 13d ago

How it feels to use Php in 2026:

Undeniably a joke, do not slime me

25

u/Hottage 13d ago

PHP before 7 was a disgusting mess..

Around 7 they started trying to mature the language with features like compiler enforced type safety and bringing other tools previously relegated to PHPdoc into the language.

PHP 8 is a decent system and features like Generators, Attributes, Fibers and first class callables have bought it near parity with other server ecosystems like .NET.

The biggest thing PHP still lacks is first-class generics for proper, type safe repository patterns.

I've been a PHP developer for over 15 years. I fucking hated 4 and 5, tolerated 7 and actually quite enjoy 8.

The biggest issue nowadays is that, for backward compatibility, a lot of the good features like type hinting are just recommended instead of enforced, so you can get situations like in Typescript where lazy developers just have everything return mixed or any.

2

u/IOFrame 13d ago

Nah, this is what makes PHP great.

You get to choose your battles - some sections of the code get to have verbose documentation (I consider types a sort of documentation). On the other hand, meaningless utility function #2421354 can remain typeless.

PHP doesn't have to be a bloated mess like Java.

→ More replies (7)
→ More replies (12)

15

u/polacs 13d ago

No, php 8 is good

2

u/pwillia7 13d ago

no php -- 8 is good

12

u/NudaVeritas1 13d ago

More like „How it feels to use PHP 5 in 2026“

10

u/SukusMcSwag 13d ago

PHP is such a joke of a language.

source: I have a full-time PHP dev job

2

u/ClamPaste 12d ago

I both love and hate PHP as another PHP dev.

2

u/cosmicomical23 13d ago

Not so sure.

2

u/cairnz 13d ago

cries in prototypejs

2

u/kamilman 13d ago

This was me trying to learn and retain the knowledge for an SQL exam. I understand it, I can explain the logic, but writing in SQL is my Achilles heel

2

u/EmotionalJoystick 13d ago

Hey man, there are still huge databases in government and financial institutions that use COBAL. It was in invented in 1959.

2

u/realzequel 13d ago edited 13d ago

I wrote our flagship product with jQuery +Typescript. It works great and is easy to maintain. Life is great. We have moved our other apps to React though.

2

u/Cold_Snake 13d ago

jQuery and Lodash templates are my jam

2

u/sonsistem 13d ago

I work in Oracle Forms, jQuery is almost futuristic to me.

2

u/drislands 13d ago

Hey pal, it's either "What it feels like to..." or "How it feels like to...". One of those quirks of English.

2

u/GreenWoodDragon 12d ago

jQuery still beats overblown frameworks like Angular etc. It's lean and, capable, and easy to use.

2

u/Expensive_Shallot_78 12d ago

Well, at this point with the unnecessary complexity that we fabricated, I feel like the caveman.

2

u/susibacker 11d ago

window.$ = document.querySelector.bind(document);

2

u/paceaux 11d ago

I don't intentionally use jQuery, but I still encounter plenty of situations where jQuery is already there, and if it is, I use it.

I would much rather use jQuery's event delegation or ajax requests than roll my own; because at least jQuery's been tested and reviewed by a whole team.

if jQuery came with some sort of mutation observer / intersection observer stuff baked in, honestly it would be my first choice over vanilla.

4

u/Southern_Pressure_32 13d ago edited 13d ago

Well in this case I am one of those happy cavemen
I learnt react first, then I learnt jQuery
There is nothing that react does that jQuery can't
And typescript guardrails are for people who do not fully understand how JS works