Apologies, I thought after posting, I hadn’t actually answered the question you asked.
For me personally, I find the class based resources easier and I am no developer, the problem is that most of the public resources are MOF based and I can’t work out how to get a mix of class and MOF resources to work in the same “module”. However, it might not be a requirement to wrap them into one module.
The actual .Net part of the resource is / can be fairly small and the rest can be written in traditional PS.
I guess it’s a case of personal preference, although class-based resources mean the MOF file is written out for you, so one less step. There may be some technical differences, but from the field, I haven’t found any negative ones yet and this includes extensive use in Azure.
When I have to write my own, I will always see if I can get away with writing class-based before MOF.