3 ms·

I really enjoy Bret Victor's talks. Here is one where he discusses his driving principle: Creators need an immediate connection to what they create (e.g. immed

I really enjoy Bret Victor's talks. Here is one where he discusses his driving principle: Creators need an immediate connection to what they create (e.g. immediate feedback) http://worrydream.com/#!/InventingOnPrinciple http://worrydream.com/#!/InventingOnPrinciple

voltagex_ 11y ago
It's a pity the code isn't open but I'm sure there's a reason.
TheAceOfHearts 11y ago
Along these lines, this is why I love hot-loading code. For example, there's react-hot-loader [0] (which was actually superseded already by react-transform [1]). This enables you to iterate much more quickly while you're building an interface. Along that same line, the same guy created redux and redux-devtools [2], which also enables you to iterate quickly on application code. I've been using hotloading css, react and redux for the past few months and it's an amazing experience. It enables you to iterate quickly and see changes immediately. (Admittedly, as a project grows, there's a small delay between saving and seeing the change. I'm not sure if it's avoidable or not... But it's still much faster than having to do a full-page reload.) [0] https://gaearon.github.io/react-hot-loader/ https://gaearon.github.io/react-hot-loader/ [1] https://github.com/gaearon/react-transform-boilerplate https://github.com/gaearon/react-transform-boilerplate [2] https://github.com/gaearon/redux-devtools https://github.com/gaearon/redux-devtools
- akilism 11y ago
  If you like hot-loading code you should checkout this strangeloop video of Bruce Hauman talking about devcards https://www.youtube.com/watch?v=G7Z_g2fnEDg https://www.youtube.com/watch?v=G7Z_g2fnEDg
- pka 11y ago
  Check out Elm [1], it had hot-swapping and a time travelling debugger even before React. [1] http://www.elm-lang.org http://www.elm-lang.org
- dirtyaura 11y ago
  A small side track to the topic: I've been evaluating data querying, caching (or syncing) options for building modern JS apps. Public GraphQL solutons seem not to be practical enough for fast prototyping yet, but redux looks a promising middle-ground. Have you done production apps on it? Any downsides?
  - TheAceOfHearts 11y ago
    I'm currently in process of rewriting our work application from AngularJS to Redux. The downside with redux is that simpler things can take a bit more code than you might wish. You have to add an action handler / reducer, action creator, etc. However, it's generally very easy to extend previously written code, and it's very easy to reason about the data / logic flow. Another pitfall with redux is that it doesn't provide any help when you have to react to changes. A few days ago in reddit I wrote a small example explaining what I mean [0]. You might be interested in checking out relay-local-schema [1], it looks promising for experimenting with GraphQL and Relay. [0] https://www.reddit.com/r/javascript/comments/3u0167/getting_started_with_redux_a_free_30part_video/cxbg9s4 https://www.reddit.com/r/javascript/comments/3u0167/getting_... [1] https://github.com/relay-tools/relay-local-schema https://github.com/relay-tools/relay-local-schema

voltagex_ 11y ago

It's a pity the code isn't open but I'm sure there's a reason.

TheAceOfHearts 11y ago

Along these lines, this is why I love hot-loading code. For example, there's react-hot-loader [0] (which was actually superseded already by react-transform [1]). This enables you to iterate much more quickly while you're building an interface. Along that same line, the same guy created redux and redux-devtools [2], which also enables you to iterate quickly on application code. I've been using hotloading css, react and redux for the past few months and it's an amazing experience. It enables you to iterate quickly and see changes immediately. (Admittedly, as a project grows, there's a small delay between saving and seeing the change. I'm not sure if it's avoidable or not... But it's still much faster than having to do a full-page reload.) [0] https://gaearon.github.io/react-hot-loader/ https://gaearon.github.io/react-hot-loader/ [1] https://github.com/gaearon/react-transform-boilerplate https://github.com/gaearon/react-transform-boilerplate [2] https://github.com/gaearon/redux-devtools https://github.com/gaearon/redux-devtools

akilism 11y ago
If you like hot-loading code you should checkout this strangeloop video of Bruce Hauman talking about devcards https://www.youtube.com/watch?v=G7Z_g2fnEDg https://www.youtube.com/watch?v=G7Z_g2fnEDg
pka 11y ago
Check out Elm [1], it had hot-swapping and a time travelling debugger even before React. [1] http://www.elm-lang.org http://www.elm-lang.org
dirtyaura 11y ago
A small side track to the topic: I've been evaluating data querying, caching (or syncing) options for building modern JS apps. Public GraphQL solutons seem not to be practical enough for fast prototyping yet, but redux looks a promising middle-ground. Have you done production apps on it? Any downsides?
- TheAceOfHearts 11y ago
  I'm currently in process of rewriting our work application from AngularJS to Redux. The downside with redux is that simpler things can take a bit more code than you might wish. You have to add an action handler / reducer, action creator, etc. However, it's generally very easy to extend previously written code, and it's very easy to reason about the data / logic flow. Another pitfall with redux is that it doesn't provide any help when you have to react to changes. A few days ago in reddit I wrote a small example explaining what I mean [0]. You might be interested in checking out relay-local-schema [1], it looks promising for experimenting with GraphQL and Relay. [0] https://www.reddit.com/r/javascript/comments/3u0167/getting_started_with_redux_a_free_30part_video/cxbg9s4 https://www.reddit.com/r/javascript/comments/3u0167/getting_... [1] https://github.com/relay-tools/relay-local-schema https://github.com/relay-tools/relay-local-schema