I had to uninstall unifont to get nice looking CJK fonts in Firefox; somehow the font-fallback for my font was picking unifont over all of the other fonts installed...
The right way to solve your problem is to go to Firefox Settings/Language and Apperance/Fonts, then click on "Advanced".
There you can set what fonts should be used by Firefox to display each script/language, including Chinese, Japanese and other CJK variants.
If you do not configure this, then it is indeed unpredictable which fonts will be used by Firefox to render the Web pages, unless it can match exactly a font requested by the page.
I've reproduced issues with Unifont's glyphs being invisible in firefox and chrome (at different times, on what seems like certain versions), with much confusion. There are a few issues on the nixpkgs issue tracker about this, including one about Noto Color Emoji doing the same thing.
You wrote up "of course I refigured it" as if refiguring mirrors is something any reader would know how to do. I (and I suspect most of HN) does not; have you (or others) written on this topic?
Here is a talk (in french, but maybe the auto-subtitling would work?) I recorded that overviews the whole process (2h30 though, and lacks info on the Bath) : https://www.youtube.com/watch?v=Wt7lBLS0ueg
Wow, thanks for the link to Texerau. I had no idea a pdf was floating around and have wanted this book for some time. You video looks interesting, especially the part around Ronchi and Focault testing. I have 'Understanding Focault' but have to admit that reading it doesn't give me confidence.
One question I always think about is how much time and effort a "one-time" mirror maker should plan on making to exceed the quality of a generic 8" or 10" F/5-F/7 available from the Chinese mirror makers.
Zambuto seems to imply that whatever magic happens for his mirrors might be in very long, machine driven polishing to smooth out the final surface imperfections that cause scatter. With his retirement and with few mirror makers in the US, it seems like options for buying "high end" mirrors in the 6"- 10" size are very limited. I have been debating an 8" F/7 and would love to just purchase a relatively high quality mirror, but most of the mirror makers seem more taken with significantly larger mirrors.
But it's been illegal to peddle porn to minors for much longer than it's been illegal to peddle social media, so it's a good proxy for how effective our current efforts are.
The approximate substitute-good for porn is actual sex, which parents generally stop teens from doing. The substitute-good for social media is talking to people in person, which parents are generally happy with.
TL;DR: If I find a library I'm using would need dependency versioning, I consider that library broken and find (or write) an alternative.
You can always just add a version check and error out if it's too outdated. The thing there isn't an easy way to do is say "this needs a version of that system lower than X" but it would be unusual for a system to intentionally break backwards compatibility (or for an unintentional break to not be fixed relatively quickly after being discovered); usually if there is the semver equivalent of a "major version" change in lisp, the system-name itself gets changed.
Yeah, the liberating thing for me in CL is that things just don’t break as much as they do in other ecosystems. So, when I get breaking changes I look for an alternative that doesn’t break.
One idea: Buy one of these (https://www.harborfreight.com/150-lb-capacity-foldable-hand-...) and turn it into this (https://images.turnto.com/media/t7kuhATX6jW2ChSsite/5A481415...). If you want to keep it foldable, instead of an axle going all the way through, use either a long bolt or threaded rod, with nuts and lock washers, to attach a smaller pneumatic wheel to each side (threaded rod goes through plastic enclosure, nuts/lock washers keep it locked on either side of plastic housing, wheel fixed on outside with bushings or cotter pin)
The most interesting thing about this article was the Bow Wow Wow song linked. It's a song about music piracy (including a usage of the word "pirate") from 1980, including this stanza:
It used to break my heart when I went in your shop
The power of macros is somewhat overblown and not at all hard to explain.
Consider e.g. the "with" statement in Python[1]. Someone came up with the idea, found a way to integrate it into python and a year later, people could use it. In Lisp, you write a macro.
Now Python is a rather agile language as these things go. In other languages it would be a lot more than a year. When I was in college, my professor wanted us to use generics, but the school mandated language, Java, lacked generics at the time. So we were told to use a fork of javac that had generics added. Pretty much none of the development tools would play nicely with this, and javac was at least two orders of magnitude slower at compiling than my preferred java compiler at the time (jikes).
None of this is world-ending, but it really is annoying. The argument for macros is just "what is the next generics/with/whatever feature that your language is missing." Most of the features that lisp programmers use macros for have made it into modern languages that continue to evolve, so the leverage narrows. In the late '90s it was probably a much bigger multiplier than today.
Ah cheers thanks, my stupid! (And what's worse - wasted some others attention and even thought what someone took time to create was at fault!) However thankful for kind directness there.
reply