DatePickers should be a W3C standard handled by the browser. We shouldn't rely on JavaScript plugins to do this basic input stuff

What's your worst experience with "not invented here syndrome"?

In the recent past I've been dealing with custom made JS datepickers, autocomplete boxes and various other widgets that were purpose made for some feature. Almost every single widget the app uses is built from scratch.

Now there are new features that need these widgets to behave differently, and needless to say, none were built with customisation or extendability in mind.

Hardly shocking, I know, but I'm the one that has to spend several hours to get these widgets to work for the new features instead of using some of the many open-source, tested, mature and customisable solutions that are out there.

!rant

What are people thinking when they are building datepickers (or any type of angular/jQuery plugin for that matter)?

Lets put all of the code in one file, place everything that should be dynamic and optimizable in constants, provide no localization support, finish it all up, publish it to bower and npm (so poor devs won't have to struggle) and last but not least don't accept pull requests with useful features for months!

When you don't care to put datepickers

Fuck JavaScript!!!!!

I'm building an application using Vue with MaterializeCSS and i'm using moment to handle dates. i have to initialize datepickers with values at mount of the vue. i use variables to store the states. there are proper routines for intialization and setting of the pickers. the routines run. there are no errors. the pickers show values. no errors. but the fucking variables ar empty!!!! the pickers are not being set. holy mother of fcuking shitty js milk!