rhgraysonii

Some of the AMA can be found on Archive https://web.archive.org/web/20150701154352/https://www.reddi...

Just added the all past versions feature to the API now.

I just saw this now, sorry for being 5 days late if you even end up noticing it.

The typing is governed by YAML standards. This is why symbols are left out. Since it uses `YAML.dump` and `YAML.load` with the set/get, it will automatically assume the string '1' is an integer, '1.0' a float, and so on.

> is it possible to enumerate the versions of key-values that have been saved?

Yes, using the `get_version` method, you could do something like:

    all_items = $ITEMS[key].map { |hash| db.get(hash) }

I should add this as a normal function to the API. Its now on my todo list.

Any plans for Linux support?

As I said to the other comment I replied to, I didn't mean to indicate this was a fact for all. Simply my experience.

I was speaking for me personally, I apologize if that wasn't clear enough. I don't try and speak for others best interests.

As a developer who has been prescribed this after a fit of what could only be described as 'true mania' in my college years, I consider this statement somewhat disturbing from a personal perspective. I quite literally functioned as a zombie while on this nightmare of a substance. I ended up opting to spend double digit hours a week in therapy and implementing a system of Cognitive Behavioural Therapy over living my life in a cloud of misery after over 4 months on it. I'd rather feel and have to keep myself in check over function as a zombie barely capable of running a cash register or reading a real book.

For reference: I've never had a mania or true low since working with it this way, and if I did I would immediately seek a medicated solution knowing the severity of the situation. But, I've managed to hold a full time job, excel my career more than I thought possible, and generally be quite well physically professionally and mentally without it.

Just wanted to say thanks for all the input, pull requests, and ideas to develop this further with. :) Really appreciate it HN!

That's awesome (though frustrating w.r.t the last tidbit). I always find working on 'hacky' or 'pointless' things often yields the most new knowledge and insight. I'm reminded of Jim Weirich's 'Y Not: Adventures in Functional Programming' talk.

Hunna Fresh! I miss you, man. Hope life is good! :)

PS I emailed you the other day.

Someone added a PR with some benchmarks. Here they are on my system doing 1000 set/gets each time in 4 blocks [core i5, 8gb ram, ubuntu 15.04]

    user     system      total        real
    set:      0.150000   0.080000   0.230000 (  1.093421)
    hash set: 0.110000   0.120000   0.230000 (  1.085441)
    get:      0.150000   0.040000   0.190000 (  1.091698)
    hash get: 0.110000   0.060000   0.170000 (  1.075470)

This would hopefully play well with the potential of use of a more robust git tooling like rubiquity had mentioned in another comment. I had thought about the gc aspect but didn't dive into it too much since its so immature still. Definitely will be considering all this as I plan 0.3. Thanks.

That would definitely be interesting! My JavaScript is rusty, it would be a good excuse to do a refresher. Bookmarked and added to my todo notes :)

> My only shock here is that this wasn't done sooner.

This was my initial reasoning for making it. However when I began looking into it on Twitter @steveklabnik informed me that Rust's crates.io uses a similar system [0]. I found this especially intriguing, but have not gotten in touch with someone who knows the codebase better to give me some more insight.

[0] https://twitter.com/steveklabnik/status/608778665825083392

I've done no benchmarking yet. It is a piece that evolved initially from a project I was doing to just explore git's innards a bit more. I eventually gave a talk on what became v0.1 of this (only string store, no typing) at the Columbus Ruby Brigade, and have just been hacking on it a bit in the last couple of weeks because I've found it intriguing.

> This is non-persistent as it relies on the global `$ITEMS`, right?

In a sense. $ITEMS is a hash ruby-object whose keys are what is set as the key by the input, but its values are the hashes that are stored in the git filesystem. There are about 10,000,000 improvements this could have and by no means would I consider it production quality software. Any ideas on a better means of persistance knowing this? Could back up the dict itself as a string in the git filesystem and have it be restorable on instantiation, possibly...

This is definitely a plan in the future. My initial use case was operating off of the assumption that whatever server I would be running this on would have git pre-installed, so it was a simple way to get it up and running quickly. Thanks for the recommendation, its definitely towards the top of my todo list for 0.3 :)

Author here. Would be happy to answer any questions or clarify things. Its very much moreso a 'fun/useful toy' than 'production software' but there are some interesting principles that tie into it.

I don't know enough to truly speak on this, but it honestly sounds to me as if you are someone who is very rational and thinks before acting. If this is a detriment to your employer...I don't know what to tell you.

I have not taken a job through it, but I have met many interesting startup team members that I have kept in touch with on an ongoing basis from the platform. I am currently experimenting with it in partnership with a local group that has had a successful kickstarter and is looking for an angel/seed investor to bolster their first production run (product, not software based startup).

While I know this paper carries signifiance, I have to ask: has anyone here actually read this and completely grokked it? While I am far from a point to truly understand the entire thing, I find it somewhat confounding that some of the most brilliant folks I know who possess Master/PhD level degrees in CS admit openly to not truly understanding the whole thing.

I'd love to see a breakdown of it that might make understanding the more fine-grained pieces in a deeper/more complete sense.

Maybe I'm an edge case, but I have never once had to deal with a whiteboarding session in a single interview I have been in. Though, this is obviously a small sample. I've worked at one startup, largely contracted otherwise, and am just now looking to join another.

Largely my experience has been 1/2 to full day pair programming sessions, building a sample application that does something reasonably nontrivial, or a combination of these two.

I really personally enjoy this practice. Even though a day of billed hours is a large opportunity cost, so is the expense of potentially hiring a bad fit for the team. It goes both ways.

Author here. Obviously this is purely an experiment/toy. But it was quite fun digging into the guts of git to use it this way in a light fashion. Happy to answer questions and/or take feedback.

I would recommend starting with a calculus book. If you aren't comfortable enough with the trig side of things, do a refresher on OCW or Khan Academy.

This book is my personal favorite.

http://www.amazon.com/Calculus-Practical-Man-J-Thompson/dp/1...

If you get on angel.co and search 'marijuana' you can find a list of investors that have funded such things. As well as startups in the space.

What I mean is lets say I do this:

Save my Bench Press

Save my Dead Lift

Now, I will have the success * message at the bottom from submitting my Dead Lift, but if I go to the bottom and delete it, this success message is still showing, even though I have deleted the value.

Adding a simple event handler for the click of the delete button to empty the container containing success messages would handle this.

A couple points I noticed toying with it --

Using the back button seems to keep trying to resubmit the form and break the page for me.

Also, you could remove the last result when an item is deleted from the page. It was displaying a record I had deleted because it was also the last submitted.

Really like the concept. I've always been a fan of doing core lifts like this and generally just keep it all in a notepad I jot on after I leave the gym.

I don't mean this as a knock on the author, but outside of full-scale books does anyone know of some resources that go more in depth with building nontrivial systems/apps/programs in Elixir? I would love to dive further but I find my limitation at this point is my understanding of OTP and the core methodologies, but want to get some more familiarity before I take a dive in as deep as a book would require time-wise.

That said, awesome illustration of building something useful with a minimal codebase and really embracing the nature of what the language is built upon. :)

Out of curiosity (not ragging on your decision at all) why are you going this route?

No problem. Keep up the wonderful work :)