amarshall

Certainly I would not say “don’t ever quote strings in Bash”, that’s plainly wrong. Actual advice I would give is to use Shellcheck for all shell scripting as it will generally correctly warn about missing quoting (e.g. of shell vars) and does warn about tilde not being expanded in quotes.

It does not warn about `echo "$PATH":~`, though, but that is perhaps an uncommon “error” that is more about your contrived test case (not that Calvinball is good, ofc).

Or you can just…not quote the tilde. Folks always seem to reflexively quote “strings” in Bash while not realizing that (almost) everything is a string and most strings are not quoted and it would be odd to do it (e.g. no one is doing `"ls" "-a" "foo"`).

Use nixos-unstable-small branch or backport the change and build yourself.

H.264 is supported on Linux in DR Studio, it’s just not in the free version.

I rarely care about the date of the commit on the branch to determine recency, I care about when I last switched to the branch.

This comment gets it correct https://news.ycombinator.com/item?id=49504860

I wrote my own version to do this nearly 10 years ago: https://github.com/amarshall/git-recent-branches

Qubes uses VMs, Jails use a shared kernel. So I wouldn’t say Jails are safer nor that they have a smaller exposed area with regard to host isolation than VMs.

Bigger issue was that native encryption doesn’t (didn’t?) have a maintainer, so even though most bugs got fixed, it’s not a great thing to build on. Some of the key storage is also a bit outdated.

IMO use LUKS unless you really need the features of ZFS native enc.

Has it? Most of the LLM-generated commit messages and PR descriptions I read are needlessly verbose and miss the point: elucidating the why of a change rather than the what. If I actually pose a question based on them the author often tells me “yea that was some AI generated nonsense, I rewrote it now”.

Use uBlock Origin and add custom filters to block scripts on http:// ; e.g.

    http://$inline-script,domain=~localhost
    http://$script,domain=~localhost

It’s possible to make a fake display to avoid that; both Linux and Windows have this ability. No dummy plug is required (though it is simpler than software solutions).

Pretty light on details, heavy on fluff. 9.8s to 3.1s was userfaultd + hugepages, 500ms was PS/2 mouse and… where is the rest of the time to get to 400ms?

No, and having that is not required to know output speed nor the effect of thinking, so I don’t see the point in such a superfluous, indirect question.

As for the question you’re likely asking: benchmarks that include speed across many models and providers available at various places e.g. https://artificialanalysis.ai/leaderboards/models

Thinking doesn’t change output speed. Anthropic’s models are ~ 40–60 t/s median output speed.

Can take the geometric mean of total and active parameters of MoE to get approximate equivalent quality to dense model params. So sqrt(35*10)≈18.7.

The trade-off of MoE is that it is worse but faster for the same total size.

What context length and kv cache quant (if any) are you using? And MTP?

Probably want `kitty --single-instance` to reduce memory usage when opening multiple.

https://sw.kovidgoyal.net/kitty/invocation/#cmdoption-kitty-...

The actual paper (linked in another comment here) is literally titled “Nonergodicity and Simpson’s paradox in neurocognitive dynamics of cognitive control”. Why they omit it from the blog post version, I’ve no idea.

Seems like a case of Simpson’s Paradox https://en.wikipedia.org/wiki/Simpson%27s_paradox

If you are running on 4090 and get 5 t/s, then you exceeded your VRAM and are offloading to the CPU (or there is some other serious perf. issue)

Oh I missed the "quad" before 3090.

You're almost certainly (definitely, in fact) confusing the 120b and 20b models.

Yes. Even 90 Hz is a noticeable improvement over 60 Hz. I wouldn’t pick it over high-DPI, though.

No, the connector is longer than it is tall.

Maybe, but Apple doesn’t make them thinner anyway so the argument is invalid. iPhone 6S with headphone jack: 7.1mm thick. iPhone 17 is 7.95mm thick.

It’s easier than that. Replace shorts with watch in the URL.

Non-Shorts can be vertical as well. It works fine, and without the swipe-encouraging UX. If they were “just making long/medium-form videos in portrait now” they don’t need YT Shorts to do that.

DisplayPort 2.1 (which the monitor supports) provides sufficient bandwidth for 7680x4320@60 Hz 10-bit without DSC when using UHBR20. The press release unfortunately doesn’t clarify whether the monitor supports UHBR20 or only the lower UHBR10 or UHBR13.5 speeds. Of course, the GPU must also support that (Nvidia RTX 5000 only at the moment, as I believe AMD RX 9000 is only UHBR13.5).

Redownloading everything isn’t a risk when the lock file contains a hash of the download on first update.

Enabling Reduce Transparency is a sure-fire way to find a dozen bugs within a few hours. It is always quite apparent no one who is empowered tests it at Apple. At least the padding issue is the one Feedback report I sent that got the “more than 10 similar issues” label so it may actual get fixed.

> SO much padding

No idea on macOS, but turn on Reduce Transparency on iOS and there’s tons of padding most of the time, but then sometimes zero padding. And I mean zero. The edges of buttons and text are at the edge of the underlying background. It’s…embarrassing.