JQuery has me frustrated sometimes

M

MisterBigglesworth

Expert Member
Joined
Aug 15, 2006
Messages
3,334
Reaction score
13
Location
/\\/¯¯¯\//\
JQuery is great, dont get me wrong...but it's also a pain in the ass! Lots of awesome scripts and goodies with JQuery...but I have run into an issue where Im using 2 JQuery scripts. One uses JQuery 1.3, the other JQuery 1.8

What sucks is you would assume just having reference to JQuery 1.8 is enough for both (as the script needing 1.3 should run just fine with a later version - so I left the reference to it out the code). Nope...not the case, getting Javascript errors. So then I add both in so there is reference to both JS files...nope, dont work...they clashing.

So now I have to go debug...so frustrating.

Just had to vent a bit... :whistle:
 
JQuery also poses a problem when you have clients that are still stuck in IE5.0 [ :wtf: ] .... need I say more? :D
 
froot said:
JQuery also poses a problem when you have clients that are still stuck in IE5.0 [ :wtf: ] .... need I say more? :D
Click to expand...

dafuq

And that's the unfortunate situation when you just copy someone elses addon for jquery that never upgrades. The only way is to not rely on addons that much and when you do choose one that fits your needs, to make sure it's an active project before going the live root.

however, it should be pretty simple for you to get it up and running without intervention from the original programmer. making stuff compatible with 1.8 is quite straightforward really.
 
people who use IE should banned from the internet and printouts of their add-on bars laminated to their foreheads.
 
The problem comes in when you're faced with clients who pay millions for your enterprise software and you're faced with the reality that 90% of the access would be via IE7 terminals that aren't upgradeable...
 
stricken said:
people who use IE should banned from the internet and printouts of their add-on bars laminated to their foreheads.
Click to expand...

"Designers" who don't know how to code for the most popular browsers should go back to client-server desktop work :)
 
jQuery is nice for IE6 and up as well as the other browsers. What ****s my mind is the different interpretations of CSS/HTML5 RFC's

Corporates usually stick with IE if they're running Windows. It's also easy to manage through Active Directory etc. So I don't care, I always write my **** with compatibility between all major browsers except Safari. Safari can go fly a kite, not installing that on my PC ;)
 
When you develop something, keep the user in mind - like what their company policy is, what they have, and what they most comfortable using. Shoving FF or Chrome down their throats will not get you another project.

I use Chrome 99.99% of the time, but the clients (users) use IE 99.99% of the time.
 
Fuma said:
When you develop something, keep the user in mind - like what their company policy is, what they have, and what they most comfortable using. Shoving FF or Chrome down their throats will not get you another project.

I use Chrome 99.99% of the time, but the clients (users) use IE 99.99% of the time.
Click to expand...

I use Chrome and it's very seldom that I run into an incompatibility issue with IE re: code. More likely with CSS than anything else
 
AcidRaZor said:
jQuery is nice for IE6 and up as well as the other browsers. What ****s my mind is the different interpretations of CSS/HTML5 RFC's

Corporates usually stick with IE if they're running Windows. It's also easy to manage through Active Directory etc. So I don't care, I always write my **** with compatibility between all major browsers except Safari. Safari can go fly a kite, not installing that on my PC ;)
Click to expand...

Well if you write public facing websites you will lose a rather large chunk of users who do use Safari.
 
semaphore said:
Well if you write public facing websites you will lose a rather large chunk of users who do use Safari.
Click to expand...

it depends hey, i usually analyze the visitors from GA to see where it's trending/how it's growing. If it's less than 5% for the past 2-3 years I don't bother
 
AcidRaZor said:
it depends hey, i usually analyze the visitors from GA to see where it's trending/how it's growing. If it's less than 5% for the past 2-3 years I don't bother
Click to expand...

Yeah because nobody really uses an IPad these days ;)
 
Do you get a lot of visitors from China? http://www.ie6countdown.com/

I'm of the opinion that if an organisation has lots of money to spend on an internal project, then they should have money to hire someone who's clued up on IT, to even realise that IE6 is a security risk ... Can't say about 7 and 8.

