It's not just the explicit API. Event style APIs create a huge amount of implicit surface that is nearly impossible to document and account for. It's sometimes worth it but very expensive to get right.
-
-
Yup. I even think
@wSokra saying a few months back, if he would write it today, it probably would likely look at bit different.1 reply 0 retweets 1 like -
Replying to @TheLarkInn @wycats and
Does webpack have any guarantees around hermetic and reproducible builds?
1 reply 0 retweets 3 likes -
I've still not entirely wrapped my head around this concept so please correct me if I misunderstand: When a build happens, if nothing changes it should produce the same output every time?
2 replies 0 retweets 1 like -
-
Replying to @montogeek @samccone and
Then yes. We even guard against this on the surface (although shallow with example) in our stats tests IE: our stats and output is snapshotted to ensure hashes do not change and fail if they differ across platform etc.https://github.com/webpack/webpack/tree/master/test/statsCases/preset-detailed …
1 reply 0 retweets 0 likes -
Replying to @TheLarkInn @montogeek and
Sam, there could be more depth in this. Like we could technically spin up a test case specifically for hermiticity (sp?) and snapshot resulting exact code etc.,
1 reply 0 retweets 0 likes -
Replying to @TheLarkInn @montogeek and
Does that answer your question accurately?
1 reply 0 retweets 0 likes -
-
Replying to @samccone @TheLarkInn and
It's more than just "if nothing changed there's no new output" (which can be handled with a guard) but also "if something small changed it ran a predictable and guaranteed set of steps to get an update"
1 reply 0 retweets 1 like
In other words if something DID change, you get the same output. If you flip flop one line of code, you get output A then B then back to A etc. Exactly the same A and B.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.