Neopets "Help" page has been updated!

[RealisticError]

LITERALLY

They're based in US, right? US with some of the best laws for businesses (at the expense of the workers).

Fucking CONTRACT SOMEONE IF YOU'RE CHEAP JFC

Pay them the same, whatever, but just contract someone fucking capable for a project JFC.

[There's probably a myriad of reasons that it's problematic, but like... they've tried nothing and they're all out of ideas]

Speaking as a web developer: they seem to be building the new site pretty much from scratch (judging by the awful naming scheme of their CSS: nav-profile-dropdown__2020 nav-dropdown__2020, yeah that'll go down great when we hit 2021) and there's no reason for a new build to be problematic, they basically have free reign to fix all of the issues that they had in the old site and make it look pretty on top!

[Using My Pass]

Speaking as a web developer: they seem to be building the new site pretty much from scratch (judging by the awful naming scheme of their CSS: nav-profile-dropdown__2020 nav-dropdown__2020, yeah that'll go down great when we hit 2021) and there's no reason for a new build to be problematic, they basically have free reign to fix all of the issues that they had in the old site and make it look pretty on top!

Wait, could the 2020 in the name actually cause issues once the date is 2021??

Unless that's indicative that it's linked to something that IS date based.

Actually, I get the impression that if the answer is "yes" explaining the reasoning to my dumb ass is basically pointless.

I think they mentioned building it from scratch - or maybe it's just been the general consensus.

Either way, if '2020' in their fucking css naming scheme can cause problems in 2021... And they haven't noticed that... God help them and us.

[Da Plushee Boree]

Does this mean bye bye to helpfull zafara avatar?

[motherfucker]

Wait, could the 2020 in the name actually cause issues once the date is 2021??

Unless that's indicative that it's linked to something that IS date based.

Actually, I get the impression that if the answer is "yes" explaining the reasoning to my dumb ass is basically pointless.

I think they mentioned building it from scratch - or maybe it's just been the general consensus.

Either way, if '2020' in their fucking css naming scheme can cause problems in 2021... And they haven't noticed that... God help them and us.

It won't cause any coding issues as not much code is ever tied to dates.
It's just messy.

They should clean and streamline because they're essentially starting over their "stylesheet".

[RealisticError]

Wait, could the 2020 in the name actually cause issues once the date is 2021??

Unless that's indicative that it's linked to something that IS date based.

Actually, I get the impression that if the answer is "yes" explaining the reasoning to my dumb ass is basically pointless.

I think they mentioned building it from scratch - or maybe it's just been the general consensus.

Either way, if '2020' in their fucking css naming scheme can cause problems in 2021... And they haven't noticed that... God help them and us.

It couldn't cause issues, it's just bad practice and stupid to do haha Imagine going back through website code in 2025 (maybe I'm being generous) and seeing everything named _2020, you'll sit there thinking "has this bug I'm trying to fix been there since 2020, has it been fixed and just continues to use this naming scheme?" etc

[koopatrooper]

It might be but one would have to check.