Thoughts on Microsoft's Time-Travel Debugger
robert.ocallahan.org
Thoughts on Microsoft's Time-Travel Debugger
1–10 of 77 posts
Re: Thoughts on Microsoft's Time-Travel Debugger
#2Very cool.
I seem to recall geohot doing similar to TTD in the past?
Re: Thoughts on Microsoft's Time-Travel Debugger
#3What 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.
Re: Thoughts on Microsoft's Time-Travel Debugger
#4Very cool. I seem to recall geohot doing similar to TTD in the past?
Re: Thoughts on Microsoft's Time-Travel Debugger
#5What 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.
Re: Thoughts on Microsoft's Time-Travel Debugger
#6What 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.
Are you a .net developer??? Everything of MS still works, nothing has been deprecated. The comment you gave is really plain wrong.
Re: Thoughts on Microsoft's Time-Travel Debugger
#7What 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?
Re: Thoughts on Microsoft's Time-Travel Debugger
#8What 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?
Shit WPF is deprecated, whats the Microsoft preferred way to writes GUI apps on the desktop?
Re: Thoughts on Microsoft's Time-Travel Debugger
#9Earlier quoted context omitted.
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?
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.
Re: Thoughts on Microsoft's Time-Travel Debugger
#10As 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.