> I've never understood the need to keep code "up to date" with idioms. It helps with readability to have everything using the same idioms, and it helps with q

> I've never understood the need to keep code "up to date" with idioms. It helps with readability to have everything using the same idioms, and it helps with quality to have everything using the best idioms. > Most of the time idioms change incrementally Incremental changes stack up over time. > the seismic shifts I can think of a) have happened pretty much only once in a language's life, big changes happen much more often in new ecosystems > and b) were basically an admission that the original language design was bad and/or insufficient in some way. Yeah. If I'm considering whether to join a language, I want to know if they have so many unresolved problems that they're still fixing them all the time. Slowness is related to maturity.