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

help-circle


  • the AI explanation and reasoning is weak. what does “largely disappears” mean without numbers? Cloudflare doesn’t do vibes; give me numbers. in any case “desktop” surely means that the user-agent reflects a desktop browser and not a CLI tool, right? otherwise this number would be closer to 90% than 10%. unless the agents are intentionally spoofing browser user-agents i don’t buy it.

    no mention of Steam’s and Framework’s hardware offering that come with Linux? no mention of the clear mass migrations?

    here’s an AI explanation: LLMs are helping people who otherwise would struggle move to Linux









  • classic. this has been a problem since the language was new.

    the problem is that Rust is designed to not have this as a use case, or rather has machinery to make this marginally safer (mutexes etc) or make it unstable (panic) or just as unsafe as C (unsafe). if this is a pattern you want to maintain, Rust is going to throw friction at you by design, because tbh this pattern is the source of a ton of bugs.

    it’s conceptually more complicated, but game engine devs have been moving to some form of Entity Component System[1] architecture, because it gives you a way to access memory that is both cache efficient and safe.

    all that said i’m not a game dev. i think Bevy[2] was the blessed solution for a while?

    1: https://en.wikipedia.org/wiki/Entity_component_system?wprov=sfti1 2: https://bevy.org/


  • my hot take is that a distro at the end of the day is just a package manager and an install script.

    the question i would ask is: what do you want out of your package manager?

    this would be an odd question for your given non-Linux user because their package manager before was called “fuck it YOLO”.

    i’ll go through some that i use or have used.

    apt/rpm/etc: stable. designed for the Linux of the 90s. uptime is king. i end up using these usually out of network effects. some popular package uses it in their Docker file or my VPS only supports these. they’re boring, but that’s on purpose. updates are purposeful and vetted (relatively). these are your Debian, Fedora, Ubuntu, etc flavors.

    pacman: seriously just a great design philosophy imo next to the others. rolling release. no versions. fix forward. also with the AUR, you get your “fuck it YOLO” packages back in a way that they can actually be maintained, updated, or nuked as appropriate. if you ever caught yourself waiting for a CUDA release on apt, this is for you. Arch, Manjaro,… i think there’s a ton of vibe coded configs that all pretty much amount to Arch.

    nix(/maybe guix?): a software engineer’s package manager. everything is declarative, reproducible, and version controllable. what was that thing i installed last weekend? it’s in the commit log. need 3 different C compilers/graphic drivers/toolchain dependencies installed? handled by the OS, and cleaned up when those versions change. this is my current rig cuz it helps me keep a bunch of machines in sync for my home projects.

    Gentoo and LFS and anything else would be a bit much.


  • yeah, i mean it’s all bit abstract, but that’s essentially what it is.

    a concrete example would be Nvidia. they’re wildly profitable, and they don’t care how overleveraged you are as long as their barrels full of cash keep coming in.

    i agree with you that there is a concerning amount of debt and leverage going on, but it’s undeniable there’s money changing hands.

    but also, speaking of abstract, all this shit is made up and most of the money “moving” is just flipping some bits in a database somewhere. i also agree with you that it’s all a bit of a facade for people with power to play with power while the true “value” of society such as cost of living and quality of life take a low priority cuz “AI has a $T valuation”. but if you live in this system, this is what it is.




  • i kinda feel sorry for Yann LeCun and his team at FAI. he’s been saying from the beginning that LLMs are not the way forward for AI research as a field, and that has kept Meta from competing in this gold rush effectively. world models, multi-modality, etc are fine and good research but aren’t here to compete with Claude Code or even as effective at being good enough for stuff like search.

    not to be too reductionist, but it’s a tough spot when your head of AI is insisting that this tech has no future when there is a literal $T market for it.

    the irony is that these “frontier labs” like OpenAI and Anthropic have basically dropped every greenfield research project that doesn’t directly support their “agentic AI” infrastructure (ie endless Markdown prompts + a while loop) while the labs working on the true frontier are seen as failures because they can’t make a bazillion bucks burning megawatts of energy to replace their front end devs.




  • people have tried.

    people predicted the enshittification of GitHub as soon as the acquisition was announced, as you can imagine. now, picture yourself as a dev in that month where a small vocal userbase is reading tea leaves based on Microsoft’s past behavior telling you to move your project, where the best outcome is nothing changes, to a new platform. you have a hundred issues and a dozen PRs in review, and those won’t stop coming in while you are migrating. now you need to mirror your project on GitHub, unless you want to immediately fade into obscurity, because while you’re spending your valuable time making sure everything is setup as it was but now on GitLab (the only realistic alt at the time), issues and PRs are still coming in, and you have to keep your releases updated in GitHub for a while during the migration. you also need to figure out CI/CD on your new platform.

    so the ideal—that you can migrate and nothing changes—is a pipe dream. your packaging is now likely totally different; you’re now that snowflake project in the config where i had to figure out how to point to something other than GitHub and waste 30min questioning whether i need your tool at all. you still continue to get PRs and issues through GitHub because of course they didn’t read the README. and there’s tiny friction everywhere. the UI is different, how OAuth is handled is different, the plug and play you got from GitHub Actions is gone, etc etc.

    meanwhile for 6 years things are chugging along fine at GitHub: Actions is getting better, Treesitter support, better UI for PRs.

    it’s the AI stuff that’s ruining GitHub no doubt. not the AI itself but the culture around it with the “what is our team doing with AI?” nonsense corporate policy. it’s all happened really quickly, and isn’t the “boiled frog” scenario at all really.

    Linux was around before GitHub, and wherever we end up as long as we still have our Unix tools like git it’ll be fine.

    ideals are great. the perfect is the enemy of the good