Julien Viala mr-wildcard

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

Learning FP the hard way: Experiences on the Elm language

by Ossi Hanhinen, @ohanhi

with the support of Futurice 💚.

Licensed under CC BY 4.0.

Editorial note

This is an auth example (WIP)

react + redux + RR

It uses https://gist.github.com/iNikNik/3c1b870f63dc0de67c38 for stores and actions.

1) create redux

const redux = createRedux(state);

2) get requireAccess func => bindCheckAuth to redux

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

Common JS support
NPM support
a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

"Everything is an expression"... since ES1?

Many languages support "expression-only" semantics, allowing to use any construct in an expression position.

NOTE: the difference between expressions and statements is that the former produce a value, while the later don't.

For example, Ruby's if-expression:

x = 10

	export function retrieve(nodeId) {
	return { type: 'RETRIEVE_NODE', payload: { nodeId: nodeId } }
	}

	export function show(nodes) {
	return { type: 'SHOW_NODE', payload: { nodes: nodes } }
	}

	import React, { Component, PropTypes } from 'react';
	import { reduxForm, Field } from 'redux-form';

	export class CreateUser extends Component {

	static propTypes = {
	createUser: PropTypes.func.isRequired,
	initialValues: PropTypes.object,
	submitting: PropTypes.bool.isRequired,
	invalid: PropTypes.bool.isRequired,

	## package.json changes

	"webpack": "^2.1.0-beta.20",
	"typescript": "^2.0.0",
	"webpack-dev-server": "^2.1.0-beta.0",
	"webpack-hot-middleware": "^2.12.2",

	"webpack-split-by-path": "^0.1.0-beta.1", <-- struggles, I've removed it
	https://github.com/BohdanTkachenko/webpack-split-by-path/pull/22#issuecomment-240050461

	import React, { PropTypes } from 'react';

	const SegmentedControl = ({ input, disabled, heading, required, className, items, name, meta: { touched, error } }) => (
	<fieldset className={`form__field ${className \|\| ''}`}>

	<legend className="form__label">
	{heading}{required ? (<span>*</span>) : null}
	{ (touched && error) ? (
	<span className="form__error"> {error}</span>
	) : null }

	1. Build GraphQL server using `express-graphql` package.
	2. Configure `schema.js` file.
	3. Query for data.