Email or username:

Password:

Forgot your password?
Top-level
ParzivalWolfram

@wyatt8740 @whitequark @jannem @dalias @unnick yeah i've never had a good experience with VS, even VSC, or even VC/VC++ lol, though i also have constant issues with C#/.NET programs and anything adjacent to it but people online tend to tell me it's somehow user error if a .NET program spits out nonsensical, never-before-seen error messages then just die. i only write in python on windows just to avoid all of those headaches.

24 comments
✧✦✶✷Catherine✷✶✦✧

@parzivalwolfram @wyatt8740 @jannem @dalias @unnick I shipped software that built on both MinGW and VS; I don't mind the compilers (either), I mind the garbage around them built by people who think fork() is peak API design

Wyatt (🏳️‍⚧️♀?) replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark @parzivalwolfram @jannem @dalias @unnick fork is quite annoying, i agree
But bash isn't the POSIX C API. You don't have to write fork()'s to use a shell script

✧✦✶✷Catherine✷✶✦✧ replied to Wyatt

@wyatt8740 @parzivalwolfram @jannem @dalias @unnick shell scripts are for automating admin tasks. write your build system in a real language, such as CMakeLists.txt (still more real than bash)

Amber replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark@mastodon.social @wyatt8740@tech.lgbt @parzivalwolfram@infosec.exchange @jannem@fosstodon.org @dalias@hachyderm.io @unnick@wetdry.world real language and seeing CMakeLists.txt threw me for a spin. I fucking hate writing cmake but I hate using anything that's not cmake 😭

ParzivalWolfram replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark @wyatt8740 @jannem @dalias @unnick question: what if csh from 1989 is the only scripting language available to you, and there's no compilers available on a target system except K&R as? i'm working on a project where this is the entire issue, and it's... not fun. this is the precise case where that "consider using bash to build GCC because some cases in other shells make the ./configure script take literal days" warning actually happens lol

Wyatt (🏳️‍⚧️♀?) replied to ParzivalWolfram

@parzivalwolfram @whitequark @jannem @dalias @unnick i was about to mention csh, actually. Lol.

There are so many things worse than a bourne shell
Bourne shell is the only way i can comfortably survive in a windows environment

always tired (moved to chaos) replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark @wyatt8740 @parzivalwolfram @jannem @dalias @unnick I'm in a project using cmake and I don't like it. (I prototyped a replacement of our build stuff in omake in finite time...) But definitely less bad than autohell.

Wyatt (🏳️‍⚧️♀?) replied to always tired (moved to chaos)

@project1enigma @whitequark @parzivalwolfram @jannem @dalias @unnick I'm a fan of writing a makefile and telling people to figure it out.

Sure, it pissed me off when i started, but once I figured out how makefiles work I appreciated them a lot more

always tired (moved to chaos) replied to Wyatt

@wyatt8740 @whitequark @parzivalwolfram @jannem @dalias @unnick make has its limitations especially in really big multi directory source trees like ours. omake is enough make like, but with multi directory stuff just working really correctly. And fast. That's why I used that for my prototype alternative build.

✧✦✶✷Catherine✷✶✦✧ replied to Wyatt

@wyatt8740 @project1enigma @parzivalwolfram @jannem @dalias @unnick I probably write makefiles better than you do and this is exactly why I avoid it inflicting it on others: as a matter of basic compassion

ParzivalWolfram replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark @wyatt8740 @project1enigma @jannem @dalias @unnick i don't mind projects with makefiles that are like 30 lines at most, where it's just a shell script but it's kept around for build systems and such. when it's a 30KB file full of high-level shell wizardry... i just have to hope i don't have to dig through it and that it just works.

Em replied to Wyatt

@wyatt8740@tech.lgbt

Sis
You both implied the same thing and diverged around "but what about other people"

Wyatt (🏳️‍⚧️♀?) replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark @project1enigma @parzivalwolfram @jannem @dalias @unnick The first link is clearly not me saying "i'm a better programmer." I am saying that I appreciate the simplicity of a makefile compared to dealing with cmake

As for the second, i said that because YOU implied I was incompetent for liking bourne shells. Jerk. Blocking now.

ParzivalWolfram replied to ✧✦✶✷Catherine✷✶✦✧

@whitequark @wyatt8740 @project1enigma @jannem @dalias @unnick cmake is still an eighties-quality tool, it can't handle being used in buildroot 90% of the time without manual intervention and the nightlies need cmake to build cmake, so that's gonna be fun to look forward to later considering that got pkg-config (or whatever it was, i forget the name) replaced with a rewritten tool by most distros pretty fast.

Go Up