On 8/27/14, 10:22 AM, Gregory Szorc wrote:
There is additional cognitive load required to map a logical feature into a set of directories. I would prefer this burden go away, as it only breeds confusion and a higher barrier to contributing (new contributors don't know these shortcuts so they sit through painfully long full builds).
I don't understand. I didn't pick these directories because there was any concept of a logical feature: I picked those because those were the files that I edited. That seems like the least-posssible cognitive load in general.
Also, for the JS-centric use case you mentioned, if we invested in those parts of the build system, we could probably get full tree builds with no binary changes to under 10s. e.g. |mach build nonbinaries|.
Sure. But since we don't have that yet, let's make sure that thing we did have keeps working? Is returning to the prior behavior by making `mach build dir` recursive a complex fix?
--BDS _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
