"Angular Material 2 is still missing a few essentials, but it is a good idea to speed up work on Material 3 now. Angular 3 will be out soon and many people will be unable to switch until Material 3 has caught up with the original."
? If one fears that, it may be better to switch to another library.
I also hope it will become somewhat easier to switch from Angular 2 to a different framework or from Material 2 to a different UI framework, because the new JavaScript language features create obvious best practice solutions where frameworks previously had to come up with their own conventions.
I expect huge changes. I foresee a future where each webpage is an almost empty <html/> tag that does little more than defining a grid that loads a big blob of WebAssembly that builds the actual 'page' (if you can still call it that by that time). One advantage would be that, say, a Python or Rust framework can run Python/Rust in the browser. Another 'advantage' would be that large companies could keep their front-end code more secret (WebAssembly obfuscates better than minifying does)