Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bootstrap 4 alpha

blog.getbootstrap.com

Post reply on HN
Print view View original

11–20 of 216 posts

Re: Bootstrap 4 alpha

#12

Post by StavrosK »

o_____________o wrote: post #9

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…

If I'm going to have to choose between Ruby and Node as a dependency for my project, I'll go with Ruby, and be unhappy regardless. Installing a whole programming language/framework and package manager just for a transpiler isn't my idea of fun.

Re: Bootstrap 4 alpha

#13

Post by not_with_retard »

o_____________o wrote: post #9

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…

Ruby? Yeah sure, if you're a sucker. https://github.com/sass/libsass

Re: Bootstrap 4 alpha

#15

Post by bpyne »

I'm a Boostrap lightweight, but I always respect an organization willing to drop support for old technology (IE8) and rewrite libraries with an improved technology (ES6).

Re: Bootstrap 4 alpha

#16

Post by mbreedlove »

o_____________o wrote: post #9

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…

They mentioned they're using libsass, a C/C++ port of the compiler. Although it's only an issue if you're using the source and not the compiled CSS. The same issue exists with v3 needing a LESS compiler.

Re: Bootstrap 4 alpha

#18

Post by thegeekpirate »

o_____________o wrote: post #9

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…

There's no reason to use Ruby https://github.com/sass/libsass

Re: Bootstrap 4 alpha

#20

Post by tmcdonald »

o_____________o wrote: post #9

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…

v4 will compile with libsass by default. You can set the TWBS_SASS environment variable to use the Ruby compiler if desired.
Post reply on HN