3 ms·
I would call technical debt to writing it as you go, since there are many small bugs and inconsistencies that (hopefully) are fixed by these libraries. Just a c
by franciscop 10y ago
I would call technical debt to writing it as you go, since there are many small bugs and inconsistencies that (hopefully) are fixed by these libraries. Just a couple of random examples:
- https://github.com/picnicss/picnic/issues/79 https://github.com/picnicss/picnic/issues/79
- https://github.com/picnicss/picnic/issues/64 https://github.com/picnicss/picnic/issues/64
So you can have a half-baked solution with 10 more minutes or use a tested and documented one and save 10 minutes.
- threatofrain 10y agoI think a more on-point rebuttal would give us examples of flexbox-specific bugs.
- franciscop 10y agoTrue, I thought it was widely know but there's a whole Flexbugs project [1] and that there are many Known Issues with flexbox [2]. Some with solution, some without them. [1] https://github.com/philipwalton/flexbugs https://github.com/philipwalton/flexbugs [2] http://caniuse.com/#feat=flexbox http://caniuse.com/#feat=flexbox
- irrational 10y agoThank you! I've never heard of flexbugs.