Can’t speak for Lumifer, but I was more annoyed by the fact that (the version I got of) OSX doesn’t ship with a working developer toolchain, and that getting one requires either jumping through Apple’s hoops and signing up for a paid developer account, or doing a lot of sketchy stuff to the guts of the OS. This on a POSIX-compliant system! Cygwin is less of a pain, and it’s purely a bolt-on framework.
(ETA: This is probably an exaggeration or an unusual problem; see below.)
It was particularly frustrating in my case because of versioning issues, but those wouldn’t have applied to most people. Or to me if I’d been prompt, which I hadn’t.
After some Googling, it seems that version problems may have been more central than I’d recalled. Xcode is free and includes command-line tools, but looking at it brings up vague memories of incompatibility with my OS at the time. The Apple developer website allows direct download of those tools but also requires a paid signup. And apparently trying to invoke gcc or the like from the command line should have brought up an update option, but that definitely didn’t happen. Perhaps it wasn’t an option in an OS build as old as mine, although it wouldn’t have been older than 2009 or 2010. (I eventually just threw up my hands and installed an Ubuntu virt through Parallels.)
So, probably less severe than I’d thought, but the basic problem remains: violating Apple’s assumptions is a bit like being a gazelle wending your way back to a familiar watering hole only to get splattered by a Hummer howling down the six-lane highway that’s since been built in front of it.
Can’t speak for Lumifer, but I was more annoyed by the fact that (the version I got of) OSX doesn’t ship with a working developer toolchain, and that getting one requires either jumping through Apple’s hoops and signing up for a paid developer account, or doing a lot of sketchy stuff to the guts of the OS. This on a POSIX-compliant system! Cygwin is less of a pain, and it’s purely a bolt-on framework.
(ETA: This is probably an exaggeration or an unusual problem; see below.)
It was particularly frustrating in my case because of versioning issues, but those wouldn’t have applied to most people. Or to me if I’d been prompt, which I hadn’t.
You do not need to pay to get the developer tools. I have never paid for a compiler*, and I develop frequently.
*(other than LabView, which I didn’t personally pay for but my labs did, and is definitely not part of XCode)
After some Googling, it seems that version problems may have been more central than I’d recalled. Xcode is free and includes command-line tools, but looking at it brings up vague memories of incompatibility with my OS at the time. The Apple developer website allows direct download of those tools but also requires a paid signup. And apparently trying to invoke gcc or the like from the command line should have brought up an update option, but that definitely didn’t happen. Perhaps it wasn’t an option in an OS build as old as mine, although it wouldn’t have been older than 2009 or 2010. (I eventually just threw up my hands and installed an Ubuntu virt through Parallels.)
So, probably less severe than I’d thought, but the basic problem remains: violating Apple’s assumptions is a bit like being a gazelle wending your way back to a familiar watering hole only to get splattered by a Hummer howling down the six-lane highway that’s since been built in front of it.
You can get it through the app store, which means you need an account with Apple, but you do not need to pay to get this account. It really is free.
I would note that violating any operating system’s assumptions makes bad things happen.