Monday, 15 July 2013

Notes from Build 2013 HTML5 vs XAML, Neural Networks and security

I met some people that where very pro
HTML5 seeing this as the future. I met some people that where very pro XAML and
see this as the future. After the silent demise of Silverlight it’s a bit
difficult to know where the future is.

On the HTML5 front I intend to catch up
on subjects such as Bootstrap (MVC5), TypeScript, Reactive Binding (MDV ECMA),
ShadowOn, Angular, Bower, Command.js, Node/Grat, Handlebars.js...

I heard a rumor that out of 10 projects
MS started in HTML5 7 have been rewritten in XAML. The pragmatic approach of
hybrid solutions is the way to go. Use HTML5 when it makes sense but be aware
there is a cost associated with its use. WPF is a more elegant solution because
it uses OO and properly separates concerns. But when you need customer reach
then HTML5 is the way to go but be careful that the target customers have
browsers capable of handling html5,

A friend of mine will be working
together with xamarin to provide a VS template with MVVM Light for ios native
apps with portable c# libraries

Tabular information where you have some
inputs (independent variables) to produce an output (the thing you want to
predict). The idea is that you have some training data that is used to fit
internal variables of the neural network after which you have a system that can
predict an output from a given set of inputs

What exactly is a neural network

The inputs are normalized, Boolean
variables are converted to -1 and +1, enumerations to a set of individual
inputs that are set to 0 or 1. There are then used in the input nodes of the
neural network. Then a to be determined number of hidden nodes evaluate a
function based on all these inputs to produce a set of output nodes.