Explore >> Select a destination
|
You are here 
|
frantic.im | ||
| | | | |
blog.davemartin.me
|
|
| | | | | A critique of modern React, specifically the hooks API, and an explanation of why it's insufficient as a web development framework | |
| | | | |
www.valentinog.com
|
|
| | | | | Learn how to test React components with react-test-renderer, and the Act API. | |
| | | | |
reactkungfu.com
|
|
| | | | | Photo available thanks to the courtesy of seeminglee. CC BY-SA 2.0 There are three different ways to define your React components. With v0.13 version of React, the dev team took a great effort to enable using pure JavaScript classes available in the new ECMAScript 2015 standard. Using such classes allow you to write more idiomatic JavaScript. It also introduces less magic than the old React.createClass syntax. Each of these approaches have the slight differences and consequences when using them. In this blogpost I want to show you examples of component classes written using React.createClass, pure ECMAScript 2015 classes and ECMAScript 2015 classes with the experimental class properties feature. This will allow you to choose wisely between those three depending on your project needs. | |
| | | | |
coronax.wordpress.com
|
|
| | | Before I move on from the C64 user port for a while, I wanted to do a project where the computer actually read a value from the environment and analyzed it. Also, I wanted to spend a little effort fixing up my kludgy SPI implementation, and give it a better workout by reading several inputs... | ||
