here is a random example to showcase how this can make sense (I'm not too familiar with the actual stacks in questions):
- stack A needs lots of tedious, not-quite boilerplate not-quite-copy-paste work whenever you implement something, but reduces cross-OS bugs, UX and accessibility issues down the line. Lots of dev frustration, slows down iteration (when humans actually have to do this).
- stack B has awesome DX and affords smooth operation of the design/UX/dev teams, very fast. More issues down the line, though. May be worth it if unaided humans need to work on it.
- stack A needs lots of tedious, not-quite boilerplate not-quite-copy-paste work whenever you implement something, but reduces cross-OS bugs, UX and accessibility issues down the line. Lots of dev frustration, slows down iteration (when humans actually have to do this).
- stack B has awesome DX and affords smooth operation of the design/UX/dev teams, very fast. More issues down the line, though. May be worth it if unaided humans need to work on it.