WELL FUCK YOU TOO!

Grunt, gulp, bower, webpack, rollup, yarn, npm, requirejs, commonjs, browserify, brunch, rollup, parcel, fusebox, babel,
wrappers for bundlers, frameworks on frameworks, then for css, theres scss, sass, less, stylus, compass, and for templates, handlebars, mustache, nunjucks, underscore, ejs, pug, jade, and about five billion other word-salad tools, all with their own CLIs, each in some way building on npm, but with their own non-congruent little syntax, like no one realized they were reinventing the same problems introduced by domain specific languages, most happy to announce "configuration takes a little time, but it's worth it!"

No, it's not. Just stop people. Just stop. You're not doing anyone any favors by creating another lib, all you're doing is tooting your own horn and self promoting. Use what exists and stop creating more shit for new people to learn, to add to the giant clusterfuck that is the 2019 hotmess known as "web development."

You're not special. You're not important. You're lib or tool will be famous for 15 minutes and no one cares what you've made.

If you want to contribute to web development, do us all a favor and contribute to global sanity by kindly deleting your contribution and any plans to contribute new solutions to problems that have already been solved.

Going through a new hire's code, CSS noobs be like...

Dear coworker,

We have a very nice SASS setup so WHY THE FUCK ARE YOU POLLUTING OUR HTML WITH INLINE STYLES!?!?!? It's not like it's even necessary to use inline in this case, I can achieve the same thing by just moving your styling to the scss files. So I ask again, WHY THE FUCK???

Sincerely,
A mildly pissed person who hates front-end dev work

It really irks me when I see 'web developers' and 'front-end developers' write CSS like a bunch of first-timers. Not considering hierarchy, specificity or even following a proper naming convention (who the fuck mixes camel case AND lowercase for class names?!) It's worse when you already have Sass or SCSS and they still write their style rules WITHOUT PROPER NESTING or keep using !important like it was a goddamn semicolon.

This is fucking basic shit for a web or front-end developer, and God help you if I ever conduct your technical interview and decide to ask you on a whim to write an Angular app WITHOUT USING BULLSHIT SYSTEMS LIKE CLARITY, ANGULAR MATERIAL OR BOOTSTRAP for your UI. But if you can explain to me the pros and cons between using CSS grid and flex, I'll be fucking impressed.

I wish these 'UI experts' I keep encountering would learn to build an optimal static site without a fucking framework or build manager before doing advanced shit, for the love of Jeebus.

display: inline-block is a work of satan

Have I told you that I love Sass? Yes? Well, that's fucking true! Like today I decided to host the used font myself and just include all font-awesome SCSS into my main.sass and saved one <link>. That boosted loading time and user don't have to see those ugly squares while page is loading. I'm truly in love.

At first I was like "meh.. SASS is not really that different from css really.. maybe this wont even help any.."
But now I'm like "dude holy shit please never let me work without SASS/SCSS again!" :D

How competent I feel today experiencing the WebDev world?

I've nearly gone insane editing my CSS code, not noticing any changes at all on my website whilst spamming F5.
Luckily, before I was beginning to plan my suicide, I realized that I was editing SCSS the entire time, having my auto-compiler turned off.

First job as a web dev (promoted within my company from helpdesk!!!!). I made it explicitly clear that my php experience is rudimentary and that I was still learning and our CIO was fine with that, just said I need to fast track learning.

In my first website support meeting today they dropped all kinds of fun stuff about Wordpress development that I only know the basics on and is now my responsibility to learn, so:

How the hell do I learn php/scss/sass/docker for Wordpress really fucking fast? Lol

I'll be the only one who prefers to use .sass syntax over .scss?

When you thought you know CSS and then find a template with perfectly orginized scss...

Taking quick naps between GULP compiles is a thing right?

OMG!! the SCSS is so Sassy..... perfect name for an extension....

SASS : Syntactically Awesome Style Sheet.

I wonder what this guy(the guy who named sass) named his child/pet

I wonder why the css class inside the css file throws an angular compiler error at '{' ... shit, it was configured with sass, not scss 🤦

SassScript, because where else to show your programming skills than stylesheets

Which is your favourite compiling CSS language for development ?

• none (CSS)
• SCSS
• SASS
• LESS
• ???

My is SCSS.

1000 lines of css is still smaller then most images optimized for modern displays (aka everything that isn't a thumbnail). Either our designers don't come up with stuff complex enough to validate adding a compilation step to interpreted code or I'm missing something,

I've been looking into CSS preprocessors. Can anyone give me an example of why you'd use one that isn't some lame programming platitude like "pushing technology forward"? Like an actual design element that can't be done in straight up CSS?

As someone who compiled AS3 for the web back in the day the "new wave" of internet technology (with all it's compilation steps) seems super dodgy.

Do you use nesting in the scss / sass / less files of your project?

Any good SCSS beautifiers? Those that I've tried so far screwed up syntax.

if css is a headache, could the use of sass be worse?

So i want to get into css preprocessors. Which one is a safe bet ? I thought less would be cool, but sass and scss seems to be becoming the industry standard ...

I don’t know if they really don’t want Sass or if they’re just scared to try it.

Not all new techs are horrible.

Hope one day they will realize that using CSS preprocessors is way better. And it’s not that as complicated as it sounds. Jesus Christ.

@ pro-CSS frontends, any thoughts?

Hi, in my latest project I'm stuck on the CSS part.

I've already an Grunt + Sass Asset Generator for bootstrap.

The project has several (> 70) subpages aka modules.

The theming is client based, currently 4 clients with different colors.

At first I thought it was easy...

Splitting bootstrap to variables per client + bootstrap, so:

client1_variables.scss
client1_bootstrap.scss (including client1_variables).

client2_variables.scss
client2_bootstrap.scss
. . .

But now I'm stuck.

Reaason: The css classes are the same between the clients, eg client-bg-primary is the class.

I wanted to prevent generating for each client a folder - as every folder would contain the same content:

module/news/client1.scss
module/news/client2.scss
module/news/client3.scss

module/dashboard/client1.scss
module/dashboard/client2.scss
module/dashboard/client3.scss
...

Each SCSS file would only differ in the variable import...

Is there a way to prevent a Global Module CSS file for each client (as there are @##* fucking classes duplicated and I really don't want to untangle that mess) but not ending up with writing the same Code over and over?

The IRC sass channel is moderated, not possible to ask there... And when I google I find mostly themes based on an class approach (border-light vs border-dark)… :(