Fuck project setups that

- Have huge nested enterprise folder structures like Java

- Use tons of shell scripts / makefiles

- Have every config file in the root folder

- Don't tell me what I need / how to build

I know some of these can't really be changed easily, but fuck this cluttery mess!

Wow!
Makefiles are SO much cooler than I thought before

$< = the first dependency file
$^ = all the dependency files
$@ = the build target

AND if I try to build something who's dependencies don't exist, it'll automatically try to build them!

After working 3 years in my current job and my boss hating anything to do with unit testing etc, I used my spare time to refactor our Makefiles to allow for the creation of unit and integration tests. I technically didn't tell my boss about it, so my heart was in my throat when he Skyped me with 'what did you change in ...'?

After having bashed any workflow with testing in it, I showed him the new workflow and automatic testing in Jenkins and he was actually enthousiastic, just like all other employees! I was hailed a hero in the R&D department, after all this time we can finally write universal tests. :D

REDIS: Great for cloud, will fuck up your local disk if too many write operations per second.

DynamoDB: WTF 10Mb should not be "too large for a single record"!!

SPARK: NEVER CONNECT IT TO A DATABASE! Wasted A LOT of cluster time. Also, can you be LESS specific on exactly what are the bugs in my code? 'cause I don't think it's possible.

NPM: can't install a package for shit. tried it waaaay to many times.

Makefiles: Just fuck you.

WSL1: breaks more often than a glass hammer.

Python >= 3.6: FUCK ENCODINGS!!

Jupyter: STOP MESSING UP WHILE SAVING!

Living is to collet bugs, it seems.

Are there more people here who use Makefiles as a façade for complicated commands? For example, 'make dev.up' executes a long docker-compose command and 'make dev.expose.secrets' activates ansible-vault with some variables. It makes doing stuff easier and makes it so that developers with less shell experience can quickly get going instead of having to use long boring commands.

Each time I try to look up what the actual purpose of a makefile is I get a long list of explanatioms talking about building C programs etc. But it never talks about using it to just put shell commands in one big file with subtargets 🤔

So, my question, any of you guys use a makefile to facilitate a facade too?

Makefiles are weird af dude.

Fuck this, gonna make a bash script.:p

when you start really learning C, not "hello world" C but Makefiles and autotools and libraries... is it me or is almost everything a C library and the rest of the languages are just wrappers for C libraries?

Shell/bash for pipelines

The entire syntax seems so hard to read and to write

Makefiles are great but programming in them is shit

Trying (for fun) to run a GNUStep Obj C program that calls c headers has proven something to me:
I really do not know what I am doing with makefiles and should probably slowly and respectfully walk away to continue doing what i was doing in c++

Kids, documentation reading is important.

I also do happen to really like objc

No ranting here but

Started doing web with POCO in C++. Could not be as pleased as now. Syntax is cool, framework is cool, GNU Makefiles are cool, aclocal isn't, but... Go to hell automake. I am happy, helping a friend and enjoying what I feel as the chilliest programming language is becoming the way I do web.

How do you do bootstrapping of blanko machines?
Imagine you get a linux/BSD/osx machine and you want it set it up to a defined state to be prepared for further setup.
Like users
ssh config
Sudoers file
Config management client or credentials
Software like vim, htop and tmux

A simple shell script sounds a bit archaic to me and i was wondering, if there is a better way...

Makefiles also came to my mind but still... Unsatisfactual

Why CMake is a steaming pile of dogshit

- Doesn't echo the command lines it is running making it hard to figure out what it is doing

- Dumps a bunch of crap all ovey my directory structure. And I thought NPM was bad

- Generates 'Makefiles' but only kinda uses Make? (I think, its confusing) WTF

At this rate I wish I could use just bash scripts. At least I could figure out why a simple thing like why my compilation fails to locate an include file even though Is is clearly specified in include_dirs() directive.

Get phucked, Cmake

What's the most sensible way to build and use 32/64-bit libraries with MSYS on Windows? Specifically, I am wondering about zlib and libpng along with SDL2.

I know there are pre-built versions available, but I am inevitably going to need to build other libraries in future.

I'm expecting things to go into /usr/local (which they do), but I'd like to have separate builds for 32-bit and 64-bit. I know I can put things into "lib32" or "lib64" using ./configure options pretty easily, but DLLs (e.g. SDL) seem to end up in "bin" so I assume I should create a "bin32" and "bin64" for those?

Then there's the issue of e.g. libpng not being able to find zlib's headers when using its MSYS makefile... Should I be editing these makefiles? It looks as though I should (things are commented-out etc.) but when I want to update to a newer version, I'll need to modify the makefile again.

It probably sounds like a really silly set of questions but I've always found that building and installing libraries on Windows feels really clumsy and I just want to make sure I'm not making a really messy dev environment.