You can finetune an LLM to a new tokenizer by nudging just a few layers (even wildly different kinds of tokens), and there's nothing stopping a lab from using someone else's tokenizer.

    GET https://rorz.io/_next/static/chunks/link-CKkD60iF.js 404
    Loading module from “https://rorz.io/_next/static/chunks/link-CKkD60iF.js” was blocked because of a disallowed MIME type (“text/html”).
    TypeError: error loading dynamically imported module: https://rorz.io/_next/static/chunks/link-CKkD60iF.js index-ConxhaY_.js:2:49967
    The above error occurred in a React component:
    Lazy@unknown:0:0
    div@unknown:0:0
    div@unknown:0:0
    div@unknown:0:0
    body@unknown:0:0
    html@unknown:0:0
    Eo@https://rorz.io/_next/static/chunks/vinext-B9_QPQZC.js:32:16818
    [...]

There's a lot of annoying issues with Python, but compared to the billions of dollars and thousands of man hours that has been spent trying to fix Javascript and how horrible it still is, it's a perfectly cromulent language.

All models do it now.

KDE actually solved that long time ago with kdeinit (https://web.archive.org/web/20010517071320/www.suse.de/~bast... and follow-up work by Lubos, see e. g. https://conference2005.kde.org/slides/kde-performance/index....), but the new crop of developers didn't notice much difference on their high-end systems with SSDs, so they ripped it out.

When you decide to suddenly stuff some of the most complex pieces of software together (the X server and the compositor which sometimes also double as a desktop shell) into giant codebase/process with seemingly no proper plan or roadmap and make up the specification along the way (or just don't, wayland still has no proper XACE replacement, so kiosk tooling etc. is ad-hoc), you get Wayland in its current form.

Rant over; if you want to actually find out what is making stuff stall, maybe try bpftrace, DTrace or SystemTap (depending on what your distro ships and what tooling is more familiar/suited to you)? Or just run `perf top` and see if anything stands out.

For the boot run `sudo systemd-analyze critical-chain` and see what it is waiting on. And be ready for the nightmare that is the systemd "design": https://blog.darknedgy.net/technology/2020/05/02/0/

People seem to believe arch is much more yolo than it actually is (though forks of arch have tended to be pretty yolo, and I assume cachyos is a bit yolo as well based on the issues people have).

In their defense the people working on glibc and gcc are pretty intelligent and spend a lot of time thinking about how everything they do affects their users, though they make mistakes like all humans (and LLMs I should say by now).

Maybe I'm just old and grumpy, but we spent decades hammering out all the incorrect (for pulseaudio) assumptions in every layer of the stack and papered over impedance mismatches, and then people decide to rewrite from scratch again (though I'll admit I was a vocal pro-dmix anti-pulseaudio hater for a long time).

It has also been protecting politics from capital in various ways; public funding of political parties, strict bans on various forms of political adverts, forced disclosure laws, essentially forcing capital into a single visible chair (NHO), etc.

How did you verify this? The results seem to indicate otherwise.

It was a neat place to host/download some big datasets before huggingface.

So updating cfront for modern C++.