TazeTSchnitzel

GP surgeries in the UK are privately owned, their relationship with the NHS is contractual. It would not be surprising if they can buy whatever B2B SaaS they feel like.

Twitter is a shadow of what it once was. The design of the site has shifted very very hard in favour of being an algorithmic content soup rather than a social network in the traditional sense. This has juiced the engagement numbers but there's a lot less meaning to them now. (I can say all this because I am a bitter holdout who still tries to use the site to have conversations with people and form personal connections. Tragically it still offers something that Bluesky and the Fediverse do not, even if that thing is slowly but surely being smothered out.)

So have many other people. What makes yours special? The vibecoding? The sloppy marketing site is really off-putting.

I'd honestly be curious what those “83+ vintage & modern synths” are but you don't even provide a list…

Also, what the hell is a “Hex-to-ASCII Parser”…

They can try to bring back something resembling the MySpace experience, but they can't bring back the millions of songs they deleted in 2018 with no backup. That was a great crime against modern music history.

NO$GBA is written in assembly language?! I can't believe it.

…only if you actually force the LLM not to use `unsafe` somehow! And one must remember that `unsafe` can have all sorts of non-local effects. One way to be maliciously compliant (or in the LLM's case, I guess it's more incompetence than malice) is to make a “safe” function that does an `unsafe` operation for you, and then replace every usage of that unsafe operation with your “safe” function. You can remove hundreds of unsafe blocks that way without any improvement in safety.

An LLM definitely can do that work, but LLMs have a tendency to follow the path of least resistance unless you force them to do things properly and carefully supervise them.

Rust contains the ability to do everything that C can, if you use `unsafe`. And a file-by-file rewrite in Rust from another language usually involves keeping the ABI and API between files very C-like (and unsafe). In practice this means that the result of a first pass this way has all the memory safety of C code, but with worse readability because Rust makes unsafe things less ergonomic.

To actually get the safety benefits of Rust in a real way you have to rework those files to not treat eachother as C code. This is the interesting and the difficult part of a rewrite in Rust, and one that an unsupervised LLM rewrite is probably not even going to attempt.

I don't think this latter stage has actually happened with Bun's codebase. The result of the Rust rewrite in Bun's case is actually less safe than the Zig it is replacing, especially because (I am told) a lot of the new Rust code is unsound (introducing UB).

I wish there were a shorthand for

  x git commit --amend --reset-author --no-edit

I use that one very frequently (after a fixup, of course) because I want the author date on amended commits to reflect the last time I edited them, not the first time I committed them.

