To get promoted at Google, you need to demonstrate project complexity so engineers is required to build new frameworks. Is it quite risky to adopt an AdWords framework (like GWT) which has high chance of being deprecated?
I believe as long as a technology is truly open source, you can fork, build and use it independently, your risk is minimal - be it Dart or any of its alternatives. Worst case: you have a stack that can operate for several years, long enough time for a business product to get migrated. If it is hobby project, you may be compelled to explore a new tech stack soon enough anyway.
As I mentioned in my longer post, I have considered alternatives. Dart's position was strengthened because the code analyzer is very advanced and easy to use. On the low-probability scenario where Dart development would cease, and I'm left with an important Dart codebase, I would have good chances that I could automatically transpile most of my app to a new stack (assuming I'm using enough type annotations).
However, as I follow Dart development and community closely, I believe there is very little risk of getting it abandoned anytime soon.
As I mentioned in my longer post, I have considered alternatives. Dart's position was strengthened because the code analyzer is very advanced and easy to use. On the low-probability scenario where Dart development would cease, and I'm left with an important Dart codebase, I would have good chances that I could automatically transpile most of my app to a new stack (assuming I'm using enough type annotations).
However, as I follow Dart development and community closely, I believe there is very little risk of getting it abandoned anytime soon.