It was the mouse pad. 35 losers who spend their waking hours trashing Canada and one who is critical of "improper display and use of the national flag." And then one competing tuber.
10 seconds into the video and that is so spot on. It was frustrating to look up videos on RU-vid about SASS because some don't mention that they are actually using SCSS and I think they should write that and not just SASS in the title. idk they look different so would help to distinguish between videos. Only looked into .sass, just know that there is different syntax for .scss.
I do it too... so sorry about that. It's because people will say Sass, even if they are referring to SCSS, even if just talking. Specially with SCSS being far more popular, it's just sort of synomimous with saying Sass now. It's the same language, just a different syntax... but yeah, 100% can be confusing.
i came to this video because i was watching another one of your vids and thought scss looked interesting, now i feel a bit more inclined to learn because i like how it flows :3 Thanks for the vid!
I personally think SCSS is better. The structure and nesting looks clean plus code editors and libraries like React natively supports it. Also you can't do much in the 5 seconds you saved by not putting curly braces in your SASS file
As a python developer, I've always struggled to see it that way. When newlines and semicolons provide essentially the same information, the semicolon is just clutter to me. the same goes for indentation vs curly braces. True, it's silly to argue about "time saved", but aside from the CSS compatibility arguments, I honestly can't see an advantage of SCSS
@@Mephistolomaniac curly braces add structure and readability for me, I hate trying to read python code. Also i love semicolons as well, they just look right to me. Even though I use JavaScript and technically don't have to use semicolons, i always do. Not using them is like a sentence without a period, i can read it just fine but somethings wrong in my head
@@skylarkesselring6075 same, I always use semicolons in javascript, and even if I don't, prettier will add any missing semicolon everytime I save/format the code
I hate SASS and love SCSS just because SCSS has brackets which I can trace where it starts and where it ends. I click the opening bracket and my Atom editor highlights where that bracket closes which makes it super easy. I'd switch to SASS only if there a way to tell what the fuck is going on, where does something start and where it ends
I'd been using SCSS becuase I was converting a lot of old projects and it's a lot easier to import and get rolling. And when you don't know what to do with part of a project, you can just leave that old CSS in there while you upgrade the project.
Id like to see more of you talking in your code editor instead of you talking, was pretty straightforward and to the point while you were talking in the code editor which is great
My question is, for someone like me who is new to the whole web development scene . . . is there a reason to use CSS at all if you can write exactly the same code from SASS and SCSS can accomplish the exact same thing? I see the css file itself as kind of an afterthought! I like the SASS approach, it feels pythonic . . . from importing other files to the indentation . . .
I mean, if you do write sass or scss, you will need to compile it into CSS anyway... Also, if you do sass or scss, you will need to know the syntax of CSS, because it's really similar except for the nesting and imports. Being someone quiet new to web dev, i would say that it's important to know the "classic" approach, but I prefer to use scss, it's just so much cleaner that stock css
@@Colnup i'm starting to wonder about that lol. I know I know . . . learn all the coding, no shortcuts . . . and when it comes to avoiding using snippets for the first few months of a full fledged language weather it be C or pyghon or java . . . i do get it. But css . . .vs scss . . . its not like scss or sass are gonna go anywhere. You can run Koala and auto compile, but why bother with css when scss is damn near identical but with added functionality. . . like you said, the differences really lie in the nesting . . . and scss adds variables which are a huge time saver, and don't require much of a learning curve. You can literally plug in a new color scheme or fonts or whatever in a matter of seconds, and yeah, in a modern text editor you can do it anyway, but still . . .as you said, scss . . . even sass . . . are cleaner.
Why would I write curly braces and semicolons if I'm not required to? SASS is a lot less of needed keystrokes. And the Python-like syntax using indentation is just awesome.
@@KevinPowell I'm actually a C++ developer originally, with more than 8 years of experience. Only recently I'm trying to learn all this web development stuff, so in term of familiarity I should be more comfortable with SCSS, but no, SASS is sexier... :-D
It has it's downsides for some things, like *having* to make a new line... sometimes I like doing single lines for some things, if It's just one property on it. But it's a small sacrifice :)
I really don’t understand why some people think that SASS is more “difficult” then SCSS. I’m not talking about you, of course. But even for a beginner, if they think that SASS is complicate, is better they rethink if development is their thing....
It's not that it's difficult, but if you are familiar with CSS, it's a super simple transition. When you write Sass, your mind is still deep in the CSS mode and it's a bit of an adjustment to stop putting semi-colons or curly braces for the first bit of time writing it, which can be frustrating. I know the feeling of going that way, and then writing regular CSS, I'd keep missing them and it drove me nuts, lol. Took me awhile to transition back the other way too.
i like sass, but i still use only css. the reason is easy. I like when i can do small change and i can see the result. I dont want compile everytime when i change something. maybe i change font size to little bit bigger and with css i can see result in second. Can Sass do it? Can Sass after saving file show the result?
its funny, you say it saves you keystrokes but..... you are accidently doing the ; so its double the keystrokes when that happens xD BUT this is a good video and easily explained, good video! I rate 5 stars
It raises the specificity, which can cause issues as projects scale up. If you limit it, it's not the end of the world, but deeply nested selectors like that can cause issues with maintaining your code in the long run.
But what's the difference? SCSS is like a fork of CSS? and SASS is the compiler? It could be better if you use some infographics. I saw the cool coding you made in SASS Meister and the equivalent on regular CSS but I didn't the concept of both. If we want to work locally, do we need to download some plug in? Sorry, this video did not meet my expectations like other yours!
Sorry about that! SCSS is like a fork of Sass, yes :). They both do the same thing, but use a different syntax. To work locally, you need something to compile the Sass/SCSS to CSS. There are extensions/plugins for editors, you can do it with gulp, or there is software like Prepros and Codekit. I've used all three (and I think I have videos on all 3 as well)
Sass looks so complicated. You need things to be fast and quick when trying to style a site and not trying to compile and add more files for buttons etc for no real reason....
@@Schattenrufer007 nothing in common? not even their approach to relying on spaces and nesting to delimit their blocks? 🤔 Of course all three target different use cases.
