Very interesting technique to get the widths of the glyphs uniform without them looking ugly in most cases. OK, one can make it look bad if you know the “pain points” of the system, but in normal flowing texts, the fonts do look good.
Very interesting technique to get the widths of the glyphs uniform without them looking ugly in most cases. OK, one can make it look bad if you know the “pain points” of the system, but in normal flowing texts, the fonts do look good.
Well, you can say exactly the same about COBOL…
People are still using those?
Apart from Python, is anyone of the listed contenders actually still breathing?
Well, to be honest C is still C, but it’s children have run mad.
We did Prolog in university - actually it was one of the two languages we had to learn in CS, the other one being Pascal.
I always considered Prolog a pain in the ass and unsuitable for anything bigger than a piece of homework due to the “we don’t do loops, we have tail recursion” making the code unnecessary complex and hard to read. On a list of Write-Only languages I’d rate it a few steps below Perl.
Old enough they still know Prolog.
I’ve read the documentation on that feature, and still don’t get over it. How can anyone with knowledge of computers be so dumb to even consider such an idea, lest implement it?
This feature is just a BIG flag waving “AbUsE mE!”
“all those COBOL developer jobs” nowadays probably fit in one bus. That’s why every company that can afford it moves away from COBOL.
Ahh, the good old RFCs dated April, 1st. This one is number 1149 ( A Standard for the Transmission of IP Datagrams on Avian Carriers), and got later updated in RFC 2549 (IP over Avian Carriers with Quality of Service).