2 ms·
You need framework integration at some point; otherwise, you end up writing glue code for every single library you use, which is a huge waste of time. The issue
by RussianCow 6y ago
You need framework integration at some point; otherwise, you end up writing glue code for every single library you use, which is a huge waste of time. The issue is when some library authors don't separate the "core" part of the library from the framework integration, but that's understandable because 1) it's less work to only support a single framework, and 2) you can design your API around that framework specifically, as opposed to trying to make something generic (which often doesn't translate well to some frameworks anyway).