3 ms·
As great as that tool is (I do think it's good) I wouldn't call that a solution, I'd call that a mitigation. If the ecosystem is terrible (dependency-bloat wise
by swsieber 7y ago
As great as that tool is (I do think it's good) I wouldn't call that a solution, I'd call that a mitigation. If the ecosystem is terrible (dependency-bloat wise), then a tool like that doesn't make a big impact.
- burntsushi 7y agoI think the biggest problem crev has is adoption. But if it solves that, then I disagree that it doesn't help with the dependency bloat problem. It would serve as pressure against adding dependencies, because with crev, adding dependencies becomes a lot more work because of the code review system. That in and of itself may be enough pressure to reduce the dependency bloat problem. It's a big if---especially adoption---but it makes sense to me.
- feanaro 7y agoSomething that requires a lot of work sounds like something people will be hesitant to use.
- burntsushi 7y agoHence my acknowledgment that adoption is the biggest problem to overcome for crev. :-)
- sriram_sun 7y agoI hope this takes off. In this really good talk https://www.hillelwayne.com/talks/what-we-know-we-dont-know/ https://www.hillelwayne.com/talks/what-we-know-we-dont-know/ Hillel mentions that (I'm paraphrasing) one metric that positively affects code quality is code review.