Third and foremost, what kind of developer are you? I like being a minimalist developer.Second stopping the bytes waste can significantly prolong the life of an SSD.Another quote found here: “This is used in our CI because it gets our build size down to a point where we can run on stock azure VM images (IIRC they have a ~10 Gig limit that we violate without hard links)” To quote a Roslyn engineer from this page Always use hard links when building in CI “One effect of this is it makes us fit within the size budget of the built-in AzDo Windows agents, which are slower, but highly available”. So having a build output that weights many GBs can make a real difference in terms of budget and feasibility. First nowadays most builds occur in CI/CD with VM size limitation and cost.
I know many developers who’d argue: “who care, I have a 2TB SSD hard-drive and need to focus on getting the job done!” Moreover the console app is still runnable: Now there is a single binary directory defined at the root of the solution and a single instance of the library DLL.
0 kommentar(er)
