I think part of the problem with modern software is the selection of libraries. Instead of selecting libraries that do one thing and can be made to work together with normal code. People select libraries that "do" 80-90% of everything they need. They don't really reduce complexity because there is often a minimal level of complexity inherent to an application and no matter how many ways you twist how a problem can be solved it isn't going to solve your problem really automagically. It also makes your code less migratable when you decide that library is weighing you down if you need to write code significantly differently when you use it. If it somehow does do one thing truely automagically for you, for 90% of other applications (including the remaining matters for your code) it will only shift how a problem is solved and make it harder to make it work with other libraries unless you find some plugin within the ecosystem.
OMG there is a huge number of plugins within the react framework! Yeah, but before we put a framework over javascript the entire npm repository was within the ecosystem. And before that all libraries were written in C and because all languages have tie-ins to C it used to be that all libraries were in the same ecosystem.
Log in
I think part of the problem with modern software is the selection of libraries. Instead of selecting libraries that do one thing and can be made to work together with normal code. People select libraries that "do" 80-90% of everything they need. They don't really reduce complexity because there is often a minimal level of complexity inherent to an application and no matter how many ways you twist how a problem can be solved it isn't going to solve your problem really automagically. It also makes your code less migratable when you decide that library is weighing you down if you need to write code significantly differently when you use it. If it somehow does do one thing truely automagically for you, for 90% of other applications (including the remaining matters for your code) it will only shift how a problem is solved and make it harder to make it work with other libraries unless you find some plugin within the ecosystem.
OMG there is a huge number of plugins within the react framework! Yeah, but before we put a framework over javascript the entire npm repository was within the ecosystem. And before that all libraries were written in C and because all languages have tie-ins to C it used to be that all libraries were in the same ecosystem.