@DamianEdwards Given the nature of scripts the tendency is to manage a single file. With C# pkgs are a necessity for the most part. Would include also cover nuget pkgs? Then dotnet CLI would just build and run
One of NDL's core promises is **polyglot support**: the same workflow works whether you're using Node.js, Deno, .NET, or any other runtime. -> https://t.co/5vw8ELMdz7
12/ Question for you:
What local dev pain points do you face with distributed systems?
Port conflicts? Manual wiring? Config drift? Integration failures?
Would love to hear what makes local dev painful for your team.
1/ "Works on my machine" syndrome—solved.
NDL brings production patterns (DNS, gateways, service discovery) to local dev. Test distributed systems the way they run in production.
Blog post → https://t.co/qLGgXOEoVh
5-min demo → https://t.co/USuz2CjzsZ
🧵 How it works:
8/ We're not recreating Kubernetes locally.
We're borrowing its architectural ideas:
- Declarative resources
- Reconciliation loops
- Operator ownership
And making them work for laptop-first development.