Live data from Hacker News

Bootstrap 4 alpha

blog.getbootstrap.com

71–80 of 216 posts

Re: Bootstrap 4 alpha

#71
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)

the Dashboard one looks nice, but is currently (of course) still using Bootstrap 3. anyone knows if there's a free upgrade to a BS4 version once released?

Yeah. We're adding this to the FAQ right now, but the updates are free for the life of the theme (including updates to future versions of Bootstrap) <3

Re: Bootstrap 4 alpha

#72
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)

Wow, only $99 for officially supported Bootstrap themes. I love it.

More expensive than some others out there but the quality of other commercial Bootstrap themes tends to be pretty low:

- Many themes out there are never updated. I remember some $15-ish Bootstrap themes for 3.1 that were never updated for 3.2, etc

- Many Bootstrap themes out there are non-semantic div hell. Headers wrapped in tags with a class of "header" instead of simply using h1/h2/h3/etc tags. That kind of thing. Often because they were simple ports of themes from other frameworks. Bootstrap isn't always the most semantic thing in the world... but some of the Bootstrap themes you can buy out there are sheer crap.

If these official Bootstrap themes can excel on those two points, they're a bargain.

Also, from their About page at http://themes.getbootstrap.com/pages/about-us

    We keep Bootstrap funded and available for everyone. To
    date, we have never taken money from investors and have
    no corporate sponsorships. All our expenses are paid for
    by us through ad revenue on our docs.
Pretty good reason to throw them $99 right there, if Bootstrap has saved you $99 of time over the years.

Re: Bootstrap 4 alpha

#73
post #45
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?

(I wanted to post this reply to DarkTree too, since it seemed equally applicable.)

I've looked at PostCSS a couple of times lately and it seems "interesting", but the cited benefits (speed, modularity, the ambiguous "more powerful") aren't really things I've ever paused to worry about with Sass. And when I look at the first example of PostCSS, it seems dauntingly weird, though presumably some of that is actual future CSS - I have enough trouble keeping up with future JavaScript, so forgive me if I've not really kept au courant with whatever is happening in the future of CSS (I think I lost interest around the time they decided to make variables really, really complicated).

Sass seems to solve all or most of the problems I care about most of the time with CSS, and it's easy to onboard people who've never used it before. In fact, to be honest, I only really use a subset of the features of Sass (variables, nesting, mixins, inheritance), so switching to something that has more powerful features that I would probably more powerfully have to eschew is... not very high on my list of priorities.

Re: Bootstrap 4 alpha

#74
post #34

Earlier quoted context omitted.

They only provide one type of license: http://themes.getbootstrap.com/pages/our-license It is comparable to the "Multiple Applications License" provided by WrapBootstrap. Still relatively expensive since most Multiple Applications Licenses are under $99.

Do I live in some sort of parrallel universe that thinks a well documented base design for dashboard/app that will presumably continue to mature for $99 is SUPER STINKING CHEAP? If this is officially supported by the Bootstrap project - this to me feels like a nuts deal.

I agree. I have definitely wasted $99 worth of time struggling with some of the crap commercial $5/$10/$15 Bootstrap themes out there.

Re: Bootstrap 4 alpha

#75
post #55
post #24

Earlier quoted context omitted.

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.

You can cut the unused styles out after.

Re: Bootstrap 4 alpha

#76
I'm not convinced that it makes sense to migrate existing sites to new versions of libraries like this unless a fairly complete redesign is happening.

Looks great though.

Re: Bootstrap 4 alpha

#77
post #26

Earlier quoted context omitted.

Wow, $99.

$99 to have your site look like hundreds of others? No thanks.

$99 to roll out an internal dashboard in hours, so my engineers can focus on more important things? Yes please.

If this is for your personal webpage, $99 might be too much. If this is for your business, and $99 can save you more than an hour or two of employee time, it's a steal.

Re: Bootstrap 4 alpha

#78
post #28

Flex! fantastic. I have no opinion but am curious about why you bailed on Less and committed to Sass. If you see this, can you explain?

From their brief description it seems like it's because Sass is more powerful and faster to compile.

It's definitely more readable. Some of the workarounds less forces upon your code get downright ugly.

Re: Bootstrap 4 alpha

#79
post #30

They seem pretty confident about Sass; It seems outdated and clunky to me, in part because it's always going to be the only Ruby dependency in any of my projects. The Javascript parser never found parity from what I know. By contrast, PostCSS is faster and has massive adoption. Seems like the way forward. Anybody think this is wrong? > PostCSS can do the same work as preprocessors like Sass, Less, and Stylus. But Pos…

I've been hearing a lot of noise about that. As a person who went from LESS to SCSS, is there any reason I should again switch my focus to PostCSS?

Because PostCSS allows you to write future spec compliant code, unlike sass. It's like writing ES6 then using a transpiler to generate ES5.
Post reply on HN