This.
Moreover, an exam for a course is, to some extent, an assessment on how the course was delivered. And an interview for a job has a much larger scope.
Oral exams have an entire other bunch of issues.
Just looking at the professor side, beside time, I imagine it would be very difficult for to grade with same meter an arrogant student, a dismissive one, a smelly one, an eloquent one, or even the first and the last one in the same session.
Totally agree.
I might a bit partial to that, because I tend to underperform multiple choice tests for overthinking, but I've really the impression that open ended questions test knoledge much better and make it more difficult to cheat.
Beside that, having almost nothing to do with cheating, another good thing in the French system is the continuous grading: labs were graded, projects were graded, small intermediate tests were graded, so you really do not study for just the exam (actually often you do not study at all for the exam).
(beware: my experience is limited to a single grande école I attended).
Thank you for asking!
Your question is the demonstration that "A Reverse DNS API" is a very subpar tagline.
As you correctly state, for "reverse DNS" usually we mean the PTR, which, not being a requirement for a working internet, is quite neglected. Few are sets, and those in large part are actually just an indication of which ISP or datacenter they belong.
What we try to do with Korbinsky is to provide information about hostnames actually pointing to a given IP address or just hosted there.
Just to give an example:
$ dig +short PTR 159.241.75.51.in-addr.arpa
Building go on the target architecture defaults on a dependency on libpthreads for DNS resolutions.
Passing either CGO_ENABLED=0 or -tags netgo fix this.
It's unclear to me how and when spawning a thread per resolution is preferrable to the netgo behavoir.