DEV Community


Discussion on: What if we would share code instead of packages?

cyberhck profile image
Nishchal Gautam

If by code sharing you mean code is checked in on your project, I feel most of the time, it's not the best idea in my opinion, and that's because it'll increase what you have to maintain, when I use a package, it's them who will update their package, not you...

valeriavg profile image
Valeria Author

I agree, there are packages that are not meant to be edited - a database protocol implementation for example; And in this case a compiled binary library would do a better job.

Like it or not, we are maintaining packages we use. It's not just install and forget. At the very best, you'll need to update it from time to time and adjust your code to the changes.

Debugging, optimisation and sometimes even testing gets really hard without full access to the code.

The package needs to be a bit different too. Closer to Dino - minimalistic, preferably with no dependencies, meant to be edited and adjusted.

Now you probably thinking about git submodules. And I agree with you - working with them is a hell. The smooth tech for this concept doesn't exist. Yet:)