dnr

7개월 전discuss

I'm not an expert here but I have to say this feels like a very weak objection.

p points to P1. One thread reads through p. Another thread races with that and mutates p to point to P2. The result is the first thread reads from either P1 or P2 (but no other object).

This seems totally fine and expected to me? If there's a data race on a pointer, you might read one or the other values, but not garbage and not out of bounds. I mean, if it could guarantee a panic that's nice, but that's a bonus, not required for safety.

dnr

8개월 전discuss

The inelegance to me isn't in the definition of the operation, but that it's doing a huge amount of brute-force work to mix every part of the input with every other part, when the answer really only depends on a tiny fraction of the input. If we somehow "just knew" what parts to look at, we could get the answer much more efficiently.

Of course that doesn't really make any sense at the matrix level. And (from what I understand) techniques like MoE move in that direction. So the criticism doesn't really make sense anymore, except in that brains are still much much more efficient than LLMs so we know that we could do better.

dnr

작년discuss

Everything you said "should" is exactly what Nix and NixOS is.

dnr

2년 전discuss

Hey, I sorta did this. Lazy substitution, at least, not lazy build. Plus a bunch of tricks to speed up downloads.

https://github.com/dnr/styx/

Lazy build sounds tricky: you don't know the contents of the package before you build it, so you don't even know what to symlink into /run/current-system/sw. I guess you'd have to have some kind of wrapper. Maybe similar to comma.

I just solved that part by setting up CI for most of my system config (integrated with the above).

dnr

2년 전discuss

You're looking at the docs for "visibility". Visibility is a separate eventually-consistent data store off to the side that's used for certain queries so it can be scaled independently of the main data store, and indexed in fancier ways. The main data store for all the stateful and transactional stuff has always, and probably will always, support Cassandra. For visibility, the recommendation for high scalability is currently Elasticsearch.

Temporal may have properties that make it not a good fit for a particular use case, but scalability is really not one.

dnr

2년 전discuss

Temporal can also run on Cassandra, which scales much larger than Postgres (if you put in enough effort). It can also be replicated across regions for high availability. It's already running some pretty huge use cases.

(I work at Temporal)

dnr

3년 전discuss

I'm also using NixOS and working on Go projects, and had to deal with out-of-date Go releases. Nixpkgs generally does get the latest Go versions pretty quickly, but only in the unstable channels, they're not backported to NixOS releases. You can just grab that one package out of nixpkgs-unstable or nixos-unstable, like:

    (import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/nixpkgs-unstable.tar.gz") {}).go_1_21

where you had `pkgs.go` before (in your shell.nix or wherever).

dnr

3년 전discuss

It wasn't quite immediately, it would take a few hours to detect+revert. And that was only the root fs, there were other places to hide things if you really wanted. But then there were other detection systems too. (Probably fairly different now, I left in '11 too)

dnr

3년 전discuss

The idea that the capabilities of LLMs might not exceed humans by that much isn't that crazy: the ground truth they're trained on is still human-written text. Of course there are techniques to try to go past that but it's not clear how it will work yet.

dnr

4년 전discuss

Oh wow, that just jogged a really old memory. I'm pretty sure I had that one, but can hardly remember anything else. Could it have been Xenocide?

edit: Oh, or maybe Silpheed? This is the closest thing I found with some searching: https://youtu.be/o98xKZk5FOk?t=182

dnr

4년 전discuss

Get a fresh cap! The caps only last about a year of heavy use. You can find replacements on amazon and elsewhere. It doesn't even matter if it's really oem, a fresh third party one will still be much better than a worn oem one.

dnr

4년 전discuss

If "two" is acceptable for "many", look at the ODROID-HC4? I made some home NASs out of them.

dnr

4년 전discuss

Actually a huge number of packages in nixpkgs are bit for bit reproducible: https://r13y.com/

dnr

4년 전discuss

Does anyone write k8s manifests in raw yaml? They're so complicated that they're generated using some templating language (helm or kustomize or whatever is popular these days, I'm a little out of the loop). So you still have something programmatic. Think of Nix as just a better and more principled templating language. (I mean, look at NixOS configs: they're much closer to "plain structured files" than "programs".)

