3 ms·
Clear article, I honestly don't have much to add to the main thesis of it, other than that I'm very curious to see how well the arguments will hold up when face
by vanderZwan 6y ago
Clear article, I honestly don't have much to add to the main thesis of it, other than that I'm very curious to see how well the arguments will hold up when faced with "real world" usage, and how Deno will evolve.
But if I may indulge in a bit of bike-shedding on the side, does anyone else think that the repeated URLs in the example dependency tree are a bit noisy and hide the deeper structure of the dependencies?
https://deno.land/x/oak/examples/server.ts
├── https://deno.land/std@0.53.0/fmt/colors.ts
└─┬ https://deno.land/x/oak/mod.ts
├─┬ https://deno.land/x/oak/application.ts
│ ├─┬ https://deno.land/x/oak/context.ts
│ │ ├── https://deno.land/x/oak/cookies.ts
│ │ ├─┬ https://deno.land/x/oak/httpError.ts
│ │ │ └─┬ https://deno.land/x/oak/deps.ts
│ │ │ ├── https://deno.land/std@0.53.0/hash/sha256.ts
│ │ │ ├─┬ https://deno.land/std@0.53.0/http/server.ts
│ │ │ │ ├── https://deno.land/std@0.53.0/encoding/utf8.ts
│ │ │ │ ├─┬ https://deno.land/std@0.53.0/io/bufio.ts
│ │ │ │ │ ├─┬ https://deno.land/std@0.53.0/io/util.ts
I'm not entirely sure what would be the ideal alternative presentation though. Perhaps something along the lines of one of these two mock-ups I just edited by hand:
https://deno.land/
└─┬ x/oak/examples/server.ts
├── std@0.53.0/fmt/colors.ts
└─┬ x/oak/mod.ts
├─┬ x/oak/application.ts
│ ├─┬ x/oak/context.ts
│ │ ├── x/oak/cookies.ts
│ │ ├─┬ x/oak/httpError.ts
│ │ │ └─┬ x/oak/deps.ts
│ │ │ ├── std@0.53.0/hash/sha256.ts
│ │ │ ├─┬ std@0.53.0/http/server.ts
│ │ │ │ ├── std@0.53.0/encoding/utf8.ts
│ │ │ │ ├─┬ std@0.53.0/io/bufio.ts
│ │ │ │ │ ├─┬ std@0.53.0/io/util.ts
https://deno.land/x/oak/examples/server.ts
├── https://deno.land/std@0.53.0/fmt/colors.ts
└── https://deno.land/x/oak/
└─┬ mod.ts
├─┬ application.ts
│ ├─┬ context.ts
│ │ ├── cookies.ts
│ │ ├─┬ httpError.ts
│ │ │ └─┬ deps.ts
│ │ │ ├── https://deno.land/std@0.53.0/
│ │ │ │ ├── hash/sha256.ts
│ │ │ │ └─┬ http/server.ts
│ │ │ │ ├── encoding/utf8.ts
│ │ │ │ ├─┬ io/bufio.ts
│ │ │ │ │ ├─┬ io/util.ts
I'm sure there are good arguments to be made against both of these options as well - plus I just came up with this on the spot, I don't even know which "rules" would generate such a tree.