The links are much more durable and survive a rename or move. Plus you can assign random files to different binders (e.g. photo album), add some additional info in a sidecar and use all the info like a database of files (with my tool grubber).
Not only Lisp, but Javascript and Ruby (AKA dynamic languages) devs also rely heavily in REPLs, for me at least the reason is that you don't know what value a variable holts, so you need to inspect them somehow, with typed languages you have less reasons to reach such tool.
iPython was famous for a while but I think its popularity has waned, but yes as you point out really any dynamic language can do a repl; it's just that it's mostly the lisp/scheme and forth families that have leaned so heavily into the idea.
It's the same reason people like symbolic debuggers: you can run your program as many lines at a time as you want and stop and inspect the state whenever you need to. I haven't really used jupyter but I understand the workflow there is very similar.
This does make sense. I generally only switch between models in pi when creating a new session. And it is apparent from the promt if this just a "how to see open ports on linux" or "make a concrete plan for feature X"
Maintaining and providing a deb is pretty easy too; the real killer for a nix flake I think it's how dirt simple it is to provide infinite testing builds for different branches.
Well, for .deb there is the dependency problem. Even if your deb is just a release of a project, you can only use versions of dependencies that are in debian repository. Or include it all in your .deb, which becomes hard to maintain.
By "infinite branches" you probably mean that a nix derivation / flake is a recipe that can build any version of the project?
Yeah, Nix flakes can be a static URL path, but they inherit your VCS refs directly, so
nix run github:tailscale/tailcat
Gets you the default branch. Tailcat doesn't yet have any tags, but if you want a build of the main tailscale repo at a particular tag, it's just:
nix build github:tailscale/tailscale/v1.102.3
But because this can be any ref, you can specify an arbitrary branch or tag, so like if you're trying to get a colleague to check out your work it's as easy as:
nix run github:tailscale/tailcat/my-fancy-branch
And obviously a flake can reference other flakes with the same flexibility, so your home manager config or your company's private app flakes can transparently pull the not-yet-merged version of a change you're proposing upstream without having to make special internal "patched" releases with tortured 1.2.3~actually.1.4.6 type version numbers like in Debian. And of course that same flake reference policy applies all the way down, so you also don't need to worry about the private apt repo as a big piece of shared state that's going rev forward and break your older code branches or Dockerfiles, since each branch of your app flake has its own flake.nix and accompanying lockfile controlling which deps it is pinned to.
It really is an awfully nice system, and shockingly modern in its sensibilities considering how old the Nix fundamentals are.
I don't have any specifics, but based on experience, it feels like software giants like to patent what a lot of people would consider obvious wins (such as interruptible animations) if no other company happens to be doing it, and it felt like this would be something where that could be the case.
That said, I can't seem to find any evidence of this particular thing being patented to support my case, so it's probable that I'm wrong.
Low DRM? I looked at Huawei devices because I figured they'd have to sell them here super cheap because of this downside most Europeans people will even see as a showstopper ("how will I install my precious WhatsApp??"), but
- they're among the most expensive (I could afford that if needed though)
- they don't allow hardware unlock (ehh.. what's the point, then, if I get a locked-down device with Chinese surprises!)
I'm curious why you think China is actually more open in this regard. The CCP has direct influence over the apps that are allowed to be installed on these phones. There is nothing more free about them.
not like that no, some US carriers don't allow them though like AT&T blocks you to google or apple phones. for them only pixel supports a way out with graphene.
Proper Framing - AGENTS.md is fixed and always contextual irrespective of its relevance; memory is the exact opposite of it. PMB does not dump the store in, rather extracts only a small top-k relevant chunk per task (a few hundred tokens generally), hence, more storage in the form of facts does not necessarily translate to more context. "Useless facts" are precisely what it is grading against, i.e., items which do not serve any purpose will simply be considered dead and decayed.
reply