4 ms·

> Writing a WPF app in F# is a real pain (no partial classes, no nice MVVM framework support like Caliburn.Micro). C# is way better there. You shouldn't be wri

by Touche 12y ago

> Writing a WPF app in F# is a real pain (no partial classes, no nice MVVM framework support like Caliburn.Micro). C# is way better there. You shouldn't be writing WPF apps at all.

sandyarmstrong 12y ago
> You shouldn't be writing WPF apps at all. Says who? Are we supposed to stop writing Windows desktop apps in C# just because the frameworks are in maintenance mode?
- Touche 12y ago
  Yes. Write web apps instead.
  - CmonDev 12y ago
    All of the web's legacy languages are lame and not going anywhere - HTML, CSS, JS. At least WPF gives you some choice - C#, F#, VB. All without crap-trans-piling. The REST is not bad though.
    - Touche 12y ago
      Perhaps true, but the web hasn't been deprecated so... And you can use F#! http://funscript.info/ http://funscript.info/
      - CmonDev 12y ago
        > And you can use F#! http://funscript.info/ http://funscript.info/ As mentioned, not a big fan of transpiling.
seanmcdirmid 12y ago
There is no replacement for WPF on desktop. I'm pretty sure at this point that WPF is still more popular than WinRT.
- CmonDev 12y ago
  HTML5 sucks really hard after XAML :(.
  - seanmcdirmid 12y ago
    I don't use XAML in my WPF code.