4 ms·

Bootstrap 3 or 4 are much more sophisticated and cover a lot more edge cases. Just comment out what you don't need in Sass. There are few projects that require

Bootstrap 3 or 4 are much more sophisticated and cover a lot more edge cases. Just comment out what you don't need in Sass. There are few projects that require the legacy browser support from v1.

claviska 9y ago
Problem is like I described here: https://davidwalsh.name/shoelace-css https://davidwalsh.name/shoelace-css TL;DR – most people just use the bundle because they don't want to setup a preprocessor.
- SippinLean 9y ago
  Certainly hasn't been my experience, I can't think of a single project in the last 5 years that didn't use a preprocessor. Personally I would never go back to not using one. It's incredibly easy to set up and you have to set up a postprocessor anyhow.
  - ythn 9y ago
    This sounds like a statement made by a professional web developer. A lot of non-web-developers find themselves needing to throw up or maintain a basic website for this or that, but the web development scene is a freaking nightmare. > It's incredibly easy to set up Yeah, once you've spent a few hours reading up on the latest docs. That's like me saying saying to you "Building a customized linux kernel for any hardware is incredibly easy with Yocto Project"
    - SippinLean 9y ago
      There are GUIs for Sass now that require 0 knowledge of the command line. I think Prepros lets you drag and drop a folder and click a folder watcher button. `gem install sass` + a basic Gulpfile isn't that hard either. https://github.com/joe-watkins/gulp-sass-starter/blob/master/gulpfile.js https://github.com/joe-watkins/gulp-sass-starter/blob/master... Although you're correct, I meant in a professional environment. Id be quite surprised if I caught one of my devs not using a preprocessor.
  - claviska 9y ago
    Many of us pro devs have boilerplate build scripts that make setting up a new project easier. I've done this for many projects — but one day I look forward to NOT using one. For enthusiasts, most really do load the entire bundle via CDN. For Bootstrap 4-alpha6, that's 192KB of CSS and another 47KB of JavaScript. They just copy and paste and override the raw CSS. Many don't even know what a preprocessor is, much less how to set one up. Now they don't have to.
    - SippinLean 9y ago
      Bootstrap 4 Full CSS over CDN is 23k minified & gzipped. There are Sass GUIs for novices, but you're correct I was referring to professionals. I don't understand the appeal of not using a build script, and, say going back to adding browser prefixes manually one-by-one? There's no benefit other than the hour you save at the beginning of your 3-month-long project editing your gulpfile.
    - claviska 9y ago
      Totally agree. Preprocessors still have a place in many projects and there are tools such as CodeKit that make them easier to manage for non-devs. But I never said this project wasn't bleeding edge. It will only become more relevant as browsers evolve :) BTW - Shoelace is only 7.9KB min/gzipped.

Bootstrap 3 or 4 are much more sophisticated and cover a lot more edge cases. Just comment out what you don't need in Sass. There are few projects that require the legacy browser support from v1.

claviska 9y ago

Problem is like I described here: https://davidwalsh.name/shoelace-css https://davidwalsh.name/shoelace-css TL;DR – most people just use the bundle because they don't want to setup a preprocessor.

SippinLean 9y ago
Certainly hasn't been my experience, I can't think of a single project in the last 5 years that didn't use a preprocessor. Personally I would never go back to not using one. It's incredibly easy to set up and you have to set up a postprocessor anyhow.
- ythn 9y ago
  This sounds like a statement made by a professional web developer. A lot of non-web-developers find themselves needing to throw up or maintain a basic website for this or that, but the web development scene is a freaking nightmare. > It's incredibly easy to set up Yeah, once you've spent a few hours reading up on the latest docs. That's like me saying saying to you "Building a customized linux kernel for any hardware is incredibly easy with Yocto Project"
  - SippinLean 9y ago
    There are GUIs for Sass now that require 0 knowledge of the command line. I think Prepros lets you drag and drop a folder and click a folder watcher button. `gem install sass` + a basic Gulpfile isn't that hard either. https://github.com/joe-watkins/gulp-sass-starter/blob/master/gulpfile.js https://github.com/joe-watkins/gulp-sass-starter/blob/master... Although you're correct, I meant in a professional environment. Id be quite surprised if I caught one of my devs not using a preprocessor.
- claviska 9y ago
  Many of us pro devs have boilerplate build scripts that make setting up a new project easier. I've done this for many projects — but one day I look forward to NOT using one. For enthusiasts, most really do load the entire bundle via CDN. For Bootstrap 4-alpha6, that's 192KB of CSS and another 47KB of JavaScript. They just copy and paste and override the raw CSS. Many don't even know what a preprocessor is, much less how to set one up. Now they don't have to.
  - SippinLean 9y ago
    Bootstrap 4 Full CSS over CDN is 23k minified & gzipped. There are Sass GUIs for novices, but you're correct I was referring to professionals. I don't understand the appeal of not using a build script, and, say going back to adding browser prefixes manually one-by-one? There's no benefit other than the hour you save at the beginning of your 3-month-long project editing your gulpfile.
  - claviska 9y ago
    Totally agree. Preprocessors still have a place in many projects and there are tools such as CodeKit that make them easier to manage for non-devs. But I never said this project wasn't bleeding edge. It will only become more relevant as browsers evolve :) BTW - Shoelace is only 7.9KB min/gzipped.