Live data from Hacker News

Pstore: Ruby Built-In Hash Persistence

github.com

1–10 of 42 posts

Re: Pstore: Ruby Built-In Hash Persistence

#4
I would think this would have limited usefulness for most web applications as the latest trend for web apps is to think of the deployed code as ephemeral, and local files are not something devs often rely on. I guess if you're mounting block storage or some other virtual file system that would be another thing. For non-web applications, this could be a simplistic replacement for what people often use sqlite for. The readme doesn't talk much about concurrent access to the store other than the transactions, so concurrent operations may also be a limitation.

Re: Pstore: Ruby Built-In Hash Persistence

#7
post #3

I do a lot of ML and AI work nowadays... I miss Ruby a lot especially the its culture around ergonomics.

I recently had the need to build an internal system that distributed workloads across many workers via a client/server model. I did the proof-of-concept using druby [1] and it turned out to be so simple and stable that we just ran with it. It'd been years since I had used that library and instinctively I assumed we'd get the prototype out and then rebuild it using some sort of web service and utilize a high concurrency web server but druby just worked!

[1] https://github.com/ruby/drb

Re: Pstore: Ruby Built-In Hash Persistence

#8
Don't use this. Marshal has too many issues. If you really need persistence and can't use something like Postgres, use the Ox gem instead. It's more reliable between versions of Ruby and easier to parse from other languages if you ever have to.

Re: Pstore: Ruby Built-In Hash Persistence

#9
post #3

I do a lot of ML and AI work nowadays... I miss Ruby a lot especially the its culture around ergonomics.

There have been some interesting ML gems rolled in the past few years:

https://ankane.org/new-ml-gems

Any thoughts on what the Ruby community would need to build in order for it to become an attractive tool for AI work?

Re: Pstore: Ruby Built-In Hash Persistence

#10
post #8

Don't use this. Marshal has too many issues. If you really need persistence and can't use something like Postgres, use the Ox gem instead. It's more reliable between versions of Ruby and easier to parse from other languages if you ever have to.

> too many issues

Such as?

Post reply on HN