Closed Buttars closed 2 years ago
So you talk mean, I will be mean too. First of all "every program needs to have 1 purpose" is not suckless philosophy, its Unix philosophy which suckless follows. I dont think you know C or makefiles, because if you just took even a small peek in Makefiles, you can see that dwmblocks and dwm are 2 seperate binary executable programs. Copy dwmblocks.c and dwmblocks.h then write your own makefile.
If you found my comments mean that's on you. After reviewing your socials I see you respond similarly to anyone with similar critiques.
You've made your software much more difficult to extend from it's original form.
If it is two separate builds have them in two repos and have a command pull them separately since they're separate software. This is how every other flavor of dwm+blocks does it.
Even if I were to follow your instructions to copy those files and write a makefile for them, that would result in the inability to pull changes from this branch in the future.
I actually have merged dwmblocks into dwm itself. some reasons
And some thoughts:
|
. Having dwm read a fifo to display the status would be okaish (maybe more unix) but def not suckless.I think this could be like comparing bspwm and dwm. both 'suckless', but muh lines of code!!11 (dwm is overall simpler)
Was there a reason to merge the two? They're two separate pieces of software that do two different things. By merging them you've violated the suckless methodology.
Is there a technical reason to doing this other than "only installing one thing?"
It's a shame because I want to use your flavor of dwmblocks but not dwm and now that is not possible.