Rhio Kim rhiokim

## nodecamp.eu-talks-2011.md

      
              1 file
            
          
              4 forks
            
          
              5 comments
            
          
              4 stars
            
          
                fhemberger
                / nodecamp.eu-talks-2011.md
            
            
              Created
              June 13, 2011 11:31
            
              
                A collection of talks and presentations held at nodecamp.eu 2011
              
          
    ##Using libuv and http-parser to build a webserver
Ryan Dahl, @ryah

http://vimeo.com/24713213

Source, Part I: http://t.co/utoIM93

Source, Part II: http://bit.ly/iBgnIA
##Node.js on windows
Bert Belder

http://2bs.nl/nodecamp.pdf

  
## 094607.md

      
              1 file
            
          
              1 fork
            
          
              1 comment
            
          
              2 stars
            
          
                hjsix2
                / 094607.md
            
            
              Last active
              June 23, 2017 01:06
                — forked from marocchino/094607.md
            
              
                ES6시대의 JavaScript
              
          
    ES6시대의 JavaScript


원문 : http://techlife.cookpad.com/entry/2015/02/02/094607

안녕하세요. 사원사업부의 마루야마@h13i32maru입니다.
최근의 Web 프론트엔드의 변화는 매우 격렬해서, 조금 눈을 땐 사이에 점점 새로운 것이 나오고 있더라구요. 그런 격렬한 변화중 하나가 ES6이라는 차세대 JavaScript의 사양입니다. 이 ES6는 현재 재정중으로 집필시점에서는 Draft Rev31이 공개되어있습니다.

JavaScript는 ECMAScript(ECMA262)라는 사양을 기반으로 구현되어있습니다.
현재 모던한 Web 브라우저는 ECMAScript 5.1th Edition을 기반으로 한 JavaScript실행 엔진을 탑재하고 있습니다.
그리고 다음 버전인 ECMAScript 6th Edition이 현재 재정중으로, 약칭으로 ES6이라는 명칭이 사용되고 있습니다.


## ring_middleware_order.clj
(defn handler
  [handler]
  (println "HANDLER"))

(defn wrap-1
  [handler]
  (fn [request]
    (println "pre-1")
    (handler request)
    (println "post-1")))

## leveldb-info.md

      
              1 file
            
          
              2 forks
            
          
              12 comments
            
          
              8 stars
            
          
                cbess
                / leveldb-info.md
            
            
              Last active
              April 26, 2019 01:59
            
              
                Google LevelDB research
              
          
    LevelDB is Google's embedded key/value store that uses similar design concepts as the BigTable Tablet
Code


https://github.com/nulayer/NULevelDB/blob/master/Classes/NULDBUtilities.mm
https://github.com/hoisie/LevelDB-ObjC/blob/master/Classes/LevelDB.mm
https://github.com/preble/APLevelDB/blob/master/APLevelDB/APLevelDB.mm

Projects


## building node-webkit on armv7 hardfp
sudo apt-get install libatk1.0-0 libc6 libasound2 libcairo2 libcups2 libexpat1 libfontconfig1 libfreetype6 libglib2.0-0 libgnome-keyring0 libgtk2.0-0 libpam0g libpango1.0-0 libpci3 libpcre3 libpixman-1-0 libpng12-0 libspeechd2 libstdc++6 libsqlite3-0 libx11-6 libxau6 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxi6 libxinerama1 libxrandr2 libxrender1 libxtst6 zlib1g apache2.2-bin bison curl elfutils fakeroot flex g++ gperf libapache2-mod-php5 libasound2-dev libbz2-dev libcairo2-dev libcups2-dev libcurl4-gnutls-dev libelf-dev libgconf2-dev libgl1-mesa-dev libglib2.0-dev libglu1-mesa-dev libgnome-keyring-dev libgtk2.0-dev libkrb5-dev libnspr4-dev libnss3-dev libpam0g-dev libpci-dev libpulse-dev libsctp-dev libspeechd-dev libsqlite3-dev libssl-dev libudev-dev libwww-perl libxslt1-dev libxss-dev libxt-dev libxtst-dev mesa-common-dev metacity patch perl php5-cgi pkg-config python python-cherrypy3 python-dev python-psutil rpm ruby subversion ttf-dejavu-core ttf-indic-fonts ttf-koc

## couchperuser.md

      
              1 file
            
          
              1 fork
            
          
              10 comments
            
          
              13 stars
            
          
                nolanlawson
                / couchperuser.md
            
            
              Last active
              March 13, 2021 21:08
            
              
                Solving "one database per user" in CouchDB/IrisCouch/Cloudant
              
          
    Background

Security in a single CouchDB can only be set up to do either:

Everyone can read/write everything (admin party)
Everyone can read, some can write
Some can read everything, and those same people can write everything

So in the very common situation where you want user data to be private, the current best practice is to give every user a database.  This sounds nuts at first, but it turns out that databases are cheap in CouchDB; Cloudant boasts that 100k databases in a single Couch is not uncommon (source).

  
## flux.js
/**
 * Basic proof of concept.
 * - Hot reloadable
 * - Stateless stores
 * - Stores and action creators interoperable with Redux.
 */

import React, { Component } from 'react';

export default function dispatch(store, atom, action) {

## why-i'm-leaving-kubernetes-for-swarm.md

      
              1 file
            
          
              6 forks
            
          
              23 comments
            
          
              104 stars
            
          
                jonathan-kosgei
                / why-i'm-leaving-kubernetes-for-swarm.md
            
            
              Last active
              January 16, 2022 00:10
            
          
    I have been an aggressive Kubernetes evangelist over the last few years. It has been the hammer with which I have approached almost all my deployments, and the one tool I have mentioned (shoved down clients throats) in almost all my foremost communications with clients, and it was my go to choice when I was mocking my first startup (saharacluster.com).
A few weeks ago Docker 1.13 was released and I was tasked with replicating a client's Kubernetes deployment on Swarm, more specifically testing running compose on Swarm.
And it was a dream!
All our apps were already dockerised and all I had to do was make a few modificatons to an existing compose file that I had used for testing before prior said deployment on Kubernetes.
And, with the ease with which I was able to expose our endpoints, manage volumes, handle networking, deploy and tear down the setup. I in all honesty see no reason to not use Swarm. No mission-critical feature, or incredibly convenient really nice to have feature in Kubernetes that I'm go

  
## .editorconfig
# Add plugin for your editors
# see: http://editorconfig.org

root = true

[*]
end_of_line = lf
charset = utf-8
tab_width = 8

## account_dreamcode.js
// sign up
account.signUp('joe@example.com', 'secret');

// sign in
account.signIn('joe@example.com', 'secret');

// sign in via oauth
account.signInWith('twitter');

// sign out
	(defn handler
	[handler]
	(println "HANDLER"))

	(defn wrap-1
	[handler]
	(fn [request]
	(println "pre-1")
	(handler request)
	(println "post-1")))
	/**
	* Basic proof of concept.
	* - Hot reloadable
	* - Stateless stores
	* - Stores and action creators interoperable with Redux.
	*/

	import React, { Component } from 'react';

	export default function dispatch(store, atom, action) {
	# Add plugin for your editors
	# see: http://editorconfig.org

	root = true

	[*]
	end_of_line = lf
	charset = utf-8
	tab_width = 8
	// sign up
	account.signUp('joe@example.com', 'secret');

	// sign in
	account.signIn('joe@example.com', 'secret');

	// sign in via oauth
	account.signInWith('twitter');

	// sign out