Daniel Walker plaxdan

This is a response to Bill Fisher regarding experience with Flux:

@abdullin Also, can you clarify what you mean by "solution structure"? I am thinking about revising the examples soon.

Currently all flux samples (that I've seen) group files into folders based on technical similarity. For example, stores go with stores, action creators reside in the same folder shared with the other action creators.

This pattern works quite well for smaller projects. It feels especially good for the sample projects of various MVC frameworks, when you have just a bunch of controllers, models and views.

However, as we discovered on some production projects, such approach doesn't scale well. At some point you end up with dozens of technically similar files per folder and logically messy solution.

Towards Discussion Guidelines

I personally like to have discussions in the spirit of the Socratic method. Instead of declaring my opinion, I ask a relevant question. How about this situation? What about this case? This has two possible outcomes.

The other person explains to me how things work in that case. I realize that I misunderstood, and we both come out enriched and in agreement.
The other person realizes that those situations are not covered. They realize they misunderstood, and we both come out enriched and in agreement.

In both cases, it could have been a conflict, egos crashing together. But by asking questions, it becomes a collaboration to find the best answer. Even the simple act of asking a question in the first place says, "I care what you have to say, we can agree on this." That said, I have noticed that it is definitely still possible for things to go wrong within this framework. How can this happen?

There was a passage from [The

Angular: Just say no

A collection of articles by AngularJS veterans, sometimes even core committers, that explain in detail what's wrong with Angular 1.x, how Angular 2 isn't the future, and why you should avoid the entire thing at all costs unless you want to spend the next few years in hell.

Reason for this: I'm getting tired of having to explain to everyone, chief of which all the indiscriminate Google Kool-Aid™ drinkers, why I have never believed in Angular, why I think it'll publicly fail pretty soon now (a couple years), and why it's a dead end IMO. This gist serves as a quick target I can point people to in order not to have to parrot / compile the core of the articles below everytime. Their compounded reading pretty much captures 99% of my view on the topic.

This page is accessible through http://bit.ly/angular-just-say-no and http://bit.ly/angularjustsayno, btw.

I won't be using Angular for my next project...and neither should you. • Robe

Star this gist to see the talk at ReactiveConf 2016.
Retweet to spread the word.
Have a look at this blog post to see other proposals.
Try elm-search to see what this is all about.

An API search engine in Elm for Elm

Elm is a statically typed functional language that compiles to JavaScript. It's well-known for its developer experience: the compiler provides nice error messages, the package system enforces semantic versioning for all published packages and makes sure every exposed value or type has some documentation and type annotations.

	# http://rspec.info/
	# http://peepcode.com/products/rspec-user-stories
	# http://dannorth.net/whats-in-a-story
	# http://www.lukeredpath.co.uk/2006/8/29/developing-a-rails-model-using-bdd-and-rspec-part-1
	# http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/
	# http://www.benmabey.com/2008/02/04/rspec-plain-text-stories-webrat-chunky-bacon/
	# http://www.chariotsolutions.com/slides/pdfs/ete2008-IntegrationTestingWithRSpec.pdf
	# http://www.joesniff.co.uk/ruby/telling-a-good-story-rspec-stories-from-the-trenches.html

	# How does using stories help testing?

	/*
	* L.TileLayer is used for standard xyz-numbered tile layers.
	*/
	L.Google = L.Class.extend({
	includes: L.Mixin.Events,

	options: {
	minZoom: 0,
	maxZoom: 18,
	tileSize: 256,

	#!/usr/bin/env bash

	uninstall() {
	list=`gem list --no-versions`
	for gem in $list; do
	gem uninstall $gem -aIx
	done
	gem list
	gem install bundler
	}

	(function (window) {

	// This library re-implements setTimeout, setInterval, clearTimeout, clearInterval for iOS6.
	// iOS6 suffers from a bug that kills timers that are created while a page is scrolling.
	// This library fixes that problem by recreating timers after scrolling finishes (with interval correction).
	// This code is released in the public domain. Do with it what you want, without limitations. I do not promise
	// that it works, or that I will provide support (don't sue me).
	// Author: [email protected]

	var timeouts = {};

	# Detects if a .nvmrc file exists, and switches
	# to the specified version if it does.
	# The contents of the .nvmrc file should simply be the node
	# version to use, like "v0.8.11"
	# Put this in your .zshrc file or somewhere else that is loaded automatically
	function chpwd() {
	emulate -L zsh
	if [[ -f .nvmrc ]] then
	nvm use `cat .nvmrc`
	fi