Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Realm 1.0

realm.io

Post reply on HN
Print view View original

81–90 of 112 posts

Re: Realm 1.0

#81

Post by spotman »

sametmax wrote: post #73
spotman wrote: post #62

Realm is awesome! I have been using it for a year now in a large production iOS/swift app with great success. Great job on the recent additions to the more fine grain notifications, with this I was recently able to reduce my own code, simplify and increase performance! Core data is good and a powerful weapon, and certainly educational to learn its approach and how to use it effectively. I sometimes ponder if going th…

What's the benefit of using realm instead of Sqlite + an ORM ?

For me it's:

- simplicity, which in turns creates less complex code and less crashes

- performance, which for my use case was faster than sqlite

- slightly opinionated, in that it forces you to not access objects from different threads, which can eliminate a whole class of bugs (you could and should do this or a similar approach to prevent these with whatever solution, but Realm forces it)

Re: Realm 1.0

#83

Post by jpsim »

ttcbj wrote: post #76
timanglade wrote: post #4

VP Product at Realm here. Thanks to everyone on HN for the support over the years! We came out of YC in Summer 11 and it’s been a fantastic ride growing over the past few years. Would love to hear y’alls thoughts on what we should add next. Is there any reason why you’d still use SQLite?

I tried Realm for an OS X desktop app a few months ago. I initially liked it, but was surprised when I discovered the threading requirements (one realm instance per thread, cannot pass realm-based objects across threads). 1) When I see that a library has a note about threading, I generally expect that it will either be "its thread safe" or "these operations are not thread safe and you need your own synchronization."…

(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 could read through the "Threading" section of our docs[1] and share how you think it could be improved.

[0]: https://github.com/realm/realm-cocoa/issues/3136 [1]: https://realm.io/docs/swift/latest#threading

Re: Realm 1.0

#84

Post by coldcode »

Is having to use the Realm objects in the same thread they were created it much of a burden on how you use it? Having not tried it yet I wondered about that limitation.

Re: Realm 1.0

#85

Post by jpsim »

coldcode wrote: post #84

Is having to use the Realm objects in the same thread they were created it much of a burden on how you use it? Having not tried it yet I wondered about that limitation.

(JP from Realm here)

It certainly forces you to think about threading (which is a good thing IMO). I just responded to a similar comment[0], and there are always our docs on threading[1] which I'd encourage you to read.

[0]: https://news.ycombinator.com/item?id=11771558 [1]: https://realm.io/docs/swift/latest#threading

Re: Realm 1.0

#86

Post by tokenizerrr »

mwcampbell wrote: post #58
tokenizerrr wrote: post #56

What about using realm Java outside of Android? The readme says: > This repository holds the source code for the Java version of Realm, which currently runs only on Android. I'm interested in trying this on the desktop (windows/linux/mac), but that doesn't seem possible? Wonder what makes it android only.

The core of Realm is closed-source, and Realm only provides builds for iOS, OS X, tvOS, and Android.

Oh, missed that bit.

Re: Realm 1.0

#87

Post by ckurose »

tbolt wrote: post #70
hackim wrote: post #32

I'm using Realm for my React Native project it awesome! Thanks Realm team.

Likewise. Really making me happy so far. Is react native going to be 1.0 shortly? Or is that not included in this release?

Chris from Realm here - we're definitely working toward 1.0 for React Native as well, but it won't be part of this release :).

Re: Realm 1.0

#88

Post by flipgimble »

Realm has excellent marketing, but being a closed source third party SDK disqualifies it as anything I would recommend for my company to use.

I've had to deal with enough pain from closed source libraries from the likes of Google and others. Closed-source prevents me from adopting a new platform until the vendor gets around to porting it, and only if it fits with their strategy. Also a middleware-only company is liable to be bought out, and then closed. Example: Parse.

Post reply on HN