Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)A

akash_rawal

@ akash_rawal @lemmy.world

Posts
5
Comments
8
Joined
3 yr. ago

  • I think Deno made a huge mistake. (Node compatibility)

    Jump

  • Through compatibility, Deno established an upgrade path.

    Sure, but Node compatibility needs to work, and it needs to work reliably. Which means every last detail of Node needs to be supported.

    This is what I am trying to convey... the engineering effort to make an objectively better JS runtime while being Node compatible is likely too much effort. Many popular Node projects are already having issues with Deno. Now imagine how the compatibility scene will look like with every single proprietary Node project out there.

    So instead of trying to replace NodeJS or offering an upgrade path for existing Node projects, incentivize formation of ecosystem around Deno.

  • I think Deno made a huge mistake. (Node compatibility)

    Jump

  • Statistically speaking, you are right.

  • "GitHub CI is easy", he said. "It's just bash ", he said.

    Jump

  • We test our code locally, but we cannot test the workflow. By definition, testing the workflow has to be done on a CI-like system.

    There is nektos/act for running github actions locally, it works for simple cases. There still are many differences between act and github actions.

    It might be possible for a CI to define workflow steps using Containerfile/Dockerfile. Such workflows would be reproducible locally.

  • "GitHub CI is easy", he said. "It's just bash ", he said.

    Jump

  • Time for the yearly barrage of "Setup CI"..."Fix CI" commits.

    That is my experience with basically every CI service out there.

  • I made a library similar to Testcontainers, but works differently.

    Jump

  • Testcontainers uses 'ryuk' to clean up containers and it needs docker socket mounted within its container to work. So if you had any hardening config that prevents the docker socket access within a container e.g user namespace or SELinux then Testcontainers doesn't work.

    And I think it would be nice if Testcontainers 'just worked' with Podman without any additional steps.

  • I made a library similar to Testcontainers, but works differently.

    Jump

  • Nothing else. Though docker socket issue was important enough.

  • Programming @programming.dev
    akash_rawal @lemmy.world

    I made a library similar to Testcontainers, but works differently.

    github.com /akashrawal/disposables

  • Confused about Podman

    Jump

  • For me the value of podman is how easily it works without root. Just install and run, no need for sudo or adding myself to docker group.

    I use it for testing and dev work, not for running any services.

  • Programmer Humor @programming.dev
    akash_rawal @lemmy.world

    Give your JS codebase what it deserves!

    github.com /rohitdhas/shittier
  • Selfhosted @lemmy.world
    akash_rawal @lemmy.world

    Anyone else wants a one box replacement to a switch attached to USB NICs?