jQuery plug-ins are like any other plug-in or program out there, if you're gonna rely on it for some functionality in the long term, you gotta make sure that it was written by someone/organisation that intends on supporting that plug-in's update.
For example, Node.js is ever so popular right now, so if you build a website that you expect to have a lot of visitors, and you get an authentication module that seemed easy to implement, but has limited support, you are likely to be screwed in the future.

Make sure that you spend some time getting to understand the inner workings of your plug-ins, so that when their dependencies are upgraded, you don't get left in the dark. From what I have seen, the times of things like MySQL, PHP, .Net being on a single major version for years are over. Today you download version 3.0.4 of a product, next week it's at 3.1.2 on Github, with inadequate documentation.

If you use jQuery a lot (like most of us), maybe it's time you clone their repository, and track changes. Invest time in the plug-ins you use, so you can maintain them for yourself if you need to. I depend on Wordpress, the Node stack and MongoDB stack. Once in every 2 weeks I check out the comments on their Git repos and update my knowledge accordingly, at times it takes less than 20 minutes :)
 
SuperNev said:
Do you get a lot of visitors from China? http://www.ie6countdown.com/

I'm of the opinion that if an organisation has lots of money to spend on an internal project, then they should have money to hire someone who's clued up on IT, to even realise that IE6 is a security risk ... Can't say about 7 and 8.

jQuery plug-ins are like any other plug-in or program out there, if you're gonna rely on it for some functionality in the long term, you gotta make sure that it was written by someone/organisation that intends on supporting that plug-in's update.
For example, Node.js is ever so popular right now, so if you build a website that you expect to have a lot of visitors, and you get an authentication module that seemed easy to implement, but has limited support, you are likely to be screwed in the future.

Make sure that you spend some time getting to understand the inner workings of your plug-ins, so that when their dependencies are upgraded, you don't get left in the dark. From what I have seen, the times of things like MySQL, PHP, .Net being on a single major version for years are over. Today you download version 3.0.4 of a product, next week it's at 3.1.2 on Github, with inadequate documentation.

If you use jQuery a lot (like most of us), maybe it's time you clone their repository, and track changes. Invest time in the plug-ins you use, so you can maintain them for yourself if you need to. I depend on Wordpress, the Node stack and MongoDB stack. Once in every 2 weeks I check out the comments on their Git repos and update my knowledge accordingly, at times it takes less than 20 minutes :)
Click to expand...

Your assumption of version control is totally wrong even thou PHP, .NET get new revisions / releases. Their current product version are supported years to come until they deem it necessary to stop.

.NET 2.0: 4/12/2011
.NET 3.0: 4/12/2011
.NET 3.5: 4/12/2011
.NET 3.5 SP1: 1/13/2015 (part of Windows 7)
.NET 4.0: ? at least 3/31/2015

Anyone using .NET 2.0 should be shot in the face anyways.
 
semaphore said:
Your assumption of version control is totally wrong even thou PHP, .NET get new revisions / releases. Their current product version are supported years to come until they deem it necessary to stop.

.NET 2.0: 4/12/2011
.NET 3.0: 4/12/2011
.NET 3.5: 4/12/2011
.NET 3.5 SP1: 1/13/2015 (part of Windows 7)
.NET 4.0: ? at least 3/31/2015

Anyone using .NET 2.0 should be shot in the face anyways.
Click to expand...

Yes, agreed :), that was over simplification on my part. I don't know much about .NET (but I know enough to agree on .NET 2.0), but take PHP for instance:
PHP has been on version 5.x for as long as I can remember, 4.x was supported because a lot of web hosts (prolly other reasons too) had continued to remain on 4.x for long. Right now it's at 5.4.x and 5.3.x, both being stable releases of each branch.
In that instance, things are stable. There was talk of PHP 6 for so long in the past few years, most new features were eventually released as 5.3 and 5.4.

So compare that with today's wunderkind programs, most seem to move on a single branch, major changes often happen in about 6 months, leaving something written in say 3 months back, being error ridden because APIs are implemented differently.

SuperNev said:
From what I have seen, the times of things like MySQL, PHP, .Net being on a single major version for years are over. Today you download version 3.0.4 of a product, next week it's at 3.1.2 on Github, with inadequate documentation.
Click to expand...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X