Anton Tayanovskyy's blog articles

0
comment
on 7/25/2014 7:31 AM
UI.Next is available for experimentation as a public WebSharper.UI.Next NuGet package. You can build examples from source - just get WebSharper first. UI.Next addresses most shortcomings we felt WebSharper had for single-page JavaScript applications. The most interesting part is a dataflow model integrated with DOM for defining reactive UI, but we also provide support for client-side routing and animation. If you play with it, Simon and I will be very interested in your feedback.  Next week we plan to do[...]
>> Read the full article
.
0
comment
on 7/22/2014 2:46 PM
For about a year or so, I have made Functional Reactive Programming (FRP) taboo. I cringed at every mention of it. I think this was a mental self-defense reaction, my extended immune system was sending me a signal that I spent too much time thinking about this subject without any tangible results. The fatal attraction of FRP is its simplicity. Semantics are beautiful and clear. There are Behaviors, functions of time, Events, timed occurrences, and they all dance together. You write causal transformations[...]
>> Read the full article
.
1
comment
on 7/21/2014 12:36 PM
Learning from and going beyond D3.js to make animation scheduling declarative, in the context of WebSharper UI.Next..
>> Read the full article
.
0
comment
on 6/5/2014 8:19 AM
WebSharper is getting support for Mono, MonoDevelop, Xamarin Studio, CloudSharper on Linux and Mac OS X, improved bindings to D3.js and Leaflet.js. On performance side, we are experimenting with ASM.js for numeric code. For this summer, there are plans for better single-page application support and a functional version of data binding, to incorporate and improve on ideas in Angular JS and Facebook React.
>> Read the full article
.
0
comment
on 5/14/2014 6:02 PM
This is a brain dump from a Twitter/IRC discussion with @panesofglass and @bryanedds. So there is this brand-new thing called Facebook React and hype wave about Virtual DOM. I only skimmed this library, but here are some reasons why I remain sceptical: Identity! Typical DOM trees are a lot more than the markup. They are full of pieces of state that are *opaque* - abstract types, and *mutable*. This is especially true if you use 3rd-party libraries, but even with vanilla DOM, input tag, once rendered, int[...]
>> Read the full article
.
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us
Built with WebSharper