3 ms·

One issue that's been bothering me about Deno is this one: https://github.com/denoland/deno/issues/14244 https://github.com/denoland/deno/issues/14244 You hav

One issue that's been bothering me about Deno is this one: https://github.com/denoland/deno/issues/14244 https://github.com/denoland/deno/issues/14244 You have to use a third-party Docker container if you want to use Docker locally and develop on an M1 Mac (I use Docker to separate my different dev environments). And the issue was just ignored and became stale.

brundolf 4y ago
You don't really need Docker even with Node (because it has good dependency management), and especially with Deno (good built-in tooling too)
- spartanatreyu 4y ago
  > You don't really need Docker even with Node I'm assuming you've never run into node-gyp issues then?
  - brundolf 4y ago
    In my experience they're pretty rare. Not many Node packages need a native build (mostly node-sass in my experience, which has now been deprecated in favor of a Dart implementation which I believe compiles to JavaScript), and I don't think Deno even supports importing non-JS/WASM modules to begin with, so that type of problem should be fully impossible here
    - spartanatreyu 4y ago
      I usually see these binary dependencies in node projects: - sass - imagemin-gifsicle - imagemin-jpegtran - imagemin-optipng - imagemin-svgo Deno does support native plugins, so we could see the same thing happen there.
      - brundolf 4y ago
        I think there's still a meaningful difference between runtime plugins (which to my understanding have to exist locally on the file system, outside of normal dependencies) vs normal dependencies that just sometimes have a native component. Deno projects won't occasionally accidentally have a native dependency like Node projects do; adding one will be a Big Deal that you choose to do on purpose, probably reserved for extreme cases, and for those special cases maybe you also choose to bail out and use Docker
    - pjmlp 4y ago
      Dart has AOT/JIT support since version 2.
nl 4y ago
That's "just" the lack of an ARM64 image. That is annoying and they should fix but the workaround (of using someone who has built the image) isn't unreasonable. You still see this frequently in a number of ecosystems (eg https://stackoverflow.com/questions/70061068/could-not-find-a-version-that-satisfies-the-requirement-mediapipe-from-versions/72724056#72724056 https://stackoverflow.com/questions/70061068/could-not-find-...)
LAC-Tech 4y ago
Yeah they also can't produce musl libc binaries - so no alpine linux either. Regardless, my experience on the platforms it works on has been very positive.

brundolf 4y ago

You don't really need Docker even with Node (because it has good dependency management), and especially with Deno (good built-in tooling too)

spartanatreyu 4y ago
> You don't really need Docker even with Node I'm assuming you've never run into node-gyp issues then?
- brundolf 4y ago
  In my experience they're pretty rare. Not many Node packages need a native build (mostly node-sass in my experience, which has now been deprecated in favor of a Dart implementation which I believe compiles to JavaScript), and I don't think Deno even supports importing non-JS/WASM modules to begin with, so that type of problem should be fully impossible here
  - spartanatreyu 4y ago
    I usually see these binary dependencies in node projects: - sass - imagemin-gifsicle - imagemin-jpegtran - imagemin-optipng - imagemin-svgo Deno does support native plugins, so we could see the same thing happen there.
    - brundolf 4y ago
      I think there's still a meaningful difference between runtime plugins (which to my understanding have to exist locally on the file system, outside of normal dependencies) vs normal dependencies that just sometimes have a native component. Deno projects won't occasionally accidentally have a native dependency like Node projects do; adding one will be a Big Deal that you choose to do on purpose, probably reserved for extreme cases, and for those special cases maybe you also choose to bail out and use Docker
  - pjmlp 4y ago
    Dart has AOT/JIT support since version 2.

nl 4y ago

That's "just" the lack of an ARM64 image. That is annoying and they should fix but the workaround (of using someone who has built the image) isn't unreasonable. You still see this frequently in a number of ecosystems (eg https://stackoverflow.com/questions/70061068/could-not-find-a-version-that-satisfies-the-requirement-mediapipe-from-versions/72724056#72724056 https://stackoverflow.com/questions/70061068/could-not-find-...)

LAC-Tech 4y ago

Yeah they also can't produce musl libc binaries - so no alpine linux either. Regardless, my experience on the platforms it works on has been very positive.