▲ 243 ▼ new Date("wtf") (jsdate.wtf) submitted 1 year ago by Sheldan@programming.dev to c/programming@programming.dev 51 comments fedilink hide all child comments
[–] Tanoh@lemmy.world 13 points 1 year ago (1 child) There is a reason almost everyone use some Date lib, like Luxon and not the built in. And well, having a horrible built in lib that they can't change due to legacy code breaking is nothing really new or unique to JS. permalink fedilink source parent hideshow 2 child comments replies: [–] bleistift2@sopuli.xyz 2 points 1 year ago (1 child) The built-in lib is fine for basic stuff unless you do some crazy shit like expecting "2" to parse as a valid date. permalink fedilink source parent hideshow 2 child comments replies: [–] Tanoh@lemmy.world 4 points 1 year ago For very basic things maybe, but it has a lot of other weird problems and restrictions. Mutability, no real timezone support, very limited arithmetic, to name a few. As soon as you move beyond the very basic, you want someting more robust. permalink fedilink source parent
[–] bleistift2@sopuli.xyz 2 points 1 year ago (1 child) The built-in lib is fine for basic stuff unless you do some crazy shit like expecting "2" to parse as a valid date. permalink fedilink source parent hideshow 2 child comments replies: [–] Tanoh@lemmy.world 4 points 1 year ago For very basic things maybe, but it has a lot of other weird problems and restrictions. Mutability, no real timezone support, very limited arithmetic, to name a few. As soon as you move beyond the very basic, you want someting more robust. permalink fedilink source parent
[–] Tanoh@lemmy.world 4 points 1 year ago For very basic things maybe, but it has a lot of other weird problems and restrictions. Mutability, no real timezone support, very limited arithmetic, to name a few. As soon as you move beyond the very basic, you want someting more robust. permalink fedilink source parent