I haven’t even powered the thing up yet, because without debugging it’s just a frustrating toy (not fit for real apps), and I have enough less-frustrating toys that I’ve been meaning to get to.
Even with a fully functional Meadow, you’re trading one interpreter family (netmf/tinyclr/nano) for another (mono) and gaining syntactic sugar, but losing a lot of performance, community support, and ready-for-use functionality, while simultaneously driving up BOM cost.
The economic benefit of .net interpreters is the reduction in development cost balanced against small runs of increased BOM cost. Meadow devices add a bunch of BOM cost in exchange for very marginal (promised) feature and productivity gains, so beyond hobby use, the economics of fielding these devices seems out of whack. Nevermind that they aren’t ready for real dev work yet.