Show newer
@brainblasted That's likely systemd restarting it after a crash, maybe launch nginx manually?

GNU LibC's "wcsmbs"'s `wctob` function wraps the innards of "gconv" to convert char into a Unicode codepoint, fastpath for ASCII.

`wc[s]width` wraps the configured locale & "wctype" to compute the width of each char in the given widestring, `wcswidth` sums the result.

`wcstok` wraps `wcsspn` then `wcspbrk`, returning early NULL on error.

`wcsspn` iterates over the given widestring & with an innerloop over the acceptables chars to exit as soon as it finds a char in that set.

2/?

Show thread

Has anyone else seen this? This person from 2018 describes an issue that I have with one of my servers, but never got an answer: https://serverfault.com/questions/929326/why-does-nginx-automatically-restart-and-fail-to-do-so

Reading articles like this: thespinoff.co.nz/irl/25-11-202

I have to say: I do believe in end-to-end-encrypted group conversations. I don't believe in providing uncurated channels for promoting arbitrary thoughts, etc.

My thoughts on package managers I shared the other day apply to more than package managers...

GNU LibC's "wcsmbs" sublibrary implements UTF16 processing, which loosely resembles the "string" library with builtin "iconv" integration. Though UNIX programs now typically stick to UTF8 so "wcsmbs" doesn't get as much use or optimization. (Microsoft's kernel however deals in ASCII or UTF16, so things are different there) Typically when any real text processing is desired we pull in the external LibICU library to be properly internationalized!

1/?

My dad is not a "computer person". He is an arts professor in his 60s, and still gets double-click and single-click wrong all the time.

But he is surprisingly good with computers, because his approach to broken things is to poke it a bit, pry it open, try a bunch of things until it is more or less working.

That is a great workflow for working with software, but absolutely terrifying when he does it to the house's wiring.

a computer idea i fell asleep thinking about 

this thought:

if you think open source code has utility for users (which, as someone who uses software, i do), then one of the implied obligations is to think of the code itself as an interface to the software.

reinterpretation of economy of scale 

Economy of scale is usually known as the trick where you make a TON of something in order to make the per-unit cost lower.

But there are other types:

1. Designing an object so that it can be efficiency shared among many people. (scaling on humans instead of units produced)

2. Designing an object so that it is simple enough for others to reproduce in a decentralized fashion /wo highly specialized tools. (also scaling on units produced)

@vincent @vertigo @alcinnz @drwho As for sound and video, I'd love to include an FPGA to emulate a SID, VDC, etc, but I think that would probably add too much complexity and cost. It's probably better to use a fast enough CPU to emulate that stuff in software and run everything under a hard realtime kernel, perhaps as a fixed set of processes: sound, video, GUI, I/O handling, network, and the running application.

@vincent @vertigo @alcinnz Emacs, the Oberon System, RISC OS, ROM BASIC, APL, Smalltalk/Squeak, and Racket/DrRacket are my favorite inspirations so far.

I like that Oberon doesn't compromise its modeless UI just to make it easier for beginners. Instead they include a book. ROM BASIC and a lot of other early systems were similar because they simply didn't have the room. I would make it self-documenting like Squeak and Emacs, though.

Show older
FLOSS.social

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).