Bootstrap 5 will remove jQuery as a dependency

Post by zacmps » Wed, Feb 13, 2019, 5:01 AM UTC

Theodores wrote: post #33

entelechy wrote: post #8

This is great! This will make bootstrap more attractive and competitive as a framework. JQuery was one of the most important frameworks in Javascript history. It has enabled us to built real webapps. However since then differences between browsers shrunk significantly and we learned how to build maintainable and scalable apps in a more declarative fashion (hello React, Angular and friends)

Whoosh! Bootstrap is going the way of table layouts. Table layouts were great too but times change. Right now we have CSS Grid and it works in all browsers. I am sure they will bring this goodness to Bootstrap 5 but there is no need for the new layout engine that works great in all useful browsers to have a framework wrapper. Similarly with the jQuery, it was once useful in a table layout kind of way but nowadays you…

Post by ksec » Wed, Feb 13, 2019, 5:30 AM UTC

arp242 wrote: post #39

This PR is massive and represents a year and a half of work. If you look at the comments you see there are loads of browser-specific issues being fixed. IE support was dropped as they didn't feel making stuff compatible (jQuery did that for them before). The API is also incompatible; in the words of one dev: "we broke everything". As one of the commenters pointed out, a lot of stuff was copied from jQuery to make it…

Post by austincheney » Wed, Feb 13, 2019, 5:46 AM UTC

acdha wrote: post #185

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…

If you actually try to do this yourself, you’ll learn why Bootstrap is popular. You’ll spend plenty of time making everything consistent across browsers, responsive, visually consistent, accessible (a legal requirement for most of us), etc. If you’re working on a big project with a dedicated team, that approach can give you quite a lot but there are a ton of projects which prefer to spend their time on the core produ…

Post by akulkarni7 » Wed, Feb 13, 2019, 5:58 AM UTC

austincheney wrote: post #235

acdha wrote: post #185

Earlier quoted context omitted.

If you actually try to do this yourself, you’ll learn why Bootstrap is popular. You’ll spend plenty of time making everything consistent across browsers, responsive, visually consistent, accessible (a legal requirement for most of us), etc. If you’re working on a big project with a dedicated team, that approach can give you quite a lot but there are a ton of projects which prefer to spend their time on the core produ…

> If you actually try to do this yourself, I do frequently. There are many things in life that are hard and cross-browser CSS is not among them. In the past I have found things like Bootstrap and jQuery to be more of a frustration than a benefit by introducing cross-browser differences in their attempt to help . At the same time they don't fix the cross browser differences that really impact layout, such as differenc…

Post by [deleted] » Wed, Feb 13, 2019, 6:08 AM UTC

pupdogg wrote: post #225

capsulecorp wrote: post #196

Earlier quoted context omitted.

And when the wheel is so bloated the car can barely make it down the road without needing to refill the fuel tank a new more lightweight reliable wheel that can handle modern terrain is needed. That is why people are moving away from Jquery.

I am going to root for bloated jQuery to save my life! $('.tpm_sensors').forEach(function(sensor) { if (sensor.pressure vs: var tpm_sensors = document.getElementsByClassName('tpm_sensors'); for (var i = 0, len = tpm_sensors.length; i < len; i++) { var sensor = tpm_sensors[i]; if (sensor.pressure < threshold) fixBeforeIDie(); }