5 ms·
It's still mostly true in practice. You don't add one more layer to your image to build the next version, you rebuild it from the Dockerfile, which is the oppos
by orthoxerox 1y ago
It's still mostly true in practice. You don't add one more layer to your image to build the next version, you rebuild it from the Dockerfile, which is the opposite of Smalltalk approach.
- igouy 1y agoDo you think "rebuild it" cannot be used with Smalltalk? See https://news.ycombinator.com/item?id=45838056 https://news.ycombinator.com/item?id=45838056
- lmm 1y agoA theoretical capability is not enough; what matters is whether that's a practical workflow that's actually adopted by the community.
- cbsmith 1y agoIt's a practical workflow that's actually adopted by the community.
- igouy 1y agoIt's a practical workflow that was actually adopted. Next you'll be wondering whether changes were integrated continuously throughout the day — "This fine granularity of components enables highly concurrent development because changes can be tracked down to the individual method level …" 2001 "Mastering ENVY/Developer". https://www.google.com/books/edition/Mastering_ENVY_Developer/ld6E19QIMo4C?hl=en&gbpv=1&dq=mastering+envy+developer&printsec=frontcover https://www.google.com/books/edition/Mastering_ENVY_Develope...
- cbsmith 1y agoThat's where you're wrong. It's not the opposite of the Smalltalk approach.