2 ms·
The latest commits to jQuery.sheet were done in 2015, thus the date. The problem is not in being trendy. The problem is working on a pretty low abstraction lev
by nine_k 11y ago
The latest commits to jQuery.sheet were done in 2015, thus the date.
The problem is not in being trendy. The problem is working on a pretty low abstraction level when higher levels, streamlining the code while giving more performance, are available for years.
It's like asking why an app in 2007 would be written in plain JavaScript when e.g. jQuery is available.
Re 'no right or wrong': it does matter if you have to maintain the codebase for a long time. I've seen some legacy codebases, and I can appreciate some of the right choices done by their authors many years ago, as well as pity some of the poor choices made many years ago. Both significantly affect how easy it is to fix bugs and add features to many-yeas-old (or sometimes decades-old) code.
- alextgordon 11y agoIt's interesting to hear jQuery being criticised for being at to low an abstraction level. I thought the hip thing to do was to revisit the stone age: http://youmightnotneedjquery.com http://youmightnotneedjquery.com If jQuery is low level, what is high level? SproutCore? Cappuccino? Angular 1? These high-level frameworks have a bright future ahead.
- tim333 11y ago>higher levels, ... giving more performance, are available for years. Any data to back that? In most tests I've seen React, Angular and the like are slower than just using jQuery