(fallen london stamps by "phosphor just use a library instead of fiddling with refs/media queries/whatever ungodly thing you're trying to wrangle this time"
have you considered: I would rather have my teeth pulled
okay I KNOW this is a rich thing to say considering this project is already using React and a bespoke component library BUT
- I work for a Corporation, and I get squirrely about incorporating open source stuff into Corporate Projects because legal and also because I know there's a bunch of open source folks who (understandably) would rather not have a Corporation use their stuff
- I have control issues. I Need to know how a thing works and I Need it implemented with the barest amount of fluff possible. the first can be offset by reading the code/docs but if the library implements something in a way I disagree with I have no non-terrible way to change that and I Fume.
like goodness I have soooo many opinions about this bespoke component library we are using. 95% of my use cases are accounted for but the remaining 5% is SUFFERING. what do you MEAN these buttons are not tabbable when I nest them. am I going to have to commit crimes with tabindex to get them to work?? huh? huh??? what the FUCK do you mean this other component is bugged so it doesn't rerender when state changes WHY WOULD YOU LEAVE THAT UNFIXED IN REACT--
(the biggest irony here is that I have spent a goodly amount of time writing some of my own components from scratch and have realized that for all my reluctance to use libraries, I would probably be the sort of person to write them)