# om

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

chris-andrews 00:07:24

I’m using om alpha 47, and it looks like I can get the component associated with a query directly through the ast using the :component key. But in some of the source, it looks like it is taking the component information from the :query key metadata. Is there any reason I should use one of these over the other in my own code?

keatondunsford 06:46:59

Hey @dnolen @anmonteiro, have either of you thought of replacing om.dom with a CLJS equivalent of React-Native-Web?

I know that indirectly there has been mobile emphasis of Om Next for React Native via re-natal. But it would be so cool if there was a direct effort in the Om project to make Om work on any platform, comprising just one epic framework to “write once, run anywhere” — be it the browser, mobile, desktop or even Windows, with just a few minor tweaks. Om would totally conquer JS land once and for all. :heart:

afhammad 12:10:16

Thanks @danielstockton. That seems to be the only example out there.

danielstockton 12:13:15

you can also look at #untangled, this is created for a real application and sees more real-world usage (probably)

danielstockton 12:13:29

its a framework built on top of

danielstockton 17:00:21

Would a patch to add <use> to om.dom be welcome?

levitanong 18:19:48

@danielstockton afaik React itself doesn’t support use, and in fact it used to be in om until we found some issues. For now, try using the create-element function in master (i think 48 hasn’t been published on clojars yet)

danielstockton 21:13:08

Thanks, I did not know about create-element