Earlier quoted context omitted.
Shit WPF is deprecated, whats the Microsoft preferred way to writes GUI apps on the desktop?
electron
You're looking for trouble... But after thinking I have to second that.
Thoughts on Microsoft's Time-Travel Debugger
21–30 of 77 posts
Re: Thoughts on Microsoft's Time-Travel Debugger
#22Awesome, I hadn't heard of TTD. It's great to see reverse-debugging get serious attention
rr sounds fantastic... unfortunately, I can't use it because AMD CPUs aren't supported (they simply don't have adequate performance counters; it's not rr's fault). With the exception of Ryzen, but even there, the performance counters apparently aren't entirely reliable (meaning sometimes the debugger will go haywire)
Re: Thoughts on Microsoft's Time-Travel Debugger
#23As the article talk mentions it as well; I wonder how good it scales for long running binaries and how well it integrates with stuff like .net native. I mean doing artificial demos on a dll is cool, but how well will it scale for say tracing bug in say a key-value store than runs for days and then crashes.
As far as I know, .NET Native isn't really something you're supposed to be running for development; just a target you compile to for maximum performance that should produce identical results (think of it as an uber-release mode).
Microsoft advises to regularly test .NET Native builds, to ensure UWP apps work properly when compiled at the store level.
Re: Thoughts on Microsoft's Time-Travel Debugger
#24What I personally do not enjoy as a developer about MS products is that eventually they hit end of life and you are left hanging. With open source stuff, if the project is used enough there will always be some maintainer.
Besides the fact that you're simply not right (COM, MFC, ATL, SWF, WPF, etc are all deprecated yet still supported and maintained), how is this on topic?
COM used to be treated as a legacy technology by Microsoft, but it is pretty central now.
Re: Thoughts on Microsoft's Time-Travel Debugger
#25Re: Thoughts on Microsoft's Time-Travel Debugger
#26What I personally do not enjoy as a developer about MS products is that eventually they hit end of life and you are left hanging. With open source stuff, if the project is used enough there will always be some maintainer.
a) not true for reasons already given here b) they are(have) open sourcing a lot of developer stuff; I didn't check but would not surprise me if this ends up on github too if it didn't already with a good OSS license
Re: Thoughts on Microsoft's Time-Travel Debugger
#27What I personally do not enjoy as a developer about MS products is that eventually they hit end of life and you are left hanging. With open source stuff, if the project is used enough there will always be some maintainer.
It seems to me like it’s the other way around. Microsoft keeps comparability forever, which also has tons of negative consequences. With Linux it seems almost like you have to recompile everything anew for each system and each updates, where tiny differences in distributions can break things.
A statically compiled application will run for just about forever on linux. glibc has extensive backwards compatibility too. If you pack your application with its libraries, there's very little to worry about.
Kernel modules need constant recompilation but that's a very separate issue from programs.
Re: Thoughts on Microsoft's Time-Travel Debugger
#28Earlier quoted context omitted.
Shit WPF is deprecated, whats the Microsoft preferred way to writes GUI apps on the desktop?
The flavor-of-the-day is UAP/UWP, which actually has awesome APIs. The only problem is that it's Windows 10+ and can't make universal or standalone binaries.
> and can't make universal or standalone binaries
Highly ironic for a framework that's called Universal Windows Platform :D
Re: Thoughts on Microsoft's Time-Travel Debugger
#29Earlier quoted context omitted.
https://youtu.be/eGl6kpSajag
Damn, is he actually that humble or is it just a persona? Skip to around 4:15 for the actual content.
He's a smart kid and obviously likes himself to a degree that gets a bit annoying but his achievements are quite something. I still find the presentation style pretty entertaining.
Re: Thoughts on Microsoft's Time-Travel Debugger
#30Very cool. I seem to recall geohot doing similar to TTD in the past?
qira is cool but it doesn't scale. It singlesteps the program, recording the effects of each instruction in a fairly naive way. gdb's built-in reverse execution is similar. It's roughly a factor of 1000x slowdown and requires massive storage.
Getting the overhead down to < 2x (for rr) or 10x (for TTD), with reasonable trace sizes, requires much higher tech ... and is absolutely necessary for most users.