mikaelbr

4 ms·

1.
Abstracting the DOM by making ad-hoc React-like library(medium.com)
2 points by mikaelbr 7y ago|0 comments
2.
ES2015 (ES6) Features Commonly Used with Functional Style React(open.bekk.no)
1 points by mikaelbr 11y ago|0 comments
3.
Scaling Front End Build Steps by Necessity(open.bekk.no)
3 points by mikaelbr 11y ago|0 comments
4.
by mikaelbr 11y ago
This topic is also covered in the talk from JSConf Budapest: "Functional UI and Unidirectional Dataflow": https://www.youtube.com/watch?v=JNMWi7Z0Ssg
5.
by mikaelbr 11y ago
Component here is just to illustrate that the type is of a view component, and due to it being implemented on top of React. `component()` is a factory/syntactic sugar on top of React allowing you to have referentially transparent compo
6.
by mikaelbr 11y ago
With Omniscient there is a syntactic sugar on top of React class factories, which encourages to think of components as pure and smaller/more focused functions. This tries to lead more to simpler and composable components.
7.
by mikaelbr 12y ago
Yeah. The main part here is using immutable structures from the top, having cursors to sub-components with information about only the relevant data for that component, and have a way of re-start the loop when a data has changed. Sometimes,
8.
by mikaelbr 12y ago
It doesn’t really relate to the Flux architecture directly. You could probably use something like Flux in addition to Omniscient. In the same way that Flux encourages a continuous loop with data from the top, Omniscient has a single directi
9.
Show HN: Omniscient: Abstracting React – fast top down render of immutable data(omniscientjs.github.io)
11 points by mikaelbr 12y ago|4 comments
10.
by mikaelbr 13y ago
After some feedback the example (the piano implementation) is updated to include black keys.