Cẩm Huỳnh qcam

Functional Programming

Week 1

Programming Paradigms

Main programming paradigms include:

Imperative Programming

What's gRPC?

In gRPC a client application can directly call methods on a server application on a different machine as if it was a local object, making it easier for you to create distributed applications and services. As in many RPC systems, gRPC is based around the idea of defining a service, specifying the methods that can be called remotely with their parameters and return types. On the server side, the server implements this interface and runs a gRPC server to handle client calls. On the client side, the client has a stub (referred to as just a client in some languages) that provides the same methods as the server.

gRPC clients and servers can communicate no matter what programming languages they're written in. For instance, you can easily create gRPC servers in C++ and clients in Ruby/Python.

Transport and Semantics

gRPC uses (Protocol Buffers, aka. Protobuf)(https://github.com/google/protobuf), for data serialization.

What's RPC?

In distributed computing, a remote procedure call (RPC) is when a computer program causes a procedure (this is what it differs from REST) to execute in another address space (commonly on another computer on a shared network), which is coded as if it were a normal (local) procedure call, without the programmer explicitly coding the details for the remote interaction.

There are multiple implementation of RPC: ONC RPC, JSON-RPC, XML-RPC, gRPC, SOAP, etc.

How RPC works?

The client calls the client stub. The call is a local procedure call, with parameters pushed on to the stack in the normal way.
The client stub packs the parameters into a message and makes a system call to send the message. Packing the parameters is called marshalling.

git credential-osxkeychain erase
host=github.com
protocol=https

##Jekyll Installation

Make a new directory for your blog

mkdir my-awesome-blog
cd my-awesome-blog

Create your .ruby-gemset and .ruby-version

##Rails Submit button I18n way

en:
  helpers:
    submit:
      create: "Make New %{name}%"
      user:
        create: "Register"
 update: "Update Profile"

Rails Active Record Query

INNER JOIN

Category.joins(:posts)

# SELECT categories.* FROM categories INNER JOIN posts ON posts.category_id = categories.id

The markup

<div id="parent">
  <a id="child">Click here please</a>
</div>

Instead of binding event this way this way

##Capybara - Wait for ajax to complete

def wait_for_ajax
  Timeout.timeout(Capybara.default_wait_time) do
    loop do
      active = page.evaluate_script('jQuery.active')
      break if active == 0
    end
 end

	# Place your file in ~/.config/hub
	github.com:
	- user: huynhquancam
	oauth_token: XXX # personal token can be obtained from your Github > Settings > Security > Personal Token