Bootstrap 4 alpha • Hacker News Board

Re: Bootstrap 4 alpha

#51

Post by lol768 » Wed, Aug 19, 2015, 5:33 PM UTC

joshburgess wrote: post #50

Sass by default FTW! It says they rewrote all of the JS using ES6... Does this mean jQuery is no longer a dependency?

Assuming the comment in the starter template isn't outdated, jQuery is still required.

http://v4-alpha.getbootstrap.com/getting-started/introductio...

Re: Bootstrap 4 alpha

#52

Post by hnrch02 » Wed, Aug 19, 2015, 5:36 PM UTC

joshburgess wrote: post #50

Sass by default FTW! It says they rewrote all of the JS using ES6... Does this mean jQuery is no longer a dependency?

No, jQuery is still required.

Re: Bootstrap 4 alpha

#53

Post by joshburgess » Wed, Aug 19, 2015, 5:36 PM UTC

lol768 wrote: post #51

joshburgess wrote: post #50

Sass by default FTW! It says they rewrote all of the JS using ES6... Does this mean jQuery is no longer a dependency?

Assuming the comment in the starter template isn't outdated, jQuery is still required. http://v4-alpha.getbootstrap.com/getting-started/introductio...

Booooooooooo. Bootstrap is the most popular CSS/UI framework on the planet. I don't get why they continue to depend on jQuery while most modern app frameworks are abandoning it...

Re: Bootstrap 4 alpha

#54

Post by ivansavz » Wed, Aug 19, 2015, 5:36 PM UTC

mbreedlove wrote: post #5

I'm very excited for the move to SASS and ES2015. Also, the few themes they have on themes.getbootstrap.com look very nice!

Yeah, I also like the move to SASS! I used to work with an unofficieal sass port of bootstrap, but not in the future!

(I know less / sass is about the same thing, but i have a bunch of folders of old projects i can copy-paste from in sass, and not in less, so i'm super biased)

Re: Bootstrap 4 alpha

#55

Post by hit8run » Wed, Aug 19, 2015, 5:37 PM UTC

zzalpha wrote: post #24

hit8run wrote: post #21

I'm not sure if one really needs to load in tons and tons of css and js for displaying a site like http://themes.getbootstrap.com/products/marketing :/

Meh, if it means rapidly putting together a high-quality, cross-browser, responsive website with little effort, I'll accept a little bloat. The savings in developer time is more than worth it, IMO. Doubly so given how much of that CSS and JS is likely cached.

For prototyping this is okay. But for production I try to keep bloat as low as possible. I see this as service to my customers. A fat ui framework like this adds its very own complexity and as soon as you want to go out of the crud box you will have to add your own styles anyway.

Re: Bootstrap 4 alpha

#56

Post by dlandis » Wed, Aug 19, 2015, 5:41 PM UTC

Does anyone know why they don't want to support right-to-left? I've seen tons of questions and posts about it over the years so I'm surprised that even with the next major release they aren't addressing it. Maybe I'm missing a perspective here though -- don't other people think that rtl should be a core capability of a framework like this? I'm also curious whether accessibility will be improved in 4.x.

Re: Bootstrap 4 alpha

#57

Post by Siecje » Wed, Aug 19, 2015, 5:41 PM UTC

I'm curious about the process of writing the Docs in markdown.

Re: Bootstrap 4 alpha

#58

Post by at-fates-hands » Wed, Aug 19, 2015, 5:42 PM UTC

JuanSoto wrote: post #32

Very interested in the new grid system. It's always been my favorite part of Boostrap—looking forward to see what they do with it.

I'll be interested to find out what level of customization you can do to it.

The fact their grid was so rigid is why I switched to Jeet a while ago:

http://jeet.gs/

Re: Bootstrap 4 alpha

#59

Post by coderdude » Wed, Aug 19, 2015, 5:42 PM UTC

hliyan wrote: post #6

Also launching official bootstrap themes: http://themes.getbootstrap.com/collections/all Edit: unfortunately though, the 'dashboard' theme is not fully responsive (tables (order history) in mobile view)

I hope this leads to a 'standard' way of developing Bootstrap-based templates. Something comparable to the submission guidelines on WrapBootstrap but codifying how a template's assets should be arranged, written, etc. Using Bootstrap as a base for new template designs was a major step forward for the template industry because customers aren't walking into a completely foreign codebase with each purchase. If that familiarity were extended further then it could lead to interoperability of component styles between templates developed by different designers, which is something customers have brought up numerous times over the years. It's never quite that simple but I think for example simple namespaces would be a step in the right direction ('.unify .nav-tabs' and '.vitality .nav-tabs').

Re: Bootstrap 4 alpha

#60

Post by AhtiK » Wed, Aug 19, 2015, 5:43 PM UTC

jscheel wrote: post #45

pyre wrote: post #41

Earlier quoted context omitted.

Not unless you like chasing the "latest and greatest" fad. If Sass (or Less) is working for you, then use it. If you are running into issues, then research alternatives. Both Less and Sass are actively maintained projects, so there's not reason to run around switching frameworks unless there is a concrete need for it.

I ran into significant issues with LESS that forced me to switch. I haven't seen any with SCSS, so that's the question. Is it just another new fad, or have people exhibited a real need for switching?

would you mind sharing what were the significant issues with LESS?

I'm using LESS and just wondering what I might be missing.