3 ms·
As someone who does front-end JS stuff and uses a bunch of packages here is why I do it: I got tired of copying and pasting the same classes between projects.
by sibit 5y ago
As someone who does front-end JS stuff and uses a bunch of packages here is why I do it:
I got tired of copying and pasting the same classes between projects. The worse part was I'd add new features to the newer projects and when I would have to go back to work on something from a year or two ago I'd have to spend time backporting all the new code. I also don't like how bloated a bunch of the "popular" packages are. Why do something in 40kB of JS when you can do it in 3kB. Smaller is faster which is important to me because one of my main selling points is that I build modern-looking marketing websites that load and render under 5 seconds on a slow 3G connection.
- cmckn 5y ago> I got tired of copying and pasting the same classes between projects. The worse part was I'd add new features to the newer projects and when I would have to go back to work on something from a year or two ago I'd have to spend time backporting all the new code. Why not create your own common library and publish it to a private repo? There's a lot of options between using a stranger's package and what you're describing.
- CRConrad 5y ago> Why not create your own common library and publish it to a private repo? There's a lot of options between using a stranger's package and what you're describing. Exactly what I thought. Fascinating how they can have missed this obvious solution.