Digests » 73


These 4 Tutorials Create a New Language in Less Than 200 Lines of Code

Have you ever wanted to design your own programming language? It seems like such fun, but if you’ve ever tried you probably got stuck right around the time you read “LLR Decent Parsers and Abstract Syntax Trees.” Traditionally designing your own language was hard because it requires a very specialized set of arcane tools, tools that take a long time to learn and use effectively. But it doesn’t have to be this way. Ohm, a new compact parser toolkit from the team at HARC, lets you build your own languages with simple and clean Javascript.


Testing React components with Jest and Enzyme

Some people say that testing React components is useless and in many cases it is, but there are a few cases when I think it’s useful.

What were the biggest 'aha' moments you had while learning react?

I'm currently in the process of getting the hang of reactjs and one of the biggest 'aha' moments is the fact that 'this' refers to the object(simple i know) and using bind() allows you to access certain objects from within methods in classes. Anyways I figured it'd be a helpful part of the learning process if people on here were to post their 'aha' moments.

React.js Tutorial Pt 1: A Comprehensive Guide to Building Apps with React.js

By now you’ve probably heard about facebook’s React. You’ve probably even heard really good things. There has never been a better time to take the leap and start learning React. The difficulty starting out with React isn’t React itself. It’s important to remember React is “just the V in MVC” or “just the view layer”. Comparing React to Angular or React to Ember is unfair because React isn’t trying to be a full fledged framework. It’s just trying to be the view layer, which it’s really good at. This brings up issues for developers who are trying to learn React. React isn’t difficult to learn; putting all of the pieces together to build a full web application in React is.


An ecosystem of composable React components for building interactive data visualizations.

Redux at Knewton

About two years ago it became apparent that our frontend architecture was showing its limits. We dreaded adding new features because of side-effect bugs. Changing a dropdown could break unrelated parts of the UI. These issues occurred mostly because of the way we managed our application state, or actually didn’t: the DOM was the state.