I prefer the first example that he says is crap. It has all the arguments grouped together to make it slightly easier to read. I don't buy the argument about w

I prefer the first example that he says is crap. It has all the arguments grouped together to make it slightly easier to read. I don't buy the argument about wasted whitespace. If you cramp too much of your code into dense one-liners, it makes the code unreadable. Secondly, I'd say that code width is unnecessarily narrow. 120 characters is fine to fit two files side-by-side on a 1920x1080 monitor with space to spare. 80 characters is just too close. Thirdly, I'd typedef "struct wlr_surface" to "wlr_surface_t" (assuming I were writing this in C. I don't know if this is actually CSS)