3 ms·
Alternatively we need to start making optional frameworks. Essentially a way to do many of the usual things you use a framework for (like model binding) but wil
by BinaryIdiot 10y ago
Alternatively we need to start making optional frameworks. Essentially a way to do many of the usual things you use a framework for (like model binding) but will work, without changing the code, when using just about any framework.
I hate taking the basic things that are not hugely different in concept and workflow but end up using very different code so I can't port it between frameworks. Working on the start of this in my msngr.js library (shameless plug) because I would like to use it but also because I think it's important.
A new framework every couple of weeks is daunting but okay. Not being able to reuse code between them is awful.