4 ms·
I applaud the effort. Nothing much has changed beyond C and the FTP-zip-tar-configure-make landscape since, what, 1980? The distro package systems have improv
by imglorp 11y ago
I applaud the effort.
Nothing much has changed beyond C and the FTP-zip-tar-configure-make landscape since, what, 1980? The distro package systems have improved things a little.
This will have a bigger impact on the language than a lot of the individual library incorporation that's been going on.
- acveilleux 11y agoconfigure scripts became ubiquitous in the mid nineties about the same time as Linux. Prior to that, it was FTP-uncompress-untar-edit config.h-make. You'd be expected to spend 10-30 minutes scanning a long config.h file or similar and adjusting as per your local unix variant. Often a BSD or SVR4 like system (rarely both) would work mostly out of the box. AIX, Ultrix, or HP-UX were more troublesome from what I can remember, SunOS or Solaris (never both ;-)) would mostly work out of the box as that was commonly the dev platform.
- ataylor284_ 11y agoAh, yes. There was also the imake/IMakefile variant too, mostly for X11 related stuff.
- easytiger 11y agoIf people used it properly, it wouldn't really be an issue.
- imglorp 11y agoIt's not an issue, it's a ginormous convenience. Wouldn't you rather have one # decl that does all the legwork of installing a dependency for you, plus all the things it depends on? All these cool kids' languages have that stuff builtin now. Or at least builtin one level away, ie gem, "go get", gradle, etc and ilk. It's so convenient. I dread that part of c*.
- easytiger 11y agoGo live behind a firewall. See how that pans out for you. It will encourage some horrendous levels of indirection in dependencies that cpp currently doesn't suffer from. I've been doing this for 7/8 yers and I don't feel inconvenienced. Indeed I think it represents a decent quality control step
- imglorp 11y agoTrue, there's tradeoffs there.