Conversation started Nov 22, 2016 at 23:43.
jrh
jrh
Nov 22, 2016 23:43
@RobertHarvey Not sure if you're familiar with John Carmack but here's another article you might like, I found it in one of the comments on the question I mentioned earlier number-none.com/blow/john_carmack_on_inlined_code.html
I try to read most blogs on programming style that I can find, but articles that mention specific cases where the programming style did or didn't help the author are especially interesting for me.
Nov 23, 2016 00:09
> Typically I am there to rail against the people that talk about using threads and an RTOS for such things, when a simple polled loop that looks like a primitive video game is much more clear and effective.
Funny, a simple polling loop is exactly how our workflow server works.
jrh
jrh
IIRC Win32, and thus Winforms (and WPF?) is also just a polling loop behind the scenes.
Sort of. It's called a "Message Pump."
It's event-driven, but fired events have to wait in line to be executed.
And it's got some intricacies, like ripping a hole in the universe if you try to modify a control from another thread.
(ergo, Invoke())
jrh
jrh
I sometimes kind of miss the simplicity of game rendering when working with Winforms, I guess at one point it in time it was significantly more efficient to only redraw a control if it needed to be updated, but I sometimes would prefer a capped frame rate.
And by "simplicity" I mean the flow of control is simple, vector arithmetic and light calculations can be pretty hard.
The problem with Winforms is not so much its complexity (or relative lack thereof), it is its propensity for encouraging spaghetti code.
WPF solved this problem by using Model-View-ViewModel as its organizational metaphor.
And having killer data binding and composability.
Nov 23, 2016 00:25
"would be the "best" way"... if this question is holding you up in your progression, then I would strongly encourage you to read this: joelonsoftware.com/articles/fog0000000018.htmlTravis J just now
jrh
jrh
Nov 23, 2016 00:35
interesting, I've never done WPF but I kind of hope to experiment with it when I have time.
I think I avoided spaghetti code with my stuff (hopefully) but I've heard of some codebases that definitely fell into the spaghetti category
Nov 23, 2016 00:49
There's a fellow on Pluralsight that made some really good training videos on WPF.
And I think WPF is probably much better suited to game programming than Winforms is.
jrh
jrh
I do game programming for fun, mostly in C; Winforms is for work, I originally mentioned WPF as an alternative to Winforms but I got a firm "no" from my boss, so I kind of tabled it for a while. I think he wasn't willing to go into WPF because as far as I know all of our previous software's in Winforms.
Though after I graduate I might dig into WPF, I should probably start using it for one off utility programs I make sometimes, just to get a feel for what it can do.
If it's a line-of-business application, web applications using some state-of-the-art framework like Angular 2 or Aurelia win hands down over WPF.
But there are still companies that succeed admirably in WPF, because they've gotten used to the desktop application metaphor and are good with it.
Doing web applications as well as WPF's capabilities generally requires some investment in a top-notch toolkit like Telerik.
jrh
jrh
Noted, though the application I'm doing Winforms for is technically embedded and strictly desktop.
Sure. Sometimes that's all you really need.
 
Conversation ended Nov 23, 2016 at 0:56.