Houdini: Maybe the Most Exciting Development in CSS • Hacker News Board

Re: Houdini: Maybe the Most Exciting Development in CSS

#61

Post by talmand » Mon, Mar 28, 2016, 8:47 PM UTC

kolme wrote: post #56

talmand wrote: post #51

Earlier quoted context omitted.

Well, it does clean up the code a bit, depending on your point of view. But it wouldn't necessarily interfere with cascade. It's just right now, because CSS doesn't support it, that SASS code gets compiled into large selectors if you aren't careful.

It helps a little in the code organization, however, it creates new problems. It makes deep nested code hard or impossible to reuse. It tightly couples style and markup, so a change in the latter can break the former, etc. So while it is a nice feature to have, I'd recommend using it scarcely and with great care.

That's not a problem, that's not understanding how it works.

Any nested SCSS is impossible to reuse outside of its parent scope. If someone is using nested SCSS and expecting to reuse that code elsewhere then they are doing it wrong. It's the same problem that exists if one were to create a class as a child of an ID and then expect to use that class outside of the ID's scope.

Re: Houdini: Maybe the Most Exciting Development in CSS

#62

Post by Raphmedia » Tue, Mar 29, 2016, 2:03 PM UTC

err4nt wrote: post #58

Raphmedia wrote: post #52

Earlier quoted context omitted.

I understand where you stand from, I've done quite a lot of work on support / upgrades of existing websites. I still think you may benefit from a workflow that uses a local build system... and once you use a build system, why not throw a preprocessor in? I can give you an exemple of my workflow for simple websites using Gulp.js (I used to use grunt.js, but really, it's all the same) I have a frontend folder structure…

That's a pretty elaborate setup. I have my own toolbox of scripts and plugins, but they're all written in CSS, HTML, and JS. I have CSS files like http://staticresource.com/basic.css upon which I can layer other colour styles like: http://staticresource.com/template/css/themes/swiss.css I also have plugins that I've written like http://staticresource.com/notifications.html But this year I decided to do something craz…

I like all those tools, plugins, etc. you have going. They are great.

As for the build system that I use, I can update it via the command line and I can also install it on any machine via npm install. I do agree that with this, I couldn't work on an iPad, but I have that 11inch macbook air for that job already.

Here's the open sourced version that is the base of my workflow (this one is the one we use where I work, my own is a bit simpler but based on the same concepts). Take a look: https://github.com/absolunet/nwayo/tree/master/src

As for the breakpoints, I use the variables as a starting point (small mobile, large mobile, tablet, desktop, big desktop, etc.) but do end up using hardcoded breakpoints for small components or in betweens.

edit: Mail me if you want to chat more, contact info in profile!

Re: Houdini: Maybe the Most Exciting Development in CSS

#63

Post by coldtea » Wed, Mar 30, 2016, 5:37 PM UTC

talmand wrote: post #27

err4nt wrote: post #24

Earlier quoted context omitted.

In my work doing frontend web development CSS is the primary language I use. I don't use Less or SASS, I just write straightforward CSS. The only limitation I've run up against as far as responsive styling goes was that @media queries were always scoped to the browser's width/height, and I figured I could build much more advanced layouts if I had a way of scoping styles to individual elements. It turns out that's tru…

Most of the time when I see people complain about CSS it's because either they don't know how CSS works, or they want it to do something it wasn't designed to do in the first place. Most of the time it's because they don't know how it works.

If you frequently see people not knowing how CSS works, then that could be a sign that CSS is fundamentally broken, over engineered, etc for what it does...

(rather than those devs being "stupid", "ignorant", "incompetent" etc).