3 ms·
in 2012 i had a project where i realized that frontend frameworks would be the right approach. i analyzed what was there (knockout, ember, angular and a few oth
by em-bee 8y ago
in 2012 i had a project where i realized that frontend frameworks would be the right approach. i analyzed what was there (knockout, ember, angular and a few others), and picked angular as the most agreeable. that was before angular was popular.
then i stuck with it until angular 1 was essentially no longer kept current.
i evaluated again at that point, and this time picked aurelia. i'll stick with that until i run into a problem that aurelia can't help me with and then i'll start looking for alternatives.
same goes for backend frameworks, or platforms. i am still working with the same one that i discovered in 2004. not going to change until i run into a problem where this platform doesn't fit.
in the meantime i am learning more exotic things like common lisp and smalltalk (rather the opposite of shiny and new), to get a different perspective on programming, but not to help me solve todays problems (except for fun).