@akkartik this is how i see it (correct me if I'm wrong):
you take "zero dependencies" seriously because you see the downsides of dependencies. the tadi approach sees that too.
you try to get around that by taking the noble pursuit of building and re-building an entire stack of tools, which is really really hard.
the tadi web gets around it by not needing dependencies in the first place. or if it does use a dependency, it's easily discarded and replaced or re-built. continued...
@akkartik the downside of the tadi style is that you *can't make everything* with it. some things you have to sacrifice being able to make. but the positive is that you're not dependent on any 'dependency'
in your approach, i see you still have dependencies - it's the ones you build for yourself. even though you don't use someone else's dependencies, you end up stuck with your own stack, which is also hard to support, just like a dependency. continued...