@chriscoyier
Chris is a web designer and developer. He created CSS-Tricks, a website all about building websites. Going strong for nearly 10 years, it’s a community with a blog, forum, almanac, and video screencast.
He is also the co-founder of CodePen, a playground for front-end web development. CodePen is a code editor for HTML, CSS, and JavaScript right in the browser. It’s also a community. People share what they make, write and comment about code, collect favorites, follow each other, and more. It’s a social network for front end designers and developers.
Chris is the co-host of a podcast called ShopTalk, a show about (you guessed it), building websites. Modelled after CarTalk, the show features call-in questions and industry guests. It’s going on 230 episodes!
Chris has also spoken at events all over the world and authored two books: Pratical SVG and Digging Into WordPress. The web is Chris’ life and career focus. The web is an incredible, inspiring, and empowering place and helping people know it better is good for everyone.
Nothing here yet.
No blogs yet.
If they are being implemented in browser, that's great for usage on CodePen, because it means we (and you) don't have to do any special processing to make them work. As it stands, as far as I know, people are largely using Webpack for compiling that import syntax and we do support Babel/Webpack processing: https://blog.codepen.io/projects/using-babel-codepen-project/
This is a good example of a feature we could easily get sidetracked with. I'm not necessarily opposed to it, but as far as I know, this is the only time it's ever been asked for. As a tiny team we gotta pick what we work on carefully. I think if we did something like this, it would be tied into a mini-sprint where we're focused on changing some editor UI stuff, and adding this isn't a weird detour. So: maybe!
Doesn't that seem like already the case? I can't imagine hiring someone, especially to work on the web, where you don't look around pretty widely and closely about who they are on the web. If I can see how you write words, how you write code, how you communicate with people, the stuff you produce... that's powerful. If that's out there and available for me to see, that's leg up on someone else where I can see nothing.
Probably. Although "improvements" is subjective to any particular user. I'm definitely a fan of changes that are objectively better in some form. Better business. Users measurably completing goals. Easier code maintenance. Better performance. I'm happy to endure Twitter whining for objective wins.
Never! Not only do we use it to build CodePen, it's far and away the most popularly used CSS preprocessors on CodePen. https://blog.codepen.io/2016/02/24/popularity-of-preprocessors-on-codepen/ Personally, while I like the idea of preprocessing in general, and see value in all the choices, Sass still seems to me like the best choice.