Notices by Francesco P Lovergine (gisgeek@floss.social)

@jwildeboer
Totally agree about that, done maybe almost 30 years ago. And nothing is better than reading 'DNS and bind' by O'Reilly to understand how it works.

I just found a pure Python #geotiff implementation; it has been experimental for 3 years. It has a series of contributors, too.
Quite a long time ago, I wrote my own implementation of a TIFF library in C. That was before the well-known SGI libtiff implementation, and I know that writing such a lib from specs is not for the faint of heart: I was perfectly able to write legal TIFF files that caused segfaults for many applications at the time (but for Adobe ones).

https://github.com/KipCrossing/geotiff
1/2

@anna
I would definitively recommend SFSCon in Bozen as an alternative meeting. Nice location and venue.

https://www.sfscon.it/

@civodul
There is a well-known deprecation policy for Python.

https://peps.python.org/pep-0387/

I like the deprecation documentation in Perl, which is very precise. Specifically, some features are introduced as experimental and possibly deprecated if they hurt more than they are perceived as an advantage.

https://perldoc.perl.org/perldeprecation

In the case of very large projects, like a distribution, I don't think a deprecation policy is really practical: there are too many variables due to subprojects....

@hgfernan
Scheme dialects implementations performances are among the most well-hidden secrets of computing. Ok, I'm joking, not so secrets, indeed 😂

This is a post about multiple #programming #languages #performances It's not too serious, but it's interesting enough.

https://lovergine.com/a-silly-benchmarking-of-some-programming-languages.html

@nixCraft Sigh, I even remember when it was 1.0, and compiled COM files only for DOS 2.11. I'm definitively not old, but ancient.