31–40 of 66 posts
how would one go about running code/operations on ram as opposed to the hd?
On most Linux distros, /tmp is a ramdisk.
RHEL7, and all it's derivatives (CentOS, Oracle Linux etc.) don't use tmpfs for /tmp by default, and they are arguably the most used linux distros in the world.
Earlier quoted context omitted.
Spinning platter. ZFS with compression is probably helping that.
Your OS is probably caching the file at the virtual memory layer, so it doesn't even have to hit the filesystem at all.
Does anyone know the name of the app that's listing/displaying fonts? It looks pretty neat, and I haven't found anything good-looking like that for Linux/*nix.
If you're using ubuntu, there's a package for it
It is both reasonable and unfortunate that TrueType & OpenType fonts can have no more than 65,535 glyphs. That said, probably the logical font made of multiple physical fonts can be probably made to support all available planes.
Yes, that's how you can fit all of Unicode into one "font" -- use a collection of fonts with at most 64K glyphs each:
https://graphicdesign.stackexchange.com/questions/73166/what...
I'll leave it as an "exercise for the reader" to generate such a font.
Don't put your work down like this. You created something useful for yourself, and likely useful for others. I'd be surprised if someone called it stupid.