#ActuallyAutistic web dev. Does front of the front-end. Loves perf and minimalism. Prefers HTML, CSS, Web Standards over JS, UX over DX. Hates div disease.
Existing implementations get outdated. Especially on the web.
Many libraries aim for completeness: too many features, may still lack a feature you need, and not enough minimalism. There is no point to add in features you don't use, and code splitting does not always remove all of the parts you don't use.
I think it is almost always better to write a custom solution fit perfectly for the need and keep your dependencies at a minimum, too. You'll get tons of deps even when you try to avoid them, because there is always stuff that is pointless to make yourself. And you can find minimalistic utilities that do exactly what you need, and do some hard stuff that makes no sense to spend your own time (if you're limited in time as we easily are).
Keeping code focused makes it easier to change it later and you have less to throw away.
I think this is one of the best routes to take for smaller teams. It gets more difficult when you work at scale. Working with proprietary tech increases onboarding time since it's harder to just find engineers who "know how to do the job".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Existing implementations get outdated. Especially on the web.
Many libraries aim for completeness: too many features, may still lack a feature you need, and not enough minimalism. There is no point to add in features you don't use, and code splitting does not always remove all of the parts you don't use.
I think it is almost always better to write a custom solution fit perfectly for the need and keep your dependencies at a minimum, too. You'll get tons of deps even when you try to avoid them, because there is always stuff that is pointless to make yourself. And you can find minimalistic utilities that do exactly what you need, and do some hard stuff that makes no sense to spend your own time (if you're limited in time as we easily are).
Keeping code focused makes it easier to change it later and you have less to throw away.
I think this is one of the best routes to take for smaller teams. It gets more difficult when you work at scale. Working with proprietary tech increases onboarding time since it's harder to just find engineers who "know how to do the job".