Techrights are hard to take seriously, the site's author has such a bad case of that polemic tendency that he lost a libel case because he wouldn't stop harassing someone (https://caselaw.nationalarchives.gov.uk/ewhc/kb/2025/3063).

If my eyes don't deceive me, the upscaling is happening post-dithering, which I think is a shame.

https://github.com/ValveSoftware/halflife on the other hand is the full Half-Life (GoldSrc) engine, but it's not quite an open license.

OpenAI would probably still have some kind of claim against a company that did that.

> I spent the last two weeks glued to the screen most of the time, to a degree I have never experienced before,

With respect, a single period of manic hyperfocus is not what makes a project, it is being in it for the long-haul and putting in the hours here and there even when it isn't fun any more and you have many other things you might rather be doing.

I will admit that I don't like vibecoded things, but perhaps I must stomach that AI will be writing a lot in this brave new era.

However, when the commit history has stuff like

  v0.5.0: native backends, software renderer, text input, IME
  Co-authored-by: Claude <noreply@anthropic.com>
  Co-authored-by: Codex <codex@openai.com>
  Co-authored-by: Composer <composer@cursor.com>
  Co-authored-by: Cursor Grok 4.5 <noreply@cursor.com>
  
  377 files changed
  Lines changed: 62423 additions & 2871 deletions

it's very hard. These “change the entire world” commits make for a history that is impractical to follow for a human, and therefore of little interest to me.

And Meta have made their social media platforms anti-social. Once upon a time, Facebook was primarily a place to keep up with your friends. But now it's trying to divert you away from people you actually know and instead try to make you consume an endless feed of slop.

(A similar thing has happened to X-formerly-Twitter, tragically. Musk and Bier are systematically destroying the usefulness of the site as a social platform.)

Forcing social media apps to have a less addictive design is a much better way to protect young people's brains than a social media age limit is (and frankly adults need help here too).

Isn't 誘惑 more like “allure, temptation, seduction”?

A few years ago, I signed up for an Apple Watch eSIM plan (which is a special type of eSIM plan that Apple make cell carriers agree to offer as an add-on to a normal cell subscription for your iPhone, and there is no other way go get an eSIM for it).

I then started regularly receiving phone calls (to my iPhone) intended for someone else. At first I thought it was a wrong number or an old number and kept telling them to remove this number. Buy the calls kept coming and I eventually I dared to ask what number they had dialed. And it wasn't a cell number I recognised.

After contacting support for my carrier, what I figured out was that the Apple Watch eSIM has its own phone number, for some reason, but it's not one you're supposed to know about; as an extension of your phone's subscription, the Apple Watch eSIM notionally has the same number as it. But they were calling the secret number associated with the eSIM, somehow. And I think there was a problem in the number routing table somewhere, because I think this number may have been in use with another cell carrier, and the calls only went to me when calling from my network?

Absurd nightmare situation.

If you're going to throw AI at the problem, couldn't you get it to port the real Windows CE shell ?

If I have to look at yet another website with this same fucking AI-generated theme I'm gonna have to kill somebody.

I²S is a remarkably simple design. There's no protocol handshakes, it's just raw PCM. I like how it's designed so sender and receiver can use totally different sample bit-depths (in either direction) without any incompatibility.

https://web.archive.org/web/20070102004400/http://www.nxp.co...

The “Table of Contents” in the article (https://mainmatter.com/c-to-rust-migration-book/) looks like the very basic stuff and not especially interesting, but then the headings in the book itself (https://mainmatter.com/c-to-rust-migration-book/course/) look much more in-depth and don't seem to map onto the supposed ToC. I think they're misusing that term? I guess it's aspirational too as the book isn't finished yet.

In my experience the amount of buffering you get for USB MIDI seems to be highly variable. I've had incredibly frustrating problems with mysteriously vanishing commands with two different USB-MIDI adapters on macOS (to the point I would consider macOS unusable for MIDI, but since nobody else has ever complained about this it must be a quirk of the 2017 MacBook); on Windows, everything is always buffered properly; and then on Linux, it usually works, but then will randomly blow up.

Anyway, the æsthetic of this website trips my vibe-coding sense, though I might be oversensitised. I find that pretty depressing, because MIDI is a field of carefully designed resource-constrained systems, everything has been meticulously hand-crafted by generations of engineers and there is nothing so complex it would make sense to resort to AI. (Here's my own MIDI SysEx project that's all hand-written, by the way: https://hikari.noyu.me/etc/SoundPalette. Not trying to self-promote, I just wonder if it might be interesting.)

The OP's article and replies in the comments here seem like someone who's comparing an idealised view of what Bluesky could be versus a cynical view of what Mastodon currently is. This troubles me because it overlooks the massive problems with Bluesky as it currently exists. It is hyper-centralised, much more so than Mastodon ever was. Virtually all users have their data stored by Bluesky PBC, aggregated by Bluesky PBC, access it through a website and app made by Bluesky PBC, and most crucially, are subject to the moderation decisions of Bluesky PBC at every turn. And I don't think it's a stretch to call Bluesky an “instance” here.

Now, sure, you can use a different instance for most of these services. And that instance can interoperate with Bluesky. But that's the case for Mastodon as well, and the real difference is the Fediverse has had to live with the painful compromises that come with the anarchy of the real world. I think Bluesky will discover its own version of defederation soon enough. I don't think “ah, but you technically theoretically can still interact with people even if you can't see them on your instance” is worth all that much.

I've always thought the JR logo looked like 駅, the kanji for “train station”, and assumed it was deliberate. Perhaps that was a factor in them settling on the JR name?

Anubis doesn't rely on spying on the user.

Aktiebolag is the overwhelmingly most common company form in Sweden and similar to common corporation forms in many other countries. It's not the same thing as a US LLC, which is a strange entity that has pass-through taxation.

Which is to say, there's nothing particularly remarkable about it being an Aktiebolag. It would be more remarkable if it wasn't.

These are very nostalgic. The way Apple's emoji look has subtly changed since then.

You can watch the TV programme here: https://www.youtube.com/watch?v=PNR0Q97TtRU