Yeah maybe it's less visible nowadays, but in the past the world was not just Linux and FreeBSD. There were many commercial Unixes which differed from each other and from Linux. And to be portable to such systems you needed to check everything. So autoconf was a crucial tool, not just a fancy noop.
I lived in that world, sunos, solaris, unicos, hpux, aix, irix, ultrix. I always found it preferable to have Os and even compiler specific includes for a whatever definitions needs to be different. and I certainly wasn't interested in having a rewrite pass on the makefiles. but it worked well enough when I dug up something on archie.
and then they wrapped it another layer of translation, and then another and I think more. and things started breaking because I needed the right version of autotools, and at some point I started just running "cc *.c -I. -o foo" before even starting to try to use configure, and it usually worked and saved me a lot of screwing around.
its certainly settled down some, but only because everything is really linux. but still we're here more than 30 years later checking for socklen_t.
Why is it important that the build host is portable? Why not choose a single platform for your CI and build for all of your targets on those using a compatibility library to cover up differences.
I once tried to become a Hetzner customer, but they wanted so much data from me, including photos of my ID, so I said no. No other compute provider requested that much, including all 3 big ones and OVH. Either I was lucky before KYC became a thing, and Google, Microsoft and Amazon inferred my identity from my payment cards, or I don't know, Hetzner is just too paranoid. I lean towards the latter. Yes, recently I created a new account in an another European compute provider, and they didn't want my ID.
It's not so true anymore, but when they were cheaper they probably attracted a ton of bad actors (spammers, phishing sites, etc). I assume the KYC requirements were a response to that.
I actually would be interested in doing it, if I'd been following along the 3.15 development cycle. As is, there are too many other things I could be doing.
So on one hand you're lagging 4 years (and 4 versions) behind, but on the other hand it's just 4 years and 4 versions. I like your approach. Without it there'd be no progress. Google has similar policy in many places.
It is the standard policy in the Python ecosystem, keeping in lock-step with the Python support schedule (see e.g. https://endoflife.date/python ). Although many packages chose to maintain support for Python 2.7 well into 2021.
He will try but even the Supreme Court has shown they are willing to place limits on his power, ruling against him in some cases. So I don't think he has a pathway to bypassing the 22nd Amendment.
It's truly bizarre. I think some of his supporters think that they are all in on the joke and that he doesn't mean half of it. But at this point there is zero evidence good faith, zero evidence of strategy. Just one odd PR stunt after another that someone can day trade on if they know about it a few hours in advance.
Unfortunately, we won't know for sure until they're presented with a real case involving the 22nd Amendment.
Given its recent behavior, my prediction is that the Roberts court would drag out hearing any challenge against Trump's 2028 candidacy until such time that they can confidently announce that it's too close to the election to remove him from the ballot, much like they did with his criminal case regarding classified documents leading up to the 2024 election.
Choosing a language that forgives bad memory management practices and promotes sloppy programming practices is your decision. Don't be surprised that it has to do its job. You could have chosen modern C++ or Rust and use RAII and proper automatic deallocation.
It was rather towards one-process-per-client such as PostgreSQL server or Apache HTTPd (long obsolete, fortunately). Hopefully PostgreSQL will switch to worker threads soon, and as for Apache HTTPd, I don't care.
reply