Hi Andrew, Can you give me a scenario where a writable computed observable would be required? As the KO site states, these are very uncommon, mainly because the computed nature of the observable makes them unnecessary. If you need an update, set one or more of the dependent observables, and the computer observable also reflects the change.
There are issues with null values not correctly binding without using a custom binder. See demo project here: http://www.kendoui.com/code-library/mvc/grid/binding-nullable-field-to-dropdownlist-editor-in-grid.aspx Forum post here: http://www.kendoui.com/forums/mvc/grid/nullable-property-in-grid-doesn't-update-(when-bound-to-combobox).aspx
ObservableArray currently implements some of the ES-5 Array functions, including: indexOf(), forEach(), map(), filter(), find(), every(), some() Like the other Array functions, ObservableArray should use the native implementations of these functions if the browser implements them (IE9+, Firefox, Webkit, etc.).
Currently radio buttons can only bind to a string. They need to bind to a boolean value so we can have clean models, otherwise we have to put in ugly functions to convert the string to a boolean within the model.
Knockout has a 2-way hasFocus binding: http://knockoutjs.com/documentation/hasfocus-binding.html Currently, setting input focus requires page-level (non mvvm) event binding. Having this binding or similar would allow for cleaner form code.