Preferences

pxc
Joined 5,991 karma

  1. They're in the gradual process of open-sourcing their driver stack by moving the bits they want to keep proprietary into the firmware and hardware, much like AMD did many years ago.

    It takes a long time to become mature, but it's a good strategy. NVIDIA GPUs will probably have pretty usable open-source community drivers in 5 years or so.

  2. When referring to the efforts nation-states, I'd be very interested to hear how often such metaphorical usage is used to describe the work of adversarial vs. friendly countries. I would be shocked if it's as often (in the Anglophone press) used to describe the work of US-aligned countries as it is that of US-adversarial countries.
  3. It seems extremely dishonest to frame the project of improving computer chip manufacturing to the development of weapons of mass destruction— weapons that went on to be used against civilians. Sensationalist and propagandistic framing for what is otherwise an interesting article.
  4. You can hold your hand/phone anywhere, including at the same level as your windshield, so that you can look at it without turning your eyes away from the road. Below the dashboard always puts your whole windshield in your peripheral at best.
  5. How is malicious compliance the fault of someone who asks for disability accomodations?

    It is unfortunate that the ADA is designed so that the only mechanism of enforcement of disability rights is lawsuits. :-\

    Maybe there should be some exceptions around things provided on a "best-effort" basis, if they can be very carefully crafted.

  6. Your username is vaguely familiar. You're a CUE enthusiast, right? I think I've read (and enjoyed and benefited from) some documentation you've written!

    Yeah, I think it makes sense to also let people point to arbitrary OCI registries. I'd bet support for that is coming, especially since the execution environment is Dockerized anyway.

    > Pushing nix as the DX for GHA equivalent

    I think something like Nix actually makes more sense than YAML for this kind of thing. You want a DSL that is purpose-built so that configurations are declarative, simple configurations are simple to write, and configurations are composable. YAML is too much of a straightjacket. Some kind of built-in support for deep merges is a must, imo.

    How powerful/expressive the language should be is debatable, I think. I'm interested in Turing-complete DSLs like Nix and Nickel, but CUE could be a good fit here, too.

    Anyway I'm sure they'll add first-class support for using some OCI artifact to define a CI environment. Looks like their CI implementation only recently entered the first alpha.

  7. Ah right, I've forgotten because I'm using a multi-user strategy and a patched version of the runner at this point anyway. The config directory for each runner is normally based on its install path (insane), something like that?
  8. lmao I just realized on this forum writing this way might sound like I own something. To be clear, I don't own shit. I typically write "my employer", and should have here.
  9. It is containers. It's based on Nixery, which is a virtual Docker registry where it puts together containers for you on the fly containing whatever packages you want from Nixpkgs.
  10. And if you want any concurrency at all, you need 1 runner registration per concurrent job. And each runner needs its own user. And each runner requires a full and separate copy of the runner software, which is large (hundreds of megs) and self-updates.
  11. My company uses GitHub, GitLab, and Jenkins. We'll soon™ be migrating off of GitLab in favor of GitHub because it's a Microsoft shop and we get some kind of discount on GitHub for spending so much other money with Microsoft.

    Scheduling jobs, actually getting them running, is virtually instant with GitLab but it's slow AF for GitHub for no discernable reason.

  12. So can we just go back to using external CI platforms that just interact with GitHub's commit status API or whatever?
  13. It seems that "native vs. emulated" here means "arm64 binaries vs. x86 binaries, both running on Windows". So the comparison that the OP is making wouldn't be possible if Blizzard didn't already support aarch64.
  14. I have a Kobo Elipsa 2E (which I love). I never new about the PineNote! It seems awesome. Maybe I will have to get one.
  15. I use them when they're easy to type. For me, that's on Android, macOS, and anywhere I've configured a compose key.

    Angled quotes I use only on systems on which I've configured a compose key, or Android when I'm typing Chinese.

    I don't like any kind of auto-replacement with physical keyboards, so I turn off "smart quotes" on macOS.

    Anyway I use characters like that all the time, but it's never auto-replace.

  16. They do mean the same thing, but they have different moods. With the em-dashes it's self-interjection that foregrounds the detour, but with parentheses it's, well... parenthetical.

    Aside: it's probably just style (maybe some style guides call for the way you did it), but using em-dashes for this purpose with whitespace on each side of them looks/feels wrong to me. Anyone know if that's regional or something?

  17. I was just joking that I myself may have known an annoying kid or two back when I was in school. ;)
  18. If I had to venture a guess, I'd say compression. Knopper picked up and became maintainer of a kernel module called "cloop" that supports zlib-compressed loopback filesystems.

    If Knoppix had this and Finnix didn't, or if Knopper was able to supply enhancements and bugfixes in order to support Knoppix releases, then he was likely able to fit a much more complete system onto a given CD or DVD.

    But idk what kind of compression early Finnix used, if any. (Nowadays, everything uses SquashFS, right?)

  19. Sometimes lacking context actually makes a thing much more interesting. Reading a blog post from your own circles may be intricate, but it's also mundane. Reading a post from another world is always an act of discovery, somewhere between voyeurism, archaeology, and the joy of getting lost in a new city.
  20. > let code die, especially other people’s delete all code, start from scratch you must delete! kill your code and also other people’s. let go! forget everything! start from scratch

    > delete delete you must delete! set yourself free from attachment and loss you are not dead yet, so be alive and act!

    > we are not here to make code: we are here to make changes

    I want this on a T-shirt.

This user hasn’t submitted anything.