News for hackers. Stuff that matters.

LukeW

maps might be a higher priority.
I don't know much about any of the Java web frameworks-- my only experience with a web framework on a statically typed platform is with ASP.NET MVC. ASP.NET MVC makes heavy use of reflection, and runtime errors are common -- something that's also true of the common ORMs for .NET. So even though you're on a statically-typed platform, you sometimes aren't getting the classical 'perks' of static-typing, particularly the compile-time errors.

I've got a casual interest in Haskell and flipped through Learn You A Haskell's earlier chapters, but I can't scan snippets of fancy Meta-Haskell well, so some of the specifics here are probably lost on me. The text of the slides does seem to admit that the author is also kind of new to Yesod. (I've never met a Yesod expert...)

With all of that said, I think that part of the premise was that while Yesod's not a typical 'web platform for a static language', it's an interesting case study because it (apparently) tries harder to maintain compile-time benefits static typing everywhere. (I understand this is true of the persistence layer as well)

I agree that the content isn't what you'd expect given the title, but I get why the author's interested in Yesod and why it was chosen to represent the 'static' side.

Re:Stick with Microsoft WPF (et al.) or jump ship? on Wednesday February 01, 2012 @03:47PM (#3539842)
I don't think it's really about criticizing MS for putting out new stuff-- I think .NET developers are trying to read the tea leaves about the future of .NET in general and WPF specifically, to figure out which of the new stuff to use. WPF is still new to a lot of developers. A lot of .NET shops are slow to change.

My two .NET gigs have been enterprisey, line-of-business-type apps. What the whole Metro thing is going to mean for line of business apps is hard to say. WPF might continue to be the choice for things like that. I have a hard time picturing a Metro-style data entry screen, but I haven't really looked that closely at Metro. I've been figuring that it's kind of like PhoneGap for the desktop, which may be a completely mistaken assumption. Even if Metro replaces WPF universally as the preferred way of creating Windows desktop apps, I agree that the need for desktop apps in the first place is diminishing.

Prior to the big Windows 8 announcement, it was pretty clear that WPF was a high priority for Microsoft and, a pretty safe bet in terms of skills to learn. That's not the case anymore, and even if Windows 8 and/or Metro fail with consumers, the shift in resources for things like Visual Studio, etc. will could really hurt WPF (which needs better development tools pretty badly, based on my experience). That could hasten its demise and possibly .NET's as well.