jmatsushita

###
### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places. 
###.   Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of 
###.   things to watch out for:
###      - Check out the `nix-darwin` instructions, as they have changed.
###      - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026
###

# I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs).
# So here's a minimal Gist which worked for me as an install on a new M1 Pro.

pdamoc

-- See this document for more information on making Pong:
-- http://elm-lang.org/blog/pong
import Color exposing (..)
import Collage exposing (..)
import Element exposing (..)
import Keyboard
import Text
import Time exposing (..)
import Window exposing (Size)
import Html.App as App

pdamoc

import Html exposing (..)
import Keyboard
import Window exposing (Size)
import AnimationFrame

import Task 
import Html.App as App

import Collage exposing (..)
import Element exposing (..)

evancz

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

1. There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

semarco

##Realtime Analytics

http://www.mongodb.com/presentations/real-time-analytics-mongodb-webinar

http://blog.mongohq.com/first-steps-of-an-analytics-platform-with-mongodb/

http://rubayeet.wordpress.com/2013/12/29/web-analytics-using-mongodb-aggregation-framework/

http://docs.mongodb.org/ecosystem/use-cases/pre-aggregated-reports/

semarco

#SOA

##HATEOAS

http://odino.org/hypermedia-services-beyond-rest-architectures/

http://www.slideshare.net/trilancer/why-hateoas-1547275

##Patterns http://www.infoq.com/presentations/Some-REST-Design-Patterns

semarco

#Dev Tools & Resources

##Web-API Development

RequestBin

Swagger API Docu

jsonAPI.org API-Patterns

basiszwo

AngularJS

Learning Angular

• https://github.com/zafarali/learning-angular
• http://www.angularonrails.com/ruby-on-rails-angularjs-single-page-application
• https://github.com/toddmotto/angularjs-styleguide

Links

• http://angularjs.org/

wongyouth

module Mongoid
  module Serialization
    def serializable_hash_with_id(options = nil)
      json = serializable_hash_without_id options
      json['id'] = json['_id'] if json.has_key? '_id'
      json
    end
    alias_method_chain :serializable_hash, :id
  end
end