A nasty side effect of using a terse language for apps that are split between a nice, algorithmic core and verbose, overly generic library calls for UI and stor

A nasty side effect of using a terse language for apps that are split between a nice, algorithmic core and verbose, overly generic library calls for UI and storage, is that the algorithmic part shrinks to an almost nonexistent fraction of total code volume, and only the ugly parts remain visible. I hope MS's productization of F# includes partial classes with type inference across (loaded) files, so that F# become as code gen friendly as C# and VB is. And that they add F# as an output language for their code generators. That way one will only have to deal with a graphical representation of the ugly parts most of the time.