shiomiru (u/shiomiru)

shiomiru commented on Can you slim macOS down? eclecticlight.co/2026/01/... · Posted by u/ingve

greggsy · a month ago

Unlike macOS, your cat does not, and will not, meet the industry-accepted standard that describes unix as we know it today.

https://www.opengroup.org/openbrand/register/xym0.htm

shiomiru · 25 days ago

> as we know it today

An important nuance you seem to be missing is that SUSv3 is equivalent to "IEEE Std 1003.1-2001" (that is, POSIX 2001).

In practice, I've had to work around more POSIX compatibility issues in macOS than in all other actively developed (Free) Unix-likes, combined.

shiomiru commented on Japan to revise romanization rules for first time in 70 years japantimes.co.jp/news/202... · Posted by u/rgovostes

kazinator · 2 months ago

But in the case of ō, you can only use a doubled letter if the underlying word is おお. If it is おう then you don't have a doubled letter you can use; you need "ou" and that's not Hepburn any more. It is "wāpuro rōmaji" (word processor romaji).

shiomiru · 2 months ago

"ou" is fine too, actually. See the proposal p. 14 (=16 in the PDF): https://www.bunka.go.jp/seisaku/bunkashingikai/sokai/pdf/942...

(To differentiate between the case where it's actually two vowels, you have to put an apostrophe inbetween; their example is 小唄 -> ko'uta.)

shiomiru commented on Full Unicode Search at 50× ICU Speed with AVX‑512 ashvardanian.com/posts/se... · Posted by u/ashvardanian

shiomiru · 2 months ago

That "deeper explanation" seems incorrect, considering that the KSC column is empty in the mapping linked above.

shiomiru commented on Full Unicode Search at 50× ICU Speed with AVX‑512 ashvardanian.com/posts/se... · Posted by u/ashvardanian

infogulch · 2 months ago

Unicode wants to be able to preserve round-trip re-encoding from this other standard which has separate letter-K and degree-K characters. Making these small sacrifices for compatibility is how Unicode became the defacto world standard.

shiomiru · 2 months ago

The "other standard" in this case being IBM-944. (At least looking at https://www.unicode.org/versions/Unicode1.0.0/ch06.pdf p. 574 (=110 in the PDF) I only see a mapping from U+212A to that one.)

shiomiru commented on Chafa: Terminal Graphics for the 21st Century hpjansson.org/chafa/... · Posted by u/birdculture

cherrycreek00 · 2 months ago

I've been trying for like three hours to get this to show in-line images with w3m. Anyone got a config with that working?

shiomiru · 2 months ago

w3m doesn't support chafa for inline image display.

(You can set a custom w3mimgdisplay command, but it has to speak the same protocol as w3mimgdisplay. If you're feeling adventurous, you can try modifying https://github.com/uobikiemukot/sdump/tree/master/yaimg-sixe....)

shiomiru commented on GNU Unifont unifoundry.com/unifont/in... · Posted by u/remywang

TheRealPomax · 2 months ago

The problem with Unifont is that is was never designed to actually support real text, it just has glyph support. So if you need "it can do every language I might want, while looking pretty good" you're far better off with the (much newer) family of NoTo fonts, which aren't just free to use, but explicitly use the modern SIL Open Font License.

shiomiru · 2 months ago

> which aren't just free to use, but explicitly use the modern SIL Open Font License.

Unifont is also dual-licensed under GPLv2/SIL OFL.

shiomiru commented on Incomplete list of mistakes in the design of CSS wiki.csswg.org/ideas/mist... · Posted by u/OuterVale

Timwi · 2 months ago

A lot of the behaviors should just have a toggle to turn them off. For example, there are many situations where margin collapsing is in the way and I keep wondering why there isn't simply a `margin-collapse: none`. It would also be nice to have something like `default-styles: none` that will remove all the default styling for h1/h2/etc. and em/strong/cite/etc. so I don't have to deal with browsers having differing defaults.

shiomiru · 2 months ago

> It would also be nice to have something like `default-styles: none` so I don't have to deal with browsers having differing defaults.

This already exists:

    *, ::before, ::after { all: unset }

shiomiru commented on Incomplete list of mistakes in the design of CSS wiki.csswg.org/ideas/mist... · Posted by u/OuterVale

shiomiru · 2 months ago

The greatest mistake IMO is the way float state leaks out of blocks, as this is both extremely unintuitive and undesirable for performance reasons.[1] Floats should've been restricted to inline formatting contexts, with all in-flow blocks behaving as if they had `clear: both' set.

I also don't understand why they never specced the (much simpler) `text-align: -moz-left/-moz-right/-moz-center' which already had precedent in HTML with `<div align=left/right/center>'. It's the saddest part of the "center a div" saga, all the W3C had to do to fix it is to assign a standard keyword to a feature that everybody already implemented, but to this day it still hasn't happened.[2]

[1]: https://pcwalton.github.io/_posts/2014-02-25-revamped-parall...

[2]: After many long decades, they did finally specify block-level `justify-items'. Two problems: a) it's backwards-incompatible with text-align, b) it still doesn't work in Gecko.

shiomiru commented on CSS now has an if() conditional function caniuse.com/?search=if... · Posted by u/aanthonymax

xnx · 2 months ago

If we could do it over, knowing that we'd eventually get to this point, would https://en.wikipedia.org/wiki/JavaScript_Style_Sheets have been the better path?

shiomiru · 2 months ago

I actually wonder if transpiling calc/min/max/etc. expressions to JS is a viable path to implementation, considering that you already need a fast interpreter for these.

Deleted Comment

u/shiomiru

KarmaCake day947September 15, 2021View Original