realm-swift

I got a warning today when submitting my app that said I was using a private API function. Turns out they've essentially blacklisted certain function names that match anything in one of their private frameworks. Renaming functions (making a breaking change) is apparently necessary to avoid this: https://github.com/realm/realm-swift/pull/7951

The Apple bug report was filed by my colleague, JP, after we noticed that the built size of Realm's frameworks dramatically increased after updating to Xcode 8.3. We pay attention to the built size of our frameworks as we distribute precompiled versions of them (https://github.com/realm/realm-cocoa/releases), and a signifiant size increase inconveniences our users. We've not tested the impact of the size on an app installed via the App Store, but since the increase is limited to the bitcode portion of the binary we have no reason to think it will be affected.

The core database that powers all the versions of Realm was open-sourced today here: https://github.com/realm/realm-core The various SDKs that use the core for each mobile platform have always been open source, such as realm-cocoa: https://github.com/realm/realm-cocoa

Any updates on the C++ API and lib? It's been pending since a year[1] and there are no updates :-( [1] https://github.com/realm/realm-cocoa/issues/2198

What part of it is closed source? https://github.com/realm/realm-cocoa https://github.com/realm/realm-java https://github.com/realm/realm-js https://github.com/realm/realm-dotnet Edit: Apparently not the guts of it, my bad :(

(JP from Realm here) Realm's transactions are entirely ACID, and all transactions are thread safe. This means you can't get "faults" like you would in Core Data if one thread deletes an object being accessed in another. On the flip side of this, it makes it difficult to share mutable object graphs across threads, mostly because then you'd need to know which Realm and which object is at what version of the db. Realm's underlying db engine supports this, but it's difficult to expose/enforce at the API level. We have some designs in mind to allow scoping around passing objects between threads (see #3136[0]), and some other ideas for passing immutable Realms across threads, so you can expect to see some improvements there in the future. About improving our documentation around threading, we're always open to feedback. I'd appreciate if you co

(Adam from Realm) we don't offer support for geospatial data yet. An issue to track this was created for Realm Cocoa: https://github.com/realm/realm-cocoa/issues/2569 We don't have a similar issue open for Realm Java, so it would be great if you could create one and detail your needs so we can work to support it.

(JP from Realm here) Unless I'm missing something, what you're describing could easily be done by having the version number or branch in the Realm path, or whatever identifier you want. You should open an issue[0] so we can explore that more. Strings are indexed, but I think you're referring to something like "full text search"? That's on the roadmap[1]. [0]: https://github.com/realm/realm-cocoa/issues/new [1]: https://github.com/realm/realm-cocoa/issues/3650

(JP from Realm here) Yes, it's all bits, but those bits matter :). The internal query engine is extremely optimized based on the layout of those bits, on a per-architecture basis. Also, integers are adaptively bit-packed, so you shouldn't worry about the size of your integers, as Realm will intelligently use the appropriate widths. I'd suggest continuing to use this computed property pattern and to keep track of #651[0] where we're tracking better support for this. [0]: https://github.com/realm/realm-cocoa/issues/651

(JP from Realm here) Yes, that's something we're hoping to add! We're tracking that feature as #3384[0]. Still needs some design work though. [0]: https://github.com/realm/realm-cocoa/issues/3384

The framework in our release zip only works for iOS but if you build from source[0] it will actually generate an OSX framework as well! [0] https://github.com/realm/realm-cocoa#building-realm

Thanks for the kind words! Regarding wiring this to a TableViewController, we have some code samples already for Swift[0] and Objective-C[1]. Right now you get notified of changes and refresh, but we’re very interested in exposing a reactive-style binding mechanism as well. The storage engine underneath supports that very well actually, so stay tuned… [0] https://github.com/realm/realm-cocoa/tree/master/examples/swift/RealmSwiftTableVie… [1] https://github.com/realm/realm-cocoa/tree/master/examples/objc/RealmTableViewExample

Realm currently supports Swift, though we're actively working to improve our Swift APIs[0]. You can find Swift sample code throughout our docs[1], and in our Swift examples on GitHub[2]. We learnt a lot about Swift introspection and interacting with Swift objects from the Objective-C runtime. We'll share our findings in some upcoming blog posts, so stay tuned! [0]: https://github.com/realm/realm-cocoa/pull/549 [1]: http://realm.io/docs [2]: https://github.com/realm/realm-cocoa/tree/master/examples/sw...