So let's assume there was wide spread consensus that it's a terrible idea and it should work like every other programming language. There is really no obvious way to simply "convert to the new syntax"? And trying to have "go with nil interfaces" library interact with "go with normal type system" would be it's own can of worms.
Like in this case, the only realistic path I could see would be you deprecate it, then you start warning, and then in like 10 years or something you fully remove it?
I'm not familiar with that area, but considering it's not coastal it seems hard to believe the water is simply wasted once it goes into the ground in the lower Colorado basin.
It depends a lot on where the farm is, how much they irrigate, and when they irrigate. But often something like >90% of the water goes back into the ground, where it will eventually make its way back into the aquifers and rivers.
It's why often farm water usage is not nearly as bad as it superficially seems, and why farm water usage of a river can be multiples of the actual river flow
Definitely. It's a shame that dart gets so much unwarranted hate. I mean, I also think it's an absolutely awful language but it's really proven to be a valuable source of data for what other programming languages should do and perhaps more importantly: not do. I really hope we see a lot more things like Dart, and not so much negativity.
So let's assume there was wide spread consensus that it's a terrible idea and it should work like every other programming language. There is really no obvious way to simply "convert to the new syntax"? And trying to have "go with nil interfaces" library interact with "go with normal type system" would be it's own can of worms.
Like in this case, the only realistic path I could see would be you deprecate it, then you start warning, and then in like 10 years or something you fully remove it?