The promise that I see (I haven't seen this fully realized but it should be possible) is that instead of yaml plus some ad-hoc templating language plus dockerfile plus makefile, everything is in a single language top to bottom.

dnr

4년 전discuss

> I just want to list what I want and let the tooling make it happen.

That's just what Nix does?

It's very much more declarative than any system I've seen. Yes, k8s turns your declarative manifest into running processes, but how was the image built? There's a huge gap there: you refer to container images by name, not by a description of the software you want them to contain, and then hope that some other process has built the image correctly. Nix can close that gap and take declarative all the way from the service manifest down to the git commit of the compiler used to build your binary.

dnr

4년 전discuss

The Fastmail UI is indeed snappy, except when it suddenly decides it has to reload the page, which seems to be multiple times a day these days (and always when I need to search for a specific email). Can you make it do what one of my other favorite apps does: when there's a new version available, make a small pop up with a reload button, but don't force a reload (until maybe weeks later)?

dnr

5년 전discuss

Hate to make a boring me-too comment, but I feel the same: I've been using it a bit over a year, and I wish I had started even sooner. Now I've got two laptops and a NUC, plus two odroid-hc4's, all on NixOS. All the system configuration that used to be half-broken ansible and a pile of scripts (plus all the one-off hacks that weren't even captured anywhere) is now nice pure nix configuration. I've nix-ified builds for a bunch of personal projects too.

Yeah, it took a few months to learn, and there are still lots of rough edges, but going back to a non-Nix linux distro would feel like going back to windows. I agree with the sibling comment that it makes me feel happy and giddy, like no other technology I've learned recently.

dnr

5년 전discuss

This is one of those religious arguments where no one will every change their mind, but I feel like a trackpad is the dumbest mouse interface and can't use anything but a trackpoint (or a mouse of course).

Consider dragging and dropping: with a trackpoint you click with your thumb, then use your pointer finger to move the mouse cursor any distance you like, without moving your hand, then release. With a trackpad you press the pad and then move your finger some distance and then... oops, you hit the edge of the pad. Better abort and try again, starting the motion from the opposite pad. Except if I'm on a non-apple trackpad, and I have to click near the top of the pad, it's nearly impossible because the click hinge is near the top. Or maybe I do a finger swap to reset the drag position, and hope that the OS doesn't interpret my moment of two fingers touching as some kind of gesture.

Anyway, it does take some time to get used to, so you won't get it in a few minutes or even a few hours. Try a week. Also make sure you're using a lenovo one (the dell/toshiba ones aren't as good), and very importantly, that you have a fresh cap. Worn out caps make it really frustrating.

dnr

5년 전discuss

Isn't that exactly the point, and why it's so great? It's a single algorithm that's tune-able across that wide range of speed/ratio trade-offs using a single parameter. So you can just use one thing for almost every application instead of picking between three different things.

(Yes, I know that one parameter controls multiple different settings internally, so there are multiple dimensions if you're willing to dig that deep.)

Anyway, my recollection from looking at benchmarks a while ago: zstd used at similar ratios to lzma compresses in similar time but decompresses much faster, and it's also faster than gzip when set to comparable ratios to that. lz4 is still faster than the fastest zstd modes, and lzma at the most extreme settings still gets better ratios that the best zstd can do. But there's a huge wide swath in the middle where zstd beats them all, and that's quite valuable.

dnr

5년 전discuss

No relation to the link, but does anyone else remember these books?

Algebra the Easy Way - https://www.goodreads.com/book/show/6781.Algebra_the_Easy_Wa...

Trigonometry the Easy Way - https://www.goodreads.com/book/show/2077099.Trigonometry_the...

Calculus the Easy Way - https://www.goodreads.com/book/show/3074478-calculus-the-eas...

I read these in 5th grade or so and learned most of middle school and high school math just from those.

They're written as a fantasy novel in which the characters discover the relevant math concepts as part of the story. I know, you're thinking that's a silly gimmick and it can't possibly be any good, but it was actually done quite well. At least until the later parts of Calculus where the situations have to get pretty contrived.

Highly recommended, at least for precocious kids who like math and fantasy novels.

Submissions

Show HN: Real-time collaborative crossword puzzles

Begot: a Go dependency manager and build tool

comments