React v0.13.0 Beta 1

Post by danabramov » Wed, Jan 28, 2015, 1:38 PM UTC

    function MyComponent(initialProps) {
      return {
        state: { value: initialProps.initialValue },
        render: function() {
          return 
        }
      };
    }

Post by kuni-toko-tachi » Wed, Jan 28, 2015, 1:41 PM UTC

amelius wrote: post #15

I'm actually looking for a system that allows me to write Javascript code in the normal imperative way, and automatically makes it reactive. So, for example, calling a function f(a, b) is first done normally, and then, when e.g. "b" changes value, the function f(a, b) is re-evaluated incrementally. Note that this means that not simply f is invoked again, but that f is recursively re-evaluated. Anybody here aware of s…

Post by andrewingram » Wed, Jan 28, 2015, 1:55 PM UTC

bambax wrote: post #41

andrewingram wrote: post #36

Earlier quoted context omitted.

1.0 implies API stability, so now is exactly the time they should be prioritising things that potentially change the API going forwards. Also, is 40kb gzipped really something to lose sleep over? Especially when the mere act of moving from old jQuery/Backbone soup to React reduces the size of my real code by a far greater amount.

I don't know React, and use and love Backbone. It's my (perhaps flawed) understanding that React deals only with the "view" part of an app, and that you can use Backbone and React concurrently. Could you elaborate on what you call "Backbone soup" and how React helps solve this problem?

Post by amelius » Wed, Jan 28, 2015, 1:59 PM UTC

seanmcdirmid wrote: post #38

amelius wrote: post #29

Earlier quoted context omitted.

In my opinion, the current way of doing things with reactive mechanisms really doesn't make it clear what the program is doing. There's lots of things happening at the same time, and also glitches can occur (variables rapidly changing after eachother), and also non-optimal efficiency (things being recomputed unnecessarily). If my program just gets re-evaluated in an optimal way (without any other side-effects) then t…

SAC is quite different from reactive programming in the sense that it is not, well, reactive or interactive. SAC deals with incremental recomputation on change, whereas most reactive programming systems out their don't support incremental recomputation (maybe some DOM diffing and that's about it). Check out Adapton though, which is trying to bridge the gap.

Post by eyko » Wed, Jan 28, 2015, 2:29 PM UTC

rpwverheij wrote: post #28

colin_jack wrote: post #10

Earlier quoted context omitted.

Maybe off topic but I've been wondering whether many people are finding spending time on TS worthwhile? Given the improvements in ES6, the fact that the JS community in general is so active, and the fact that I've seen some truly awful TS code (mainly where the devs want to pretend the web doesn't exist) I've been put off exploring TS too far much (beyond looking at the basic language features). I'm not sure if I sho…

After quite some consideration I chose to convert my ActionScript3 project to TypeScript. I knew I had to move away from flash for a while, and personally I really prefer to code big framework-like projects with static typing, so I gave it a go and it I have to say it has been really enjoyable. My code looks really neat, and unlike many other comments here, my code is very much targeted at the web and bound to how js…