14 ms·
So it's doa because it shedded some fairly major legacy tech debt in npm and the commonJS format? While I have concerns about the dependency management style o
by tehbeard 6y ago
So it's doa because it shedded some fairly major legacy tech debt in npm and the commonJS format?
While I have concerns about the dependency management style of deno being looser than node's package.json, I do think it is a net positive with realigning to "web standard library" over reinventing interfaces for everything.