dveeden2

This didn't mention display postscript, which was used on the NeXT systems (and later on MacOS?)

https://en.wikipedia.org/wiki/Display_PostScript

This talks about a presentation that was given where the details of font hinting were disclosed. Does anyone know if there is a video available of that?

Doesn't SCTP serve the same purpose? Any reason why that never became mainstream for SSH etc?

At PingCAP we make a scalable, opensource, distributed and MySQL compatible database system. We are hiring for many kinds of roles.

https://en.pingcap.com/careers/

Looks like the French flag has missed an update: https://www.euronews.com/2021/11/15/macron-reverts-french-fl...

Seems like this is suffering from issues around the flag of Afghanistan as well: https://blog.emojipedia.org/what-about-the-afghanistan-flag-...

I think the best way of doing this is a 4 step approach:

1. Old situation, time_t is 32-bit

2. Migration starts, time_t is 32-bit by default, -D_TIME_BITS=64 to get 64-bits

3. Migration continues, time_t is 64-bit by default, -D_TIME_BITS=32 to get 32-bits

4. New situation, time_t is 64-bit

And with a long time between these steps. So glibc is at step 2 while musl skipped step 2 and is at step 3. There should be plenty of time between steps. It might make sense to keep it at step 3 until 2037 or so for very restrictive embedded plaforms etc.

NPR did a podcast where they setup a shell company and where they look into the top countries for this.

https://www.npr.org/2021/10/06/1043746410/we-set-up-an-offsh...

It was called OpenTLS in the past. https://www.openssl.org/blog/blog/2018/12/20/20years/

Would still be good to rename, but now there are other projects that use that name. Then some way to resolve the name collision is needed.

https://status.inreach.garmin.com/ has some status updates and says that SOS communication isn't affected.

This doesn't seem to work correctly for say London and Theran as the difference is not a round number of hours.

Otherwise looks useful.

Support for comparing with more than two parties would be nice

Reminds me of the differences between `cp` and `install` for putting .so files in place.

`install` basically results in a new inode allowing for processes to keep a handle on the old version of the .so

`cp` copies the content over the old content, keeping the same inode. Now applications that had that .so open won't be happy.

Note that you can query the annotations during runtime:

In [1]: a: int

In [2]: b = 5

In [3]: c: int = 8

In [4]: __annotations__

Out[4]: {'a': int, 'c': int}

In [5]: c = 'foo'

In [6]: __annotations__

Out[6]: {'a': int, 'c': int}

Tinkering with __annotations__ is also needed for hy (python lisp(-like?) language, http://hylang.org/)

Did anyone try this with things that interface with Fortran or C?

The type hints work with older Python 3 versions. They just get ignored and mypy can use them. However the type hinting syntax for Python 2 isn't the same. For Python 2 you have to use comments. I don't think there is a way to convert between Python 2 and Python 3. Maybe a good reason to say goodbye to Python 2.

But emoji is not handled correctly, the cleartext and ciphertext are identical

On UNIX there are two copy commands: cp and install. cp copies over the destination inode. install creates a new inode. This is important when copying new .so files while an application is using the old one.

With O_DIRECT you won't hit that bug. MySQL/InnoDB allows you to do that (not the default). However I think you're not very likely to hit this bug. This is why you have backups and replication.

I once wrote something similar to figure out what happened based on corrupted and non-corrupted input.

http://unicode-doctor.myname.nl/

URL for mobile: https://nbviewer.jupyter.org/github/hchasestevens/hchasestev...

Reminds me of using wanboot with Solaris (boot over HTTP) http://www.bolthole.com/solaris/wanboot_tech.html

Directly serving /dev/zero or /dev/urandom also gives interesting results. (Be aware of bandwidth costs)

Not limited to http.

http://databaseblog.myname.nl/2014/07/decoding-encrypted-mys...

For more details: https://github.com/dveeden/mysql-history-graph/blob/master/m...

The basis for that is in 8.0, the InnoDB data dictionary.

Awesome. but would have liked to see some old Linux, SunOS, IRIX, etc. reboot screens.

And next is PL/Emojicode for PostgreSQL...

MySQL Workbench recently also got a visual explain option. This is very useful, don't know why everyone keeps struggling with a text format (especially for large explain plans).

https://www.mysql.com/common/images/products/mysql_wb_visual...

Looks rather old to me