It took the JS community many iterations to get to vite. Building it into the language just means you get stuck with a "good enough" solution that survives by inertia. We'd still be using webpack.
replyI'm all for building things into the language when there's only one way to do it though.
Counter point; good enough is often... good enough
replyGo is the best example of this; it's boring but incredible stable and consistent
for sure! but there are lots of incremental shareable primitives that could help. I think about go's built in testing tools that can get extended as an example
reply