Live data from Hacker News

Bootstrap 5 will remove jQuery as a dependency

github.com

101–110 of 333 posts

Re: Bootstrap 5 will remove jQuery as a dependency

#101

Earlier quoted context omitted.

It is not just `display: grid` that is replacing the layout. Now we also have interactive elements in the HTML spec[1] like ` ` and ` `. We also have custom elements making an all in solution like bootstrap less desirable for everything except quick prototyping. [1]: https://html.spec.whatwg.org/multipage/interactive-elements....

Dialog is nice if you only support Chrome and Firefox. Maybe when Edge turns to Chromium it won't be as bad, but the truth is that Bootstrap is accessible in most if not all modern browsers, but the new HTML5 elements are not.

You can always drop in a polyfill[1], and when browser support picks up, you can remove it from your dependencies. That is what people used to do when they decided to omit jquery in favor of native web APIs a few years back.

[1]: https://github.com/GoogleChrome/dialog-polyfill

Re: Bootstrap 5 will remove jQuery as a dependency

#102

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…

Have you seen all the CSS for simple stuff like a button and for other handy components? I don't want to write all that just to make a pretty button unless your job is doing only HTML/CSS.

Re: Bootstrap 5 will remove jQuery as a dependency

#103

Earlier quoted context omitted.

For one, fetch() doesn’t support progress reporting.

It does. The fetch response object exposes a `ReadableStream` through the `body` property, which you can loop through with a `for await ... of` loop. On each iteration, simply update your progress.

See [1] for a demo

[1]:https://tejasq.github.io/basically-streams/examples/fetch/

Re: Bootstrap 5 will remove jQuery as a dependency

#104

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…

dialog doesn't work by default in Edge, Firefox, or Safari. I don't think it's ready yet.

My reason for using bootstrap is that it looks better than any UI I design from scratch.

Re: Bootstrap 5 will remove jQuery as a dependency

#105
Long-ish time ago I tried to modularize and modernize Bootstrap [0] to be easier to use with the (still) current way of development and needless to say it was hard, very hard. In the meantime challengers like Bulma, Semantic UI and Material and Material UI have risen to challenge, with the added benefit of being written at least partly from scratch (again).

I still think that Bootstrap has it's uses, but incremental updates at this point seem to be harder than rebooting the whole thing writing everything from scratch, maybe even using things like CSS Grid and friends in the background. All the best to the current maintainers in their pretty hard task!

[0] https://github.com/twbs/bootstrap/issues/19017

Re: Bootstrap 5 will remove jQuery as a dependency

#108

Can someone explain why if you like jquery and you're used to it why is it a bad idea or it's not but just personal preference at this point?

Not a total expert, but as a fan of JQuery I've read the arguments. JQuery modifies the DOM at runtime, this means lots of node traversals and redrawings on the fly, which make it nearly impossible for the Javascript engine to optimize anything. More modern frameworks in general use the concept of a Shadow DOM: they keep their own representation of the DOM internally and only send the full frame to the engine for ren…

Virtual Dom faster than direct manipulation? Source please.

Re: Bootstrap 5 will remove jQuery as a dependency

#110
post #82

Earlier quoted context omitted.

Legacy bootstrap did ship with considerably fat set of dependencies - jQuery, popper, etc. Compare that to Bulma or something more modern, it ships without these dependencies. When the world is moving towards css-in-js and other aggressive ways of trimming unwanted code, removing dependencies is a good move by Bootstrap

Only part of the world is moving to css-in-js. I won't be on the boat leaving for that destination.

Completely agree - I find the current trend (and that's what I see it as) of css-in-js to be most disagreeable. CSS works fine without JS, or even better with SASS/LESS.
Post reply on HN