3 ms·
So I need to load an additional js framework in additional to whatever one I'm using so that I can run plugins from yet another framework? As much as I love jav
by geuis 17y ago
So I need to load an additional js framework in additional to whatever one I'm using so that I can run plugins from yet another framework? As much as I love javascript, we still have to remember that most people don't use the kickass speedy browsers that we tend to (Chrome, Safari). Depending on your audience, you have 30-40% of your audience using Firefox. That's pretty good, but things get boggy with FF and too much js running.
If you're building a web application, i.e. something like Gmail, then you need to pick one js framework and stick with it. Make your code as efficient as possible. If you are just building a regular web site, do you really need to have all of that extra overhead for a couple of widgets?
Treat js development like da Vinci treated marble. Cut away until you find the statue in the marble.
- johndaviddalton 17y agoThe idea is that with FuseJS powering the framework it will be more stable (additional bug fixes, additional browser support) and faster (less abstraction, forked methods, speedy design). So you can replace the emulated framework with FuseJS + emulation layer and not have to reprogram your entire application that is running on the old framework. FuseJS is designed to be modular so you can use only the parts you need :D