• 1 Post
  • 107 Comments
Joined 2 years ago
cake
Cake day: March 3rd, 2024

help-circle

  • thanks for clarifying. it was hard for me to dignify such a comment with a response.

    you’re also going to run into hardware acceleration issues trying to run Metal acceleration with a Linux kernel. i don’t really see a need to containerize these workloads these days anyway with tools like uv.

    it’s a big pain in my ass at times trying to do web dev work with an aarch64-darwin dev env vs the target x86_64-linux. adding in hardware acceleration issues just sounds painful.

    i also just personally don’t like containers. feels like bludgeon of a solution.






  • so, it’s the same.

    saying “Linux does dynamic linking and Window does static linking” is both false and a mischaracterization. Windows absolutely does dynamic linking with its Dynamically Linked Libraries (.dll). how dependencies are linked is up to the developer and whatever hardware constraints. one reason i like Rust is that it prefers static linking, and a lot of tool chains are moving in that direction. the reason Linux distros push people toward their internal package management tools (eg apt) is to have tighter control over dynamic linking.

    and we’re also glossing over scoop and chocolatey and winget and Docker.

    but that’s where you get to stuff like flatpack and snap and Nix that try to contain the dynamic dependencies.

    i don’t think downloading exes hoping that Windows has stuffed enough DLLs into the OS and just running them is a better solution.




  • honestly it’s hard to beat Macs these days in this space for two reasons:

    • unified memory means that you don’t have to load up on RAM just to load the model and then also shell out for a video card with barely enough VRAM to fit a basic language model
    • their supply chain is solid and has mostly avoided the constraints that other OEMs and parts manufacturers are struggling with

    pricing is tough. sure, crypto is on its way out, but GPUs are still the platform of choice for most neural net workloads (outside of SoCs like Apple M-series). i built a PC in late 2024, and it’s easily worth twice what i paid for it.





  • art isn’t something you can generate as such. having a model that can copy the Mona Lisa pixel perfectly hasn’t stolen the Mona Lisa. it’s the shitty kids’ movies and TV ads and company logos that are at stake.

    art is about effort and ingenuity and is centered around people and places and times and can’t be simply replicated by an industrial process, as much as Disney wants that




  • it’s one of those cases where if you have to ask, you should probably just use systemd. anything else is outdated or a passion project based on some idealism, which i’m all for, but if you’re worried about gaming performance as a primary concern i’d put it out of your mind. for example, i’m an obsessive tinkerer that uses NixOS and Arch before that and i use nushell and Neovim and Hyprland, but i use systemd cuz i don’t see a reason not to. it’s well supported and stable.


  • i’ve been a big fan of Jujutsu (jj) since adopting it a few weeks ago. things i used to avoid with git like proper rebasing and focused commits become so much easier, in addition to the benefits of conflicts being easier to handle. the learning curve i thought was going to be grueling only took a couple days to get used to, and honestly interop with GitHub and my team’s particular workflow were the hard parts. so not only is it useful, powerful, and becoming more important to my workflow all the time, it’s a joy to use compared to git.

    i guess honorable mention to zoxide, which has basically replaced cd for me since it does everything cd does but also keeps a small db of your most commonly visited directories so you can just do z Downloads or z my_project or whatever from any directory


  • “unhackable” is a bit sensationalized here. the Xbox One is actually a security success story not because it is impossible to hack, but because it’s a rare example of a console that wasn’t hacked in its service lifetime. at the risk of giving praise to Microsoft, the architecture is actually really neat and informed the security features of subsequent Windows releases, ie a hypervisor with sandboxed sub containers (this is why they required TPMs).

    (also i’m not agreeing with requiring a TPM for general purpose machines; they make sense on a bespoke hardware platform like a game console)

    i bet this hack is nuts, but the blue team deserves some level of kudos

    https://youtu.be/U7VwtOrwceo