# Improving Motoko's programmability **URL:** \ **Category:** Language Support\ **Tags:** Motoko\ **Created:** [February 18, 2022, 1:54am UTC](https://forum.dfinity.org/t/improving-motokos-programmability/10952 "2022-02-18T01:54:06Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![claudio](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/claudio/32/322_2.png) [@claudio](https://forum.dfinity.org/u/claudio)\ **Post date:** [February 18, 2022, 11:24am UTC](https://forum.dfinity.org/t/improving-motokos-programmability/10952/7 "2022-02-18T11:24:29Z")
Exposing Candid to/from Blob serialization is not difficult and largely already supported by the compiler, but not exposed. It would be easy to add as a dedicated construct (similar to debug\_show) but harder to surface as a library. I would be very reluctant to add reflection to the language as it breaks all sorts of properties of the language itself and introduces much overhead. It sounds like you are mostly interested in reflecting on candid interfaces, not all Motoko features. That seems like a more reasonable ask and I can see the applications for that. However, even though canisters currently can expose their textual interfaces using a (hidden) text based query (that’s how icrocks obtains them) we’d probably want something with more structure than just text for a programmatic interface. --- _[View the full topic](https://forum.dfinity.org/t/improving-motokos-programmability/10952)._