Discussion
getting ready to build firefox and they won't fucking tell me which build option builds the whole damn thing from source
looking around. find this page: https://firefox-source-docs.mozilla.org/build/buildsystem/slow.html
Why the Build System might be slow
if i wrote shit like this at twitter inc, our engineers would have said the build team is wasting their time and just written their own modules in scala sbt
it's unprofessional is what i'm saying. and it's implicitly disrespectful towards the build and deploy process as a critical component of delivering the product. i don't know what the hell engineers are thinking when they have to wait for builds to complete. i think they seriously believe firefox is bigger than the fucking twitter monorepo
this is a pattern of behavior for mozilla, defining these arcane ridiculous systems nobody understands. it reminds me of how the first two iterations of SSL (the first by ElGamal, the guy with the cryptosystem named after him) were too obviously backdoored to release to the public. and that was netscape, which is now mozilla, which is now google, who refines the approach to produce TLS 1.3, guaranteed to induce a state of complete overwhelming nihilism, like a curse laid upon a treasure stolen by indiana jones
i think v8 is probably easier to turn into a new language. but chrome has too much google all over it. firefox still has the love
@hipsterelectron oh hey another former pants dev in the wild! that was my full-time job at square around 2014–2016, as half of the two-person java monorepo build team. we were egregiously understaffed lol
@gwenverbsnouns OMG YOU'RE A REGEX WITCH I HAVE SO MANY THOUGHTS AND FEELINGS ABOUT REGEX
@gwenverbsnouns as in the RE2 maintainer and i were hacking on re3 together before a sudden tragic accident. i had to refile a very lengthy tweet (i call fedi posts tweets) into a blog post just a few hours ago
Install bonfire.cafe
Get the full app experience
