Kanbaru 🌟 (one hikari of too many)

megacorp-scale software projects are so unsustainable. if your project's source code is larger than a gigabyte or takes more than a few minutes to compile… god, i'd rather sacrifice a months of my time writing a smaller alternative than have to suffer through building it

3 replies →
3 replies

abadidea

(replying to Kanbaru 🌟 (one hikari of too many))

@hikari I refuse to believe that anyone, anywhere has ever actually compiled chrome. the binaries are some sort of divine artifact

2 replies →
2 replies

Saagar Jha

(replying to abadidea)
@0xabad1dea @hikari https://github.com/chromiumembedded/cef-project#build

abadidea

(replying to Saagar Jha)

@saagar @hikari why... is the first word I see "spotify"

Saagar Jha

(replying to abadidea)
@0xabad1dea @hikari So the thing with CEF is that it takes forever to build so basically the official way to use it is you download Spotify’s precompiled binaries and ship those

Kanbaru 🌟 (one hikari of too many)

(replying to Saagar Jha)

@saagar @0xabad1dea this is also my friend (@AmyZenunim)'s solution to having ANGLE as a dependency. divine artifacts, from hell

✰ Alice D. ✰

(replying to Kanbaru 🌟 (one hikari of too many))

@hikari @saagar @0xabad1dea yep. I have a GitHub Action compile the library for all the platforms I need and then upload them as binary blobs to the repo afterwards. compiling them all independently would be a full-time job 🥲

Ridley @ WATCH LYCORECO

(replying to abadidea)

@0xabad1dea @hikari back at plex we compiled chromium, at least

tamas 🦀

(replying to Ridley @ WATCH LYCORECO)

@rcombs @0xabad1dea @hikari 🫠

tamas 🦀

(replying to tamas 🦀)

@rcombs @0xabad1dea @hikari FWIW I agree with the take the binaries are not real and divine artifacts instead

Kanbaru 🌟 (one hikari of too many)

(replying to tamas 🦀)

@tamas @rcombs @0xabad1dea give us this day our daily build, and forgive us our vulnerabilities, as we forgive those who exploit ours,

Saagar Jha

(replying to Kanbaru 🌟 (one hikari of too many))
@hikari @tamas @rcombs @0xabad1dea Clearly making Chrome impossible to build is meant to be a barrier for exploit developers

eilidh :kfgreen:

(replying to Kanbaru 🌟 (one hikari of too many))

@hikari i hate to say it but i have compiled firefox once (1 time) and it sucked very badly

Kanbaru 🌟 (one hikari of too many)

(replying to eilidh :kfgreen:)

@doe a friend of mine, who will be left unnamed to protect the innocent, has been essentially continuous maintaining a local fork of firefox (she has a small patch that adds a feature she relies on), so she has to regularly rebuild it. i can't imagine doing that to myself.

Saagar Jha

(replying to Kanbaru 🌟 (one hikari of too many))
@hikari We thank you for your service

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

(sorry, i am once again venting about ANGLE… but this may as well be about LLVM or <insert large, Google-sponsored project here>)

1 replies →
1 replies

Saagar Jha

(replying to Kanbaru 🌟 (one hikari of too many))
@hikari Wait LLVM is actually easy to build though, all you really need is CMake and a bit of patience

Saagar Jha

(replying to Saagar Jha)
@hikari Ok to be fair its source code is very large and it takes a while but like on the hierarchy of how much things suck there’s like

* ./configure && make && sudo make install
* Some simple custom build script
* CMake
* Download the internet

and LLVM is in category 3

Kanbaru 🌟 (one hikari of too many)

(replying to Saagar Jha)

@saagar yeah I completely agree (https://social.noyu.me/@hikari/statuses/01H5HXKCVRJWEY246KSV4XXR5A). an LLVM checkout may be at least 2GB in size and it might take an hour to build, but it is a single git repo, uses a normal build system, and is at least partially modular, so it's not too bad. i've worked on multiple projects that integrate it

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

@saagar also LLVM has this amazing thing called OFFICIAL BINARY RELEASES that Google have never heard of

1 replies →
1 replies

Saagar Jha

(replying to Kanbaru 🌟 (one hikari of too many))
@hikari Binaries? You mean the things that exist to run on servers?

Kanbaru 🌟 (one hikari of too many)

(replying to Saagar Jha)

@saagar facebook voice binaries? you mean the multi-gigabyte blobs we have to use BitTorrent to distribute to our datacentres?

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

@saagar so yeah it was definitely unfair of me to so much as utter LLVM in the same breath as ANGLE or Chromium

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

have any of you noticed how few dependencies touchHLE has, considering all the things it needs to do, and how it can be compiled in less than quarter of an hour even on an underpowered dual-core machine? that's my way of fighting back against compile-time and source-code bloat.

1 replies →
1 replies

eater

(replying to Kanbaru 🌟 (one hikari of too many))

@hikari but llvm is a dependency, check mate atheists /s

Kanbaru 🌟 (one hikari of too many)

(replying to eater)

@eater LLVM is not a dependency of touchHLE! I considered using it for reading object files, and I do have a branch somewhere which does use it for that, but I was able to find a much more lightweight alternative

eater

(replying to Kanbaru 🌟 (one hikari of too many))

@hikari rustc can work without llvm?

Kanbaru 🌟 (one hikari of too many)

(replying to eater)

@eater oh i see what you mean, but i don't have to build rustc myself at least

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

Google projects are a special beast though. LLVM has the scale of a Google project but they are not so arrogant as to think that only a Google engineer would want to download or build it.