If you want to jump in and see what it looks like, explore the Dak Tour.
Browser output is an important goal. Specifically, small bundle size and tree shaking for pay-as-you-go, are key considerations that determine the design choices. If you are making a browser based application in Dak, a Vite based setup is the recommended choice. ES Modules support is virtually required and baked in.
CLI tooling using
node can be built using the ESM Loader.
It provides a loader but otherwise doesn't get in your way. Maybe look at
inspiration. For one off use
npx @daklang/cli can do in a
npx adds considerable overhead.
A language needs an ecosystem. Formatting, LSP, VSCode extensions, REPL, unit testing, benchmarking and so much more. We don't have much here.
Macros and the programmable aspects of Dak are what I consider to be it's selling points. It's much easier to achieve this in a Lisp like language. These are still very much a work-in-progress. Expect heavy iteration here.
It's all a bit fuzzy, but a seemingly good near term goal is to provide a fun, featureful and fast development experience to build browser based UX applications that can use hiccup like syntax and leverage React, lit-html or Solid.