• 1 Post
  • 47 Comments
Joined 2 years ago
Cake day: September 5th, 2023
  • nate3d@lemmy.worldtoFirefox@lemmy.world•Is Firefox promoting malware in their extensions page?
    9·
    4 months ago

    Huh? Do you know what tamper monkey even is? It’s simply just a JS injector you can do even with the dev tools with the regular browser now with no extensions installed. This extension simply automates this process and is extensively used for modding browser based games. It’s not malware or for malicious use in and of itself.

    Edit: it’s the name squatting “Tamper monkey” versus the official “Tampermonkey” extension

  • nate3d@lemmy.worldtoProgrammer Humor@lemmy.ml•Docker Building
    3·
    7 months ago

    Yeah! So the first thing that BuildKit provides that greatly improves build time is that it will detect and run the two stages (one, two) in parallel so the wall-clock time for your example is 5s (excluding any overhead). Without BuildKit, these would be built serially resulting in a wall-clock time of 10s (excluding any overhead).

    Additionally, BuildKit uses a content-based cache rather than a step-by-step key cache used by classical Docker. This content-based cache is intelligently reused across different builds and even re-ordered instructions. If you were to build then rebuild your example, the sleep steps would be skipped entirely as those steps are fully completed and unchanged in the content-based cache from the previous build. It will detect changes and re-build accordingly.

    Lastly, (albiet not a BuildKit feature directly) is to leverage inline build caching for things such as dependencies so they are persisted to your filesystem and mounted during build time such that you don’t have to fetch them constantly. This isn’t really necessary if leveraging BuildKit fully since the content-based cache will also handle the dependencies and only pull if changed. i.e:

    RUN --mount=type=cache,target=/root/.cache \
    your-build-command