The Jade 2025 release focuses on modernising the developer experience and helping you build faster, smarter, and more scalable applications.
We have a isEmpty method on collection - most of the time I'm checking if its not empty so just putting a not at the front - I think having a isNotEmpty Jade native method would be easier to read and a handy feature for devs.
We've mostly changed to the Object.hasMembers() method, mostly for Locking benefits.
For what it's worth we added our own method to the Collection class in our top-level base schema for this very reason. And as the RootSchema implementation of Collection::isEmpty is a Jade method, not an external method, there's no noticeable performance hit to implementing it ourselves.
Note
We didn't code return not self.isEmpty(); though, as the isEmpty method probably does something like return self.size() = 0; or similar, so we just coded return self.size() > 0; in our implementation to avoid another level of method call. We also named our method hasEntries rather than isNotEmpty so that it reads as a more positive statement in the code when we use the method.
Hope that helps,
BeeJay.