engineering at @aaveaave ๐ป and @lensprotocol ๐ฟ // creator of @lenster ๐ธ // fighting for human privacy ๐ก๏ธ // opinions are mine // he/him ๐
I am a software engineer currently working @ShopPad, previously @HPE. I like to build websites and web application in PHP, JavaScript, and Golang. I have an unhealthy obsession with Mexican food (๐ฏ)
This could potentially become a very big problem depends on how your app is structured. For instance, if you have a monolithic app that has, it has decoupled components (modules or whatever you want to call it), and each of them has theirs on vendor directory, this will make your app huge.
This brings problems with IDE indexing taking forever, and even downloading the repo.
engineering at @aaveaave ๐ป and @lensprotocol ๐ฟ // creator of @lenster ๐ธ // fighting for human privacy ๐ก๏ธ // opinions are mine // he/him ๐
Striving to become a master Go/Cloud developer; Father ๐จโ๐งโ๐ฆ; ๐ค/((Full Stack Web|Unity3D) + Developer)/g; Science supporter ๐ฉโ๐ฌ; https://coder.today
This will increase the size of the repo!
This could potentially become a very big problem depends on how your app is structured. For instance, if you have a monolithic app that has, it has decoupled components (modules or whatever you want to call it), and each of them has theirs on vendor directory, this will make your app huge.
This brings problems with IDE indexing taking forever, and even downloading the repo.
Yeah exactly of course it will take too much time to index in my IDEs.
It will have to be indexed and downloaded regardless of whether it's from the repo or some web storage.
Try ripgrep or fzf, they're pretty great at fast searching.
Maybe this way devs will realize how much code they really have in their app.
Probably dead code, untested code and so on. Package managers make things so easy to throw away performance, lower level concerns and build sizes.