u/blatyo

You should post this on the Elixir forum as well. They tend to get more traffic than this subreddit. There's a section for libraries: https://elixirforum.com/c/your-libraries-os-mentoring/libraries/43

Agreed. Very nice library. Started using it this week for KLL datasketches. Also pretty interested in the apache serialization/deserialization that's planned. Use apache druid for some things and there are instances where it'd be nice to process those server side.

I've been looking around the internet and I think it might be a female fiddler crab. Can anyone confirm?

https://en.wikipedia.org/wiki/Fiddler_crab

https://dreamfish.com.au/wordpress/wp-content/uploads/2013/02/CRAB-Pink-clawed-fiddler.gif

Based on that wiki page, those seem to live everywhere besides where I do. None of them seem to be in North America.

Read this section of the Supervisor docs:

http://elixir-lang.org/docs/stable/elixir/Supervisor.html#module-simple-one-for-one

TL;DR: Use :simple_one_for_one and start_child/2

I can help. PM me.

I would say this is not always good advice. Code organization is also influenced by the business for which it is written. I agree on isolating the client and server, but I don't necessarily agree about keeping them in separate repositories. If you explicitly hire backend and frontend developers, that kind of separation may make sense. Where I work, we explicitly hire full stack developers, so the person who changes the frontend will be the same who changes the backend. Second, ensuring that when changes are made in both the right versions are released can be difficult. If you can tie the build process of both together (we build slugs for both) it is simpler to keep versions in sync. Third, where I work, it is almost never the case that there is only a backend change or only a front end change. Separating the repositories makes management of changes across both more difficult. Fourth, frontends which need to serve content for search engines can require tight coupling and duplication between the client and server. Some workarounds for this exist, which I'm not a huge fan of, like rendering server side with phatom.js. Until search engines can render and traverse client side applications, there will necessarily be some work to do on the server that otherwise would be solely the clients responsibility.

It appears you're using the ruby installed with OSX. Your issue would probably be resolved with a newer version of ruby. Check out this tutorial, for how to do that:

http://ruby.railstutorial.org/ruby-on-rails-tutorial-book#sec:install_ruby

This for example:

UrlsPresenter = lambda do |base_url|
    {
      'self'    => "#{base_url}/me",
      'gauges'  => "#{base_url}/gauges",
      'clients' => "#{base_url}/clients",
    }
end

UserPresenter = lambda do |user|
  {
    'id'          => user.id,
    'email'       => user.email,
    'name'        => user.name,
    'first_name'  => user.first_name,
    'last_name'   => user.last_name,
    'urls'        => UrlsPresenter[Gauges.api]
  }
end

It can in fact be compiled:

http://tedwise.com/2009/10/08/compiling-ruby-with-macruby-0-5b1/

There's warp drive, but engine's are probably better.

You could try the RIT second life if it's still around. My room mate worked in the co-op office and part of his job was to build stuff on there.

http://www.myspace.com/nevergreen

Definitely stuff missing, for example, you can get to the trails from the corner of the grass field behind Gracies.

sqlite3 in the command line or script/console.

That link mysteriously appeared...

Anyway, like what I hear.

Link: http://primaryelement.bandcamp.com/album/hello-world

I'd say its mostly roll your own for now. That said, it should only require a few commands in a bat file to set everything up.

The first issue you would face would be installing a ruby interpreter. The best way to do this would be with the ruby installer for windows. It also supports silent installs, so you can automate it though shell scripts on windows. After this, you should be able to do everything else in ruby.

The next step is to get your application. If it's hosted on github, then you can just download it directly from there (They can create archives on demand of any commit).

The next step I would say you have two options. Find a database that will let you do a silent install like the ruby installer or create an application on heroku to act as a remote database and use Active::Resource to connect to the remote application.

The first approach has the benefit that everything is local and no internet connection would be needed. The second has the benefit that no database needs to be installed on the local machine.

Next you'll need to get the gems your application depends on. You'll have to be careful which dependencies you use because some gems don't support windows and some gems have to compile natively which may be iffy (though, ruby installer has done a lot of work on this).

After that, its the basic things you do to get a rails app up and running (rake db:create, rake db:migrate, rails s). There may be a way to make the server a service so that its always running or you could have something to start and stop it such as a bat file.

Gem naming conventions: http://blog.segment7.net/2010/11/15/how-to-name-gems

It meshes very intuitively to how I think when there is more than one resource to display on a page.

Do they mean plane tickets or just the conference ticket?

Stupid bricks

RIT as well