mdo

Code review tooling has been in the works for a long time. It's sadly taking us this long to actually ship the first fundamental bits, but there's a ton that this unlocks for us. Expect to see more soon :).

(Source: I worked on code review at GitHub for awhile!)

Definitely need to do it. We tried to do it as part of v3 but ultimately left it to the community. We saw a few good things come of it, but it's on my bucket list for the future.

Our docs are built on Jekyll, which takes either HTML or Markdown for page content. Markdown is so much faster to write in for docs, especially since we no longer have to escape inline HTML by hand haha.

We've got them! See http://v4-alpha.getbootstrap.com/components/forms/#custom-fo... :).

Also see https://news.ycombinator.com/item?id=10088173.

Happy to explain!

- Sass has a larger community of developers. - Sass seems to be iterating as a tool faster than Less. - Sass is really similar to Less, so it's an easier transition to make than jumping right to PostCSS. - LibSass (the C implementation of the traditional Ruby Sass) is super fast, faster than Less in my casual tests).

No plans :).

Thanks! <3

What specifically would you like to know?

Oh, I removed the CSS for those and forgot to remove them from the docs :grin:.

Definitely not. We're in the alpha stage. Things won't be locked in until maybe beta, but for sure the release candidates.

Hell yeah, we love doing it. Keeps us fresh and interested in the ongoing development of the project and helps push other folks forward with new web patterns, tech, etc.

Hah, happy to hear that. Thanks!

We had so few IE8 specific hacks. I don't think it really made a large impact honestly.

Thanks for noticing! :)

I spent a lot of time deleting stuff lol. Still more to optimize around though as we work through the alphas.

Yup! Lots will be a little broken until we get into the beta phase. Still tons to do, but we wanted to get this out there :).

Set an HTML font-size—likely 16px—and use body { font-size: 1rem; }. Allows for easy media query scaling of type.

All of GitHub is basically in pixels, save for our Markdown styles—for easy modification across devices, we use `em`s. It'd be a huge project to update that to `rem`s anytime soon.

Yup, see my comment above or below this. I'd find the tweets about it, but blah, Twitter search.

We got Paul Irish to re-open the bug after they made the change to their font rendering. It is indeed a bug and has been fixed.

Might be boring to you, but it isn't to us. This is (part of) our job :).

When I stopped to think about it, there was honestly no reason to not open source Primer. If the goal of open source is the share and learn and improve, then what does it matter what we release? Especially as open source?

The number of frameworks of any kind has no bearing on the willingness of more people to share their knowledge and experience with the open source community. I'd write 10 more CSS frameworks if it helped just one more person make something they loved on the web.

That is one of the reasons—you can view the slides also at https://speakerdeck.com/mdo/at-mdo-ular-css if you don't want to watch the video.

I like to use prefixes and base classes. It's faster for browsers to paint, leads to fewer rules overall, reduces selectors, and helps prevent unnecessary overrides.

Hah, yeah, nothing to rebuttal there lol. We're forever facing problems with that kind of stuff.

Absolutely no problem with vertical padding—this particular problem is a Chrome bug.

This is due to a Chrome bug with how they render Helvetica. We could hack it ourselves, but it's a regression on their end and it'd just be more work for us.

I mentioned it above, but we're working on that. No idea when it'll happen as it's a bit more involved than that, but it will eventually.

> I wish GH remembered the ?w=0 preference just as it remembers to use the split diff.

Me too! I'm working on that, but it's a bit tough as it changes the order of the lines that are rendered in the browser. Thus, code comments would kind of be borked.

Bottom line, lots to rewrite before we can do just that, but we are 100% aware of it.

Whoa, I never thought about that. The colorblindness thing is exactly why we haven't tried to remove the +s and -s, but if there are indeed colors that we could attempt to use, that'd be awesome.

Hah, been here for nearly two years now :). And no spoilers!