4 ms·
Luckily this doesn't appear to compete with React. This seems to be focused on composing a large-scale application from many different component applications. I
by curun1r 12y ago
Luckily this doesn't appear to compete with React. This seems to be focused on composing a large-scale application from many different component applications. It's the kind of thing you have to do at large companies that have many different groups and are bad at communicating and collaborating on a single code base. React helps you simplify your view logic. The two should work together quite nicely.
Just yesterday we had a meeting with the team at my company that's responsible for building the glue to allow our flagship product (~$4b profit per year) to be composed by independent releases created by independent teams that aren't always communicating on a regular basis. They built a library based on the whitepaper that was published by the main developer behind T3. At the time they started, there was nothing publicly available that served the need. But now, a company following in our footsteps will have T3 and won't have to waste the time that we did building it.
- Noobies 12y agoYeah, doesn't compete with React. If React were being used client side only (not isomorphic) then one can roughly do stuff like https://gist.github.com/priyajeet/c2731789d3a688ee85a9 https://gist.github.com/priyajeet/c2731789d3a688ee85a9 (5-min hack)
- mparr4 12y agoCurious, what's the whitepaper?