Paweł Pacana mostlyobvious

The issue:

..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.

(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)

touch-action CSS property can be used to disable this behaviour.

touch-action: manipulation The user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

React <-> D3 Resources

Thanks for all the stars.

Due to unexpected demand, I move this to a proper github repo, see here: https://github.com/chroth7/reactD3resources

I would very much like to get your PRs there, thank you!

This is my response to an email asking about Domain-Driven Design in golang project.

Thank you for getting in touch. Below you will find my thoughts on how golang works with DDD, changing it. This is merely a perception of how things worked out for us in a single project.

That project has a relatively well-known domain. My colleagues on this project are very knowledgeable, thoughtful and invested in quality design. The story spelled out below is a result of countless hours spent discussing and refining the approach.

Conclusions could be very different, if there was a different project, team or a story-teller.

	# Expectations:
	#
	# * application code in /srv/myapp/current
	# * ruby runtime in /srv/myapp/.rubies/ruby-2.3.0
	# * unicorn.rb config specifies pid file location to /srv/myapp/current/unicorn.pid and working directory to /srv/myapp/current

	[Unit]
	Description=Sample unicorn app

	[Service]

	1. Get lein
	lein - http://leiningen.org/

	2. `lein new reagent <awesome-project>`

	3. Some changes to project.clj from last night's talk:
	:dependencies [[org.clojure/clojure "1.7.0-alpha4"]
	[org.clojure/clojurescript "0.0-2371"]
	[org.clojure/core.async "0.1.346.0-17112a-alpha"]
	[reagent "0.4.3"]

	RUBY_GC_HEAP_FREE_SLOTS=600000
	RUBY_GC_HEAP_GROWTH_FACTOR=1.25
	RUBY_GC_HEAP_GROWTH_MAX_SLOTS=300000
	RUBY_GC_HEAP_INIT_SLOTS=600000
	RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.3
	RUBY_GC_MALLOC_LIMIT=64000000
	RUBY_GC_OLDMALLOC_LIMIT=64000000
	RUBY_HEAP_FREE_MIN=12500
	RUBY_HEAP_SLOTS_GROWTH_FACTOR=1
	RUBY_HEAP_SLOTS_INCREMENT=100000

	/**
	* VH and VW units can cause issues on iOS devices: http://caniuse.com/#feat=viewport-units
	*
	* To overcome this, create media queries that target the width, height, and orientation of iOS devices.
	* It isn't optimal, but there is really no other way to solve the problem. In this example, I am fixing
	* the height of element `.foo` —which is a full width and height cover image.
	*
	* iOS Resolution Quick Reference: http://www.iosres.com/
	*/

	Our file structure per single mini-application:
	app_starter.js.coffee
	--- app_directory
	--- app.module.js.coffee
	--- backend.module.js.coffee
	--- components
	--- component_file1.module.js.coffee
	...
	--- domain.module.js.coffee
	--- glue.module.js.coffee

	# backend app
	require 'sinatra/base'
	require 'json'
	class UsersController < Sinatra::Base
	get '/users/:id' do
	JSON.dump id: params[:id].to_i, name: "Josh"
	end
	end

Paweł Pacana mostlyobvious

Finding a Ruby memory leak using a time analysis

React <-> D3 Resources

Short story