Oh you mean Android Studio automagically "updating" your versions so that your build breaks and you spent 3 hours figuring out what just happened without you even touching anything?
this post was submitted on 29 Sep 2024
244 points (92.7% liked)
Programmer Humor
19289 readers
1186 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
side note, it's badass to see a gpl3 licensed game on steam, and a paid one at that!
It's a great game too, I used to play the mobile port, it's absolutely worth 10€.
Most sane android developer
Maven and Cradle might be terrible, but C and C++ have fucking nothing in terms of dependency management. Even C# has something that few people use, but it has something. C and C++ are such a shit show to build. It's so bad they had to invent languages to build them and they regularly fuck up (CMake, make, bison, scons, meson, ...).
Pull a C or C++ project on a distro or environment and try to build it and you have to dive in the abyss of undeclared dependencies. And good fucking luck with glibc and glib dependencies. If the dev doesn't know which version they were actually using, it's up to you to find out. Fun for the entire family!
Even C# has something that few people use, but it has something.
Huh? Are you claiming few people use NuGet?
NuGet is nice
To be fair, C predates dependency hell. It was either there or it wasn't. C++ has less of an excuse, but it was just object oriented concepts taped to C so it's no surprise it was also missing dependency management.
Now with cmake, gnu-make, meson, gradel, and the world of metabuild systems that wrap those, nothing will change. It it does, it might as well kick start world war 3.
I remember having to use something called Conan once, which was also quite broken. Though the devs were fast to respond with fixes and workarounds.
That's odd... all the projects i use document their install process fairly well, most of them using either cmake or autotools.
The only "terrible" scenarios i occasionally encounter is, yes, trying to automate the android toolchain - i blame Google though, not C/C++ as the Android toolchain is intentionally designed to be used with Android Studio and trying to veer of that is increasingly harder.
Even cross-compiling for windows isn't that bad.
You forgot automake.sh to the list of ways to solve the problem that still suck
Rust and Cargo enters the room.
come develop Golang , its good here.
... and other ridiculous cope statements to laugh about
I am in this post and I don't like it.
I'll take the autotools over Gradle, that's how much it sucks.
Haha this.
There's Gradle to crave joke to make here, but deploy keeps failing during dependency checks for humor.
Thank God it's not just me
Me with gh's CI
What can you expect from a social media platform ran by Microsoft & built atop YAML? It was always going to be bad.
Fair enough. As long it's simple commands it's fine, but when going to do platform builds then attach to release it's a pain.
Same