In _theory_ using a thin-client and booting into a cloud machine means you can "upgrade" your machine in a couple years w/o having to replace the thin-client.
Could be easier for grandma, could reduce e-waste, will definitely be used to pigeon-hole us into an endless hell of subscription software.
I also think "adoptability" should be a consideration. Perhaps AsciiDoc would be a slightly better fit, but every developer I know is already familiar with MarkDown and at the end of the day convincing people to write good docblocks is easier if they don't have to pick up new syntax.
I think Go's generics are reasonable, but not quite powerful enough to scale.
It's all well and good to generalize basic containers and functions (good, in fact), but I wish the language was better at inferring types.
I'm sure this is something that will improve with time, but a bit after generics were released, I tried to build a type-safe language evaluator in Go using generics and found them lacking the kind of type-narrowing necessary for fully-generic architecture.
I think this is an interesting idea, though I suspect "on net the status quo is worse environmentally" is a hard question to answer w/o the aforementioned in-depth reviews (at least to an extent; obviously the current system has problems).
The concept sounds good in theory, but I think it's going to be nigh unworkable in practice. The NCLB/high-stakes testing era exposed many problems with tying educator pay to student outcomes -- chief among them that student outcomes didn't improve.
Could be easier for grandma, could reduce e-waste, will definitely be used to pigeon-hole us into an endless hell of subscription software.