- Dev Notes
- Posts
- Firefox’s source code is now officially on GitHub!
Firefox’s source code is now officially on GitHub!
PLUS: Stack Overflow is gearing up for a facelift.


Good Morning! Firefox just flipped the switch on its hg.mozilla.org Mercurial servers and officially moved the Firefox source to GitHub. Meanwhile, Stack Overflow is staring down a 64% year-over-year drop in Q&A traffic and is rolling out a full rebrand—AI assistants are swiping our questions and they are attempting to fight it. And if you thought Figma’s slick Dev Mode was “included,” brace yourself—teams need extra seats per project to actually use it, and that little fine-print sting is leaving freelancers feeling scammed.
Firefox’s source code is now officially on GitHub!

Context: Firefox has been living on hg.mozilla.org under Mercurial since forever—complete with its own commands, hgtags, and a separate CI setup outside most devs’ day-to-day GH workflows.
What’s new:
The canonical Firefox repo is now at https://github.com/mozilla-firefox/firefox
Legacy Mercurial servers will stay in sync for now; CI, bug tracking, and code review pipelines aren’t moving (yet)
Contributions are smoother—no extra accounts required if you already have a GitHub ID
If you’ve forked linux-kernel mirrors or poked at GNOME or LibreOffice on GitHub, this should feel like second nature. No major workflow changes, just fewer infra headaches. So grab your PR hat, skim the new GitHub Actions configs, and let’s start rolling those Gecko patches. Happy hacking!
Stack Overflow is gearing up for a facelift.

Context: Stack Overflow’s core Q&A action has taken a nosedive—April 2025 saw question-and-answer volume plummet over 64% compared to last year, and it’s down more than 90% since its 2020 heyday. AI chatbots, in-IDE helpers, and Copilot extensions are straight-up stealing our rep points and pageviews.
Stack Exchange is hitting refresh with a full rebrand that breaks the mold—they’re no longer “just Q&A.” Here’s the skinny on what they’re launching:
Three new pillars—Q&A stays, then add “Community” for open discussions and “Careers” to hook you up with jobs
They’ve already tinkered with AI Answer and Question Assistants, revamped the jobs board (thanks, Indeed), and dropped GitHub Copilot, Slack, and VS Code extensions to keep you tethered. Basically, if you’re knee-deep in devops pipelines, language internals, or framework wars, expect more AI in the future rather than old SO that we were all familiar with.

Context: You’ve probably seen Figma’s slick Dev Mode launch pitch—inspect CSS, grab tokens, spin up VS Code extensions, and generally feel like a front-end wizard. But here’s the kicker: if you work with multiple clients or freelancers, that “Dev Mode included” badge hides a team-seat trap. Pay your $15/month, sure—but only for one team. Want to peek into your client’s file? You need them to pony up too. Cue the “Figma Dev Mode is a scam” Reddit thread, where devs are fuming over hidden dark patterns and double-dipping pricing.
Figma’s doubling down on Dev Mode as a premium feature, but community backlash is real. Highlights from the trenches:
Developers report needing extra paid seats per project team, losing comments/annotations when importing into free alternatives (Pixso, Penpot)
So, if you’re knee-deep in webpack configs, SCSS mixins, or debugging that one CSS grid bug, weigh your options: stick with Figma and budget for every collaborator, or export to an “inspect-for-free” challenger. Either way, keep your Git branches tidy and your wallet guarded—because even the coolest tooling can sting when the fine print bites.
🔥 More Notes
Potential U.S. semiconductor manufacturing boom faces policy headwinds: Major investments under the CHIPS Act are fueling a domestic chip revival, but proposed tariffs and trade probes from the previous administration threaten to slow or derail new fabs in Texas and California.
Tennessee to require every high schooler to take computer science: Starting with the class of 2028, all Tennessee students must complete at least one CS course—part of a push to boost tech literacy and meet future workforce needs. Other states are watching closely.
Vision-language AI models can’t reliably handle “no” and “not”: New MIT research shows that common multimodal models stumble on queries containing negation words, raising concerns for high-stakes applications like medical diagnosis or legal text interpretation.
📹 Youtube Spotlight

Was this forwarded to you? Sign Up Here