#opendaylight-spectrometer: spectrometer meeting
Meeting started by anipbu at 16:03:34 UTC
(full logs).
Meeting summary
-
- https://trello.com/b/fIVlZ0M5/opendaylight-spectrometer
<- trello board (anipbu,
16:04:00)
- agenda bashing (anipbu, 16:05:18)
- react presentation (anipbu,
16:06:37)
- trello board (anipbu,
16:06:44)
- react presentation (anipbu, 16:06:54)
- https://docs.google.com/presentation/d/15WQU9Zmdu8kKXKZpEnE2q7qj3eM6fYtJ7MUCH6PcB6E/edit#slide=id.p
(vasya10,
16:10:32)
- https://docs.google.com/presentation/d/15WQU9Zmdu8kKXKZpEnE2q7qj3eM6fYtJ7MUCH6PcB6E/edit#slide=id.p
(anipbu,
16:10:43)
- react is component based framework (anipbu,
16:13:05)
- react has simpler components to use
(anipbu,
16:13:38)
- AngularJS 1 and 2 are vastly different from
each other (zxiiro,
16:14:42)
- angular 2 is different beast from angular 1.
Using angular 2 requires you to rewrite application. (anipbu,
16:14:46)
- angular 2 is just in beta (anipbu,
16:15:28)
- react is widely used including instagram,
facebook (anipbu,
16:16:40)
- netflix using react (anipbu,
16:19:59)
- react assumes you have to repaint the whole
DOM (anipbu,
16:21:22)
- changing the DOM causes biggest performance
hit, not repainting (anipbu,
16:22:39)
- react uses virtual DOM (anipbu,
16:23:19)
- angular has too many pieces: factory, services,
etc (anipbu,
16:25:30)
- react has simpler components: only has
properties and states (anipbu,
16:26:03)
- react properties are passed just like any
attributes. states is the current display state. anytime the state
changes, react will rerender the whole thing by doing a diff with
the virtual DOM (anipbu,
16:27:15)
- http://pastebin.com/ (anipbu,
16:28:15)
- http://pastebin.com/sRHPF8Gi
(vasya10,
16:28:56)
- http://pastebin.com/sRHPF8Gi
<== sample code (anipbu,
16:29:19)
- State changes automatically fire
render() (anipbu,
16:31:18)
- react gives hook to jquery (anipbu,
16:32:20)
- react can work with d3 (anipbu,
16:33:37)
- if your library is a view layer, you can still
use react in pieces (anipbu,
16:35:06)
- react promotes “Stateless” (dumb) and
“Stateful” (smart) components (anipbu,
16:37:10)
- flux is a pattern. it suggests one way data
flow (anipbu,
16:39:28)
- Action -> Dispatcher -> Store -> View
-> Action -> Dispatcher (anipbu,
16:39:37)
- yahoo uses react as well (anipbu,
16:41:59)
- redux: Store is a combination of Immutable
objects and functional reducers (anipbu,
16:42:30)
- https://egghead.io/series/getting-started-with-redux
(vasya10,
16:47:19)
- https://egghead.io/series/getting-started-with-redux
<== video tutorial (anipbu,
16:47:36)
- react: easy to write unit tests (anipbu,
16:48:12)
- Mocha, Jasmine, Karma play very well with
React (anipbu,
16:49:16)
- Fully supports the next generation JavaScript –
ES6 and ES7 via the compiler Babel, which also polyfills to older
browser versions (anipbu,
16:50:57)
- React supports isomorphic (aka Universal)
Javascript, where same code can run on both client and server
(anipbu,
16:52:49)
- https://react.rocks/ (vasya10,
16:53:26)
- https://react.rocks/ <==
react based d3 (anipbu,
16:53:58)
- vasu says: by using nodejs ui can evolve
sepreately from backend side (anipbu,
16:57:28)
- nodejs (anipbu, 17:00:04)
- you can still use nodejs for development
(anipbu,
17:00:20)
- if not using nodejs, it going to be more
confusing, because the packages are already in npm (anipbu,
17:01:02)
- if not using nodejs, we no longer have
isomorphic javascript (anipbu,
17:05:30)
- downside of not using node.js in production is
loosing isomorphic capability (mohzah,
17:05:30)
- architecture (anipbu, 17:07:18)
- we have consensus to move forward and use
reactjs for UI client side code (anipbu,
17:08:03)
- cookies (anipbu, 17:09:14)
Meeting ended at 17:09:21 UTC
(full logs).
Action items
- (none)
People present (lines said)
- anipbu (55)
- vasya10 (11)
- odl_meetbot (7)
- zxiiro (3)
- mohzah (1)
- tnadeau (0)
Generated by MeetBot 0.1.4.