@thdxr What we _need_ is a good standardized set of CSS Custom Properties to facilitate code-sharing and customization both at once. Enough CSS-in-JS, enough inline styling. I just want to use the platform.
@jules_su Wow, this is very concerning. I went and did my own research and found other sources verifying the claim. Seems like there may be something to this. Look it up! Very concerning indeed. Wonder why the MSM isn't talking about it??
@diegohaz No thanks. Many prototypes have overlap, so checks and autocomplete would be ambiguous. Warnings raised would have more latency. Humans couldn't glance at a function signature and understand what it does. You would still have to type all your custom types, adding to the confusion
@mhevery Avoid prop-drilling in the first place. Do component composition, or create a context.
Excessive prop-drilling implies your components aren't components but just chunks of code.
@NickPickCodes @tobiasrkelvin @codewithvoid On the contrary, I'm skeptical of hiring inexperienced developers who seem unaware of their shortcomings.
Call yourself what you want, and be confident in what you can doβbut also about what you don't know.