Most of musl's performance issues come from their allocator. Using it with a third party high performance allocator allows you to benefit from static linking with very little performance loss.
> Most of musl's performance issues come from their allocator. Using it with a third party high performance allocator allows you to benefit from static linking with very little performance loss.
This is addressed and disputed very early in the article. The very first benchmark presented shows a 26% regression using musl + mimalloc, a high-performance 3rd party allocator.
It's not really disputed since musl without mimalloc has a 144% overhead, so most of the performance issues do indeed come from the allocator, by a pretty large margin (~85% of it). Not only that, but some of the "other code" performance hit might still come from the allocator: when you set a global allocator on the Rust side, musl still uses its own allocator internally (as demonstrated by https://github.com/BurntSushi/ripgrep/issues/3494).
And the compounding issue is that the allocator issues get significantly worse as parallelism increases, as the allocator is serial, so as concurrency increases so does the impact of the allocator, which is not the case for most of the "regular slow" code (of musl), those have a relatively constant overhead per thread.
"Using it with a third party high performance allocator allows you to benefit from static linking with very little performance loss" is disputed; 26% is not "very little," even if 144% is worse.
You could've changed the setting that puts the button back on the lower left corner and saved your relative the trouble.
The new default is truly terrible, though, and this was the first setting I had to change when I was forced to use a windows laptop by the company I work in.
> You could've changed the setting that puts the button back on the lower left corner and saved your relative the trouble.
Nice, I didn't know that was possible; I expected it to be unchangeable, since I heard that the whole taskbar is no longer customizable in newer Windows releases.
Last time I used Windows 11, maybe late last year, there was no way of doing that… though they had finally allowed you to turn off the source of ads (“widgets”) which they put in the corner instead.
I find accidental flags rarer due to the layout versus things I'm trying to tap, however the few times it's happened I only discovered it days or months later when visiting the "flagged" page [0].
Still, there's a kind of guilt, like realizing you unknowingly kicked a puppy who isn't there anymore.
I do find it quite ironical that the thread is about the fact that Mitchell states that there are entire companies right now under AI psychosis and then we see solenoid's comments and they do seem to prove a few part of it.
Looking at the code (https://github.com/davmlaw/uBlock/commit/fa2de61ae69927591db...), there's not much I would do differently writing by hand. It breaks some formatting/style conventions from the rest of the file, which I would probably flag in an organizational code review... but otherwise the logic is solid.
So is this "slop" simply because it's written by an LLM, even if the output is solid? Would it NOT be slop if it was worse code, but written fully manually? Honestly, I'm not sure I know the answer.
reply