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

61–70 of 112 posts

Re: Realm 1.0

#61

Post by ndarilek »

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'm looking for a good geospatial data store that works on mobile devices. Ran into an issue where Spatialite used to corrupt databases larger than 2GB on Android (as in, run md5sum on the database, open it read-only, run another md5sum, notice they've changed.) At the time when I investigated this, the Android support was scattered across both the initial project and a secondary build with a vendored Spatialite, it wasn't clear whose issue it was, and none of the projects seemed interested in claiming ownership or suggesting fixes. The whole experience left me a bit soured on Spatialite as a mobile geospatial data store if your intent was to, say, load large areas for offline navigation. Maybe it'd work better in the case where you're syncing up specific areas, but my interest was in prepopulating with specific datasets for large regions since I was often off-network and couldn't predict whether a dataset would run out in the middle of a dead zone.

Any chance Realm will or does support geospatial data? Couldn't find any indication that it does currently, so if I ever returned to this project then I'd likely suck it up and try to figure out why Spatialite corrupts larger datasets. But having an alternative would be nice.

Re: Realm 1.0

#62

Post by spotman »

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 through the that first has made me a more competent iOS developer.

Realm is the right tool for the job for me in most use cases. Don't see myself switching back anytime soon, keep up the good work!

Re: Realm 1.0

#63

Post by nabil_hachicha »

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.

We're focused more on mobile for now, JVM support is something we want to build. For now we're relying on some Android specific components like the Looper (to deliver notifications) & the Android Context, otherwise most of the API uses pure Java API.

Re: Realm 1.0

#64

Post by android521 »

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…

Do you use your own data synchronization solution? It seems to difficult to do it right. We love Realm but we eventually choose couchbase because of its out of the box sync solution. I hope Realm consider this feature as most mobile developers all have to think about this problem.

Re: Realm 1.0

#65

Post by chris_7 »

jpsim wrote: post #46
chris_7 wrote: post #29

Earlier quoted context omitted.

Is unsigned integer support coming any time soon? Right now I'm using an integer and a computed property (Swift) to reinterpret the bit pattern as an unsigned value, which is... okay, I guess, as the field doesn't ever need to be queried. Filesize really matters in my case, so I don't want to go up an integer size. It just seems like an odd limitation - it's all bits!

(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…

Oh, given the packing, is there any reason to use the property instead of just moving up a size?

Re: Realm 1.0

#66

Post by bigfish24 »

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…

(Adam from Realm) thanks for the kind words! Fine grained notifications were very important to us to support to enable a more reactive architecture. Glad it has benefited your code base!

Re: Realm 1.0

#67

Post by spotman »

android521 wrote: post #64
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…

Do you use your own data synchronization solution? It seems to difficult to do it right. We love Realm but we eventually choose couchbase because of its out of the box sync solution. I hope Realm consider this feature as most mobile developers all have to think about this problem.

Do you mean from server to client?

this is handled by the applications code, which inserts data primarily from a rest api into realm in a background thread. Not all data comes from rest however, some from apns or xmpp, depending on application state and the particular data.

Syncing is hard to get right. If realm offered it I would consider but I would not want them to do that at the sacrifice of making their product as solid as it is.

How does couch handle it? Does it have push and poll type of hooks?

Re: Realm 1.0

#68

Post by jpsim »

chris_7 wrote: post #65
jpsim wrote: post #46

Earlier quoted context omitted.

(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…

Oh, given the packing, is there any reason to use the property instead of just moving up a size?

I'm not sure what you mean here. If you mean "why would I ever use Int8 or Int32, etc. if Int64 won't take up more space in the file" the answer would be memory considerations when you take that data out of the Realm... you should just use the size you need and you'll be ok.

Re: Realm 1.0

#69

Post by bigfish24 »

ndarilek wrote: post #61
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'm looking for a good geospatial data store that works on mobile devices. Ran into an issue where Spatialite used to corrupt databases larger than 2GB on Android (as in, run md5sum on the database, open it read-only, run another md5sum, notice they've changed.) At the time when I investigated this, the Android support was scattered across both the initial project and a secondary build with a vendored Spatialite, it…

(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.

Re: Realm 1.0

#70

Post by tbolt »

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?

Post reply on HN