Bootstrap 5 will remove jQuery as a dependency

Post by acdha » Wed, Feb 13, 2019, 12:23 AM UTC

manigandham wrote: post #124

tcd wrote: post #48

Earlier quoted context omitted.

jQuery _did_ lots of useful stuff. It's unmaintained, has no interest/support (look at their github), doesn't adapt to modern features, is 'slow' compared to other frameworks that now use the Shadow Dom, and can be replaced with features that are native to JS - what's there not to like about that? One less dependency, network request and more efficient code is always worth the effort. Oh, and since the new code is va…

Jquery will fallback to native functions where available and it's feature complete. It doesn't need to have constant commits to still be immensely useful. Its primary purpose was smoothing over browser inconsistencies and it's cached by every major CDN already so using it is likely faster than trying to rebuild and maintain the individual parts separately.

Post by fenwick67 » Wed, Feb 13, 2019, 12:30 AM UTC

9dev wrote: post #137

tracker1 wrote: post #89

Earlier quoted context omitted.

Is SelectorEngine sizzle directly? I'm not sure how practical replacing jQuery is, and not going to look that deep. But jQuery isn't nearly as big today since most browsers (even IE11) are pretty modern.

A good replacement selector engine: `const selectorEngine = selector => Array.from(document.querySelector(selector));` :)

Post by JoelTheSuperior » Wed, Feb 13, 2019, 12:30 AM UTC

Solvitieg wrote: post #114

runarberg wrote: post #67

This is funny. I was thinking that Bootstrap should be suffering the same fate as jquery. That is, it’s relevance should be decreasing as web technology catches on. I see no reason for using a third party layout system now that CSS has `display: flex;` and `display: grid;`. As for modals and menus, HTML has ` ` and ` `. And for reusable components, we have custom elements, that you can either implement your self (not…

Depends entirely on the application. If your application has many basic views, you'll be wasting time writing out CSS grid properties for a basic responsive layout. I mean, at some point you'll recognize you're reinventing the wheel and just pull in a CSS grid from a framework. This applies to basically any components that has been battle tested in Bootstrap.

Post by nicoburns » Wed, Feb 13, 2019, 12:36 AM UTC

Carpetsmoker wrote: post #161

nailer wrote: post #70

Earlier quoted context omitted.

> As one of the commenters pointed out, a lot of stuff was copied from jQuery to make it work. > In other words, this entire effort seems of dubious benefit to me. You made other points, but I wanted to focus on this one. Yes, there's a few remaining bits that don't have standards. But you can do so much with querySelector, classlist.toggle(), lastElementChild, scrollIntoView, insertAdjacentHTML - literally every Jav…

> Side benefit: also no weird $(thing)[0] when you need to use a DOM API, like HTML5 validity or whatever. But looping over querySelectorAll() is painful. I'm not really a frontend dev, so perhaps I'm doing it wrong, but this is the "easier" way I found when I was writing an app a few weeks ago (in TypeScript): // Get Array of HTMLElements from querySelectorAll(). let queryAll = (q: string): HTMLElement[] => { let no…

  let queryAll = (q: string): HTMLElement[] => {
    let nodes = document.querySelectorAll(q);
    return Array.from(nodes).filter(node => (node instanceof HTMLElement)) as HTMLElement[];
  }