Problem is some CS grad comes along, sees this and thinks "What if that were HTML?" and now we have the current state of front-end development. Sad. All we really want is a const o = new Div("#my-thing"). I remember doing XAML development back in the WPF hay day. 2009-ish. Csaml and Xaml are pretty close. I hated Xaml a lot. So much so that all the views and components I wrote at the company I worked for were done using Canvas + DrawVisuals as to avoid Xaml all together. Funny, sad, ironic, and nostalgic all at the same time.
A mistake I've made a few times is thinking let's separate code and data, that sounds great. But then I realize I need to do some pretty complex stuff in the data, and I'm faced with the choice of building some hacky monstrosity, or a DSL, or just going back to the main code.
The basic tutorial examples of SwiftUI look like something you could easily do in XML, but doing it in real code makes it so much more powerful, and ultimately simpler for everyone.
You know, I suspect most people reading this weren't around for the "XML everything!" era and don't get the joke. They legitimately think it's a post about an experimental markup language.
Not just XML, but I see this article as a direct jab at XAML specifically.
XAML, the famously verbose dialect of XML tied to .NET, which hasn't seen any changes made to the core language design despite its numerous ergonomic failures (e.g. the xmlns mess). I can't explain why no attempt has been made to make it more usable.
> Basically, CSAML is an alternative syntax for C# based on XML and, more specifically, on XAML, the Extensible Application Markup Language that plays such an important role in the forthcoming WinFX and the Windows Presentation Foundation.
Almost as if someone on the inside at MS would have knowledge of what was in development and decided to poke fun at it. 2008 was when it was released, it was in development prior to that.
Seems like Petzold gave up on following Microsoft's indecisiveness regarding what should be the official GUI framework for Windows. No WinUI 3 book is planned.
I think it's more that he got married and is now 70 and wanted to retire and wanted to do other things after 30 years of writing books about application APIs.
Charles more or less states as much on his website.
I'm surprised to see you downvoted because I absolutely agree. It seems like a common-sense opinion that C# and Typescript are unnecessarily verbose in comparison to F#. (I don't know Clojure so can't compare.)
No one wants to hear their favorite language compared to XML noise I guess. Not trying to offend, just pointing out that it's legitimately how it feels. If you love C# this shouldn't offend you. I'd be curious to hear if someone said the same thing about F#, I'd want to know what they were comparing it to, maybe the new thing will be a new favorite of mine.