From dcfb172704f3afb68a30425029ec834be2883274 Mon Sep 17 00:00:00 2001 From: bt Date: Sat, 8 Jun 2024 13:22:19 -0400 Subject: More content porting, on-going markdown changes for lowdown support --- build/still-using-jquery/index.html | 41 ++++++++++++++++++++++++------------- 1 file changed, 27 insertions(+), 14 deletions(-) (limited to 'build/still-using-jquery') diff --git a/build/still-using-jquery/index.html b/build/still-using-jquery/index.html index f6db3e5..c801c47 100644 --- a/build/still-using-jquery/index.html +++ b/build/still-using-jquery/index.html @@ -1,41 +1,54 @@ - + Yes, I Still Use jQuery - - + + +
-

Yes, I Still Use jQuery

+

Yes, I Still Use jQuery

+

2019-04-15

+

I have seen a handful of condescending comments from front-end developers since the newest build of jQuery (3.4.0) released a couple of days ago. While I understand not all developers share the same work-style or are using the same tech-stack, dismissive comments towards any useful library comes off as entitled or elitist.

+ -

I still use jQuery. Well, I may not use the library for all projects since every project is different - but I certainly don't avoid using it solely because "its jQuery". I've always believed in using the best tools for the job.

-

Use what works for you

+ +

I still use jQuery. Well, I may not use the library for all projects since every project is different - but I certainly don’t avoid using it solely because “its jQuery”. I’ve always believed in using the best tools for the job.

+ +

Use what works for you

+

If you produce better work in a shorter amount of time using one of the latest and greatest technologies (React, Vue.js, Angular, etc.) then you should absolutely do so. If another developer can be just as productive building their projects with jQuery, what does it matter in the grand scheme of things?

-

My thought-process is this: a large percentage of web projects are done for clients not involved in the day-to-day happenings of the developer world. What they want is a solution to a particular problem. Clients don't care how things are done behind the scenes - so long as it is done efficiently and properly.

+ +

My thought-process is this: a large percentage of web projects are done for clients not involved in the day-to-day happenings of the developer world. What they want is a solution to a particular problem. Clients don’t care how things are done behind the scenes - so long as it is done efficiently and properly.

+

I tend to follow these principles when working on a project (with shared equal importance):

+ -

As long as all of these items are accomplished, I don't care if the project was a direct export from Microsoft Word straight to the web1. If it works great, then it works great.

-

So use whatever tools make you a happier developer, as long as your projects don't suffer because of them.

-

1This would obviously be terrible for development, but its just an extreme example

+ +

As long as all of these items are accomplished, I don’t care if the project was a direct export from Microsoft Word straight to the web1. If it works great, then it works great.

+ +

So use whatever tools make you a happier developer, as long as your projects don’t suffer because of them.

+ +

1This would obviously be terrible for development, but its just an extreme example