Today we're releasing two variable open source fonts from @GitHub, Mona Sans and Hubot Sans. We use them in production, and now you can use them too.

RT @david_dossett: 📣 Want to design and build VS Code with some of the most talented software makers in the world? The team is hiring not o…

@PeterRosdahl Pratar gärna! Lutar dock lite mer åt text/kod i och med jobbet (Copilot), men nördar gärna ner mig i allt 😌

@johnnyrodgersis Sublime ✨👌

RT @sillyalexnorris: still trying to reach the goal for my comics legal fund 💕 fighting on and feeling hopeful x h…

@Coulianos @X Same same - had to switch to using the Following tab and it’s such a breath of fresh air

@adamwathan @jacobmparis Man, seeing a nuanced discussion that (correctly) highlights a potential issue with our implementation is 100% a gift 🎁 just grateful!

@jacobmparis @adamwathan I���m responsible for this page on GitHub and… I have to agree. These two should flip (h2 should be Application Security). They should follow abstraction level and specificity, not visual hierarchy

@pumpkin Hope we’ll be able to wrap up the the last fixes this week—then we’re looking at 4-8 weeks before it lands and propagates through Google Fonts and the G Suite. So no promises on dates, but Soonish™ 😌

@haacked My impression was talks that were much more aligned towards a full stack JS focus 👀

@edimoldovan Hi!! Thank you! And not 100% sure if I’m following—but the utilities are intended to be used to scale from one value to another, so never matched as “h1-min h1-max” (doesn’t scale), but as e.g. “h6-min h1-max” (scales from 6 to 1). Is that the crux??

@renevdlende What I’m saying is that you can’t perform that calculation under the current restrictions of calc. You can’t just replace the 1px conversions—you need one extra conversion (max size - min size needs to be in rem), which breaks the calculation, since you’ll have rem * px

@renevdlende ...and since the product of the viewport division comes out in pixels, it needs to be multiplied with a unit-less number, which means you can't multiply it with rems, or ems, etc. That said, if you get to work, that would be wonderful!

@Akshat_Giri CSS calculators solve the most basic use cases, but you can’t compose freely with pre-compiled utilities, and if you want to change your setup you need to return to the calculator. The entire premise of this technique is to avoid that—will share some more advanced examples later

@xhfloz Oh dear, that’s why!

Again, all the details are here: a significant limitation of this technique right now is that we can't use rems (this only works with pixels), but that should be resolved with the relaxed CSS calc() specs 👀