The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
WinForms, or better, the Common Controls, are very underappreciated; it is a mature product. A standard that is not just available on Windows anymore, as WinForms work just as happily under Linux.
I'm sure that WPF is better for graphics, as advertised.
I build tools for people that work. They don't care about flashy, they care about reliability and predictability. I'm not paid for animated borders, but functionality - and will probably still be maintaining WinForms code by the time that our great overloads predicted that AI will write code.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
As someone who has spent far too much time wrestling with the quirks of the MS supplied WinForm Controls ... many of which are .NET wrappers around old COM.ActiveX Controls ... I have a less "rosy" view of them: imho, they are a herd of cats
From the "cup is half-full" perspective, you could say that MS enabled a market for 3rd. party control developers to create much more powerful and internally consistent controls, with consistent API's. I remember, so well, my elation when I discovered Andrej Stojkov's Lidor TreeView Control: felt like I had gotten out of jail
I was excited, initially, by WPF's promise of an all-vector rendering engine, bubbling event-model, superior binding facility, etc. And, of course, symbiosis with a web-stack, SilverLight.
There was some great work done here, on CP, by pioneers like Clifton, Adrian Alexander, O'Hanlon, Josh Smith, Sacha Barber, and others.
The reality of programming in Visual Studio with WPF, however, just was not right ... for me.
Then, came the debacle of Metro, the deprecation of SilverLight, the failure of Metro, MS VP Sinofsky's (Metro honcho) departure, the WinRT hoop-la, etc. A lot of devs felt burned; fence-sitters, like me, decided to stick with WinForms.
If only ... one can waste time fantasizing about ... WinForms had a retained-mode all-vector, 2d graphic engine, and WPF's event and binding facilities. A Designer.cs file-format that at least was more XML-like, or, even XAML like.
A few comments:
1. For WinForms TreeView and ListView that would be the 'HideSelection Property.
2. There is a more recent (2016) 2nd. ed. version of Nathan's book for Windows 10: [^], but it's listed as unavailable on Amazon, currently.
«While I complain of being able to see only a shadow of the past, I may be insensitive to reality as it is now, since I'm not at a stage of development where I'm capable of seeing it.» Claude Levi-Strauss (Tristes Tropiques, 1955)
Really like your summary of the situation because that is my experience too.
I've been using those old controls since Win3.1 -- okay Win95 --- okay I guess they get updated once in a while but it seems like those are the same controls we've been working with since Win95 and you're right there is plenty about them that is bad / crufty / cracked.
But, since we've been working with them for 20 years we know how to get around those things.
I remember about the time Vista released I started messing around with WPF / XAML and wasn't that impressed seemed like a bunch of stuff to learn to draw my own controls when I could more easily drop a windows treeview on a WinForm app and be done. I'm no graphic artist so I let the TreeView be a TreeView.
Then the Silverlight debacle and all the rest just as you said.
Now Microsoft does the head-fake to UWP. I start learning XAML again and it is pretty cool.
But then you go to look for these things that must surely be easy even in XAML since people have been doing WPF / XAML, right? But you can't find the answers? It's all just crazy.
Also, it is very interesting that the author changed that book's name to Building Windows 10 Apps from the previous name of Universal Windows Apps.
Makes me feel like Microsoft whispered in his ear something like,
"Uh, we're backing off the whole UWP/UWA thing, so..." ugh!
If that is the case, then why are these companies accepting Bitcoin payment: Virgin Galactic, Overstock.com, TigerDirect, Dish Network, Expedia, Newegg, Directnic, Microsoft, Zynga, Starbucks, and Subway.
Nice job taking the first google result that showed up but I actually went to the microsoft store sight, put a laptop in the cart, went to checkout and they had 2 selections as form of payment. Visa and Paypal. Let me know how that 15,000 dollar footlong tastes. Most companies don't take it anymore because of the volatility of the bitcoin/us dollar exchange. I believe overstock might still take it. Expedia says if you don't book in 10 minutes they don't guarantee price. Sounds convenient to me. With 1,300+ there may be a couple winners, but more losers. Just like the dot com bubble.
I think there are a number of factors in play with crypto currency not least of which is FOMO - fear of missing out! It is a volatile market and there are way too many coins out there - over 1500 now with more coming - see icowatchlist.com[^]
As an aside, I have a friend who was paid 10 bitcoin for a job a few years back and no longer has any idea what he did with them!!!
Also, there was an article the other day about a guy that bought 25000 when they were a dollar a piece - now worth over 420 million!!!
They may want to protect their assets. Funny thing about tech, most people don't understand it. They just know it's new. The market loves new stuff to play with. People get bored. The same thing happened with the dot com bubble. The people that were smart enough to get in at a great time will hopefully be smart enough to get out or protect their assets before the market corrects itself (via a crash, etc.).