@lanodan @Amikke when someone unironically uses bazel to build a project

t. anki

@icedquinn @Amikke anki to me goes together with the npm software junkies that can't control their dependence.

@lanodan years ago when I was using Gentoo, webkit2gtk, the qt equivalent, Firefox and Chromium all came at somewhere between 40 minutes and 2+ hours. I think Chromium was the worst offender, Firefox being on more or less webkit2gtk level. That was around FF 58 though.

@Amikke That quite changed but I banned so much of modern software that firefox/chromium just isn't an option anymore.

webkit-gtk keeps at around 30~45 minutes for me so it's reasonable-ish.

@lanodan so as per usual, everything related to web front-end is pure cancer

@lanodan
AND have more or less recent Node.js available on your platform 😅
@Amikke

@m0xee @Amikke oh lol, that's new to me. Kind of fun that you need chromium's JS engine to build Firefox.
(chromium itself also needs nodejs…)

@lanodan
It's also ridiculous from portability perspective — who cares if your software is cross-platform, who cares if even Rust is — you can only build it on platforms that Google cares to support. I mean, you can always cross-build — but that makes building it even more complicated, I've even cross-compiled Firefox with xbps in Void, but to me it looks like tremendous job was put into making it work and I'm not even sure all the platforms are still supported 😩
@Amikke

@lanodan
I remember the days when to build early versions of Firefox (and the whole Mozilla suite too) you just had to run the "configure" script, then "make" — just like every other software. V8 didn't even exist. 64 megs of RAM was okay and with 512 you could never ever close any tabs. We can't do any new things with computers nowadays, everything just got slower and more bloated.
@Amikke