20th October 2016, 6:00 pm
Message from the host 💬
I’ve had a bunch of fun answering everyone’s questions! There’ve been some really good ones, thank you :)
If I didn’t answer your question quite correctly, or you’d like a little more detail, please feel free to ping me an email and we can discuss things further there: firstname.lastname@example.org
For anything shorter form, you can just fire me a tweet: @csswizardry
I hope you all enjoy the rest of your days, wherever you are in the world. Thanks for having me!
If we’re ever at an event together, come say hi and let’s grab a beer!
Thank you for the AMA! To be honest, I am a fan of your ITCSS and BEMIT techniques (at least what I could find out in the WWW), so I really look forward to the AMA and all of your answers!
As for my questions, here are a few which I find highly interesting:
- On CSSWizardry, you sometimes use CSS, but you also sometimes use SCSS. Do you have any pattern when to use what?
- What are your most-used SCSS features, which will probably not be replaced by upcoming CSS standards in the short-run?
- How do you decide on responsive breakpoints? For which elements do you add special breakpoints? (images, menues,...)
- I sometimes read that rendering performance can be influenced by carefully writing certain CSS selector rules. Do you think something like that is plausible, or even relevant for todays highly performant devices?
- If you could change any one way CSS is used today with a wish to a djinn, what would it be?
- I have been waiting for the release of an official ITCSS spec and the Inuit framework for some time. Can we expect anything this or next year?
I really hope you could answer one question or another. Thank you for your time and motivation to do this AMA :)
There's very little known about your personal life in the public. Sorry my questions are little personal, since it's AMA (Ask me anything). ;)
- Are you married?
- Am I invited to Harry's Bar? 😄 https://www.instagram.com/p/BAURBEPIjB3/
- What's your favorite drink?
Have been following following your talks, you are awesome! :)
Hi Harry, how are you? Thank you for hosting this AMA! Because of you our company is now using ITCSS + BEM to create scalable and maintainable web applications!
How do you normally make ITCSS 'components' responsive? I've seen the use of responsive classes, but do you ever use media queries within your component's CSS?
What are your thoughts about Atomic CSS (acss.io) and other similar frameworks that uses single purpose styling units applied via classes?
Have you ever used them in production or recommended it to your clients?
We've be working in-house with ITCSS and Inuit for bit now. How do you reconcile certain philosophical conflicts between the two?
- ITCSS: flat file structure vs. Inuit: directory-based
- ITCSS: DRY vs. Inuit: Node install requiring potential overrides (a la Bootstrap)
Many thanks for the AMA!
What are your opinions on utilising data attributes for styling? (such as http://codepen.io/SudoCat/pen/wzBzoG - shameless plug, I know, but a prime example of what I'm talking about)
A lot of people slam unqualified attribute selectors and wildcard attribute selectors, but they provide a huge amount of power to us devs, especially helping make our CSS more Object Orientated - where do you stand on the matter? (Kind of related to the above question)
I know you're a huge BEM advocate, but what about SUIT?
Is the dream of a truly clean, tidy, maintainable code base really achievable? I feel like my FED life is spent fighting for nearly unattainable goals - is there a light at the end of the tunnel?
Agencies or Products? I've been in the agency rat race my whole career, where few companies or clients value code quality. What do you think is more useful to improving your development practises, and which do you personally prefer?
I just want to take a second to say a huge thank you for your contributions to the front end community. Your blog posts have been a huge inspiration for me, and I credit a lot of my front end success to your writing and the mindset you approach CSS with.
On recent project I split up CSS into multiple files in which there were chunks of layout (e. q. base, header, main, footer..), which were loaded asynchronously after each chunk's HTML so that the page loads/displays it's bits before whole page finishes loading while preventing FOUC. Is this considered good practice at the cost of more HTTP requests?