jordow

Hi, I'm Jordan a member of the React core team.

React is only 32kb(gzipped) in the production build (which also has performance optimizations that the development build does not).

We've also found that React helps make the rest of your application code much smaller, which may end up being even more important - but 32kb is certainly reasonable. We're extremely conscientious of page load speed and performance at Facebook which is why we place so much emphasis on React performance - second only to correctness and proper abstraction.

It's not just the advanced features. Even basic features are completely broken. Pressing undo several times can occasionally break out of undoing and start editing your document on your behalf - spewing a slew of "uuuuuu" into your document, which - guess what - ruins any hope you have of reverting back to the original document state.

https://github.com/jordow/FaxJs Completely unidirectional reactive "MVC" framework on github.

(It seems there's an overwhelming consensus forming around issues like this - which FaxJs addresses at the core.)

I have a similar toolkit that uses pure javascript.

https://github.com/jordow/FaxJs

(see reactive example)

Functional reactive programming makes ui development so much easier. I've seen a lot of people starting to think this way about ui systems (with good reason). Good work!

I'd like to add similar compiled-in reactive optimizations to FaxJs as I'm sure Elm does. I commend you on choosing a static type inference system.

Rendering arbitrarily on either the client or server is hard. Other solutions that I saw forced the developer to have to think about it, so I developed FaxJs which allows the system to handle that complexity for you.

https://github.com/jordow/FaxJs

The gist is that you just write standard declarative ui structures in pure javascript and the system disassembles the markup on the server, and reassembles it on the client with all the events still in tact. You wouldn't know all that is happening just by looking, though.

    ...
    var twoDivs = {
      className: 'outerDiv',
      onClick: this.outerDivClicked,
      innerDiv: {
        className: 'innerDiv',
        content: 'inner-most-div!'
      }.Div()
    }.Div();

I've built a toolkit that does this very thing (rendering the user interface on either client or node.js arbitrarily) https://github.com/jordow/FaxJs/

    From the video: "There are a number of existing frameworks for javascript today, but there are none like Mojito that try to blur and succeed at blurring the the server client boundary."

I'm guessing Mojito has a ton of functionality surrounding ajax/queries and business logic modules etc. FaxJs is a work in progress, but it has a couple of novel concepts besides server side rendering: In FaxJs, your view is simply a function of your model, or a "projection". That function acts as an invariant that the system upholds at all times without introducing any other concepts/abstractions. Sometimes, a function is enough.

I was originally from Seattle where I was an engineer at Amazon for a couple years before moving to the bay area. Seattle is an incredibly livable place. If you feel yourself getting bothered by the rain, just remind yourself that the rain cleans out the air and produces the greenest, freshest natural beauty that you can find on the West coast. Hands down - better summer climate than anywhere. If you're doing a startup, do you really leave your computer anyways? Just save it for when the weather's nice. I don't know why Seattle doesn't have as large of a startup scene. It's got a huge tech scene, no doubt, and it has every ingredient in the mix to foster a large startup community (smarts, companies, UW, coffee, good beer). Most of all, it seems more business friendly. In particular - the economic climate seems more startup friendly. You could get a really decent place to rent for 800 dollars a month. The transportation has gotten much better with the underground train/bus tunnel. About seven days a week there's almost always a killer happy hour where you could eat gourmet food for under ten dollars - much better than the food I've had in the Bay Area. Also, there's no state income tax. If you're looking to buy a house, I believe that all things considered, your house purchase dollars go five times further in the Seattle area. - And you're just an hour and a half flight away from the South Bay. It seems you could live there and be very frugal, and spend your credit card miles commuting to the bay area once every other week - and still come out ahead. I haven't been back there in a year, but I hear the startup community is getting even stronger. I hope it does well as a startup hub.