What caught me wasn’t the fact that Dusk supports two execution environments. It was the reason that choice might become awkward later.
So DuskVM gives native Rust/WASM developers their own path, while DuskEVM keeps Solidity teams inside familiar tooling. That’s practical. Developers don’t have to throw away everything they already know just to build on Dusk.
The complication shows up after adoption starts working.
If both environments attract real applications, Dusk could end up with two developer cultures growing side by side. Different tooling, different contract habits, different expectations around how apps interact.
That doesn’t necessarily break anything. But it can make the ecosystem harder to keep coherent.
The part I find interesting is that Dusk maybe reducing one kind of friction while quietly creating another. Getting developers in becomes easier. Making the two worlds feel like one network could become harder.
I’d be watching what happens once users stop caring which environment an app lives on. That’s probably when this design choice gets properly tested.
@Dusk_Foundation $DUSK #dusk
So DuskVM gives native Rust/WASM developers their own path, while DuskEVM keeps Solidity teams inside familiar tooling. That’s practical. Developers don’t have to throw away everything they already know just to build on Dusk.
The complication shows up after adoption starts working.
If both environments attract real applications, Dusk could end up with two developer cultures growing side by side. Different tooling, different contract habits, different expectations around how apps interact.
That doesn’t necessarily break anything. But it can make the ecosystem harder to keep coherent.
The part I find interesting is that Dusk maybe reducing one kind of friction while quietly creating another. Getting developers in becomes easier. Making the two worlds feel like one network could become harder.
I’d be watching what happens once users stop caring which environment an app lives on. That’s probably when this design choice gets properly tested.
@Dusk_Foundation $DUSK #dusk