As a sql server dev at microsoft, this has been lifeline for debugging customer issues pretty quickly. It is slow without indexing, however once it is indexed, it works really well.
Thoughts on Microsoft's Time-Travel Debugger
51–60 of 77 posts
Re: Thoughts on Microsoft's Time-Travel Debugger
#52Could someone help explain how this is different from a regular debugger that lets you step back in the call stack? Does Chrome dev tools debugger (that lets you step back in the call stack, even for asynchronous calls) come close to TTD?
Re: Thoughts on Microsoft's Time-Travel Debugger
#53Earlier 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?
Some examples: XNA, Silverlight, WCF, etc.
If WCF is deprecated, what's the current preferred way for developing service-based applications?
Re: Thoughts on Microsoft's Time-Travel Debugger
#54Earlier 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.
UWP also is like Silverlight more so in that it is missing a lot of stuff from the original WPF, you have to basically relearn it. However, Win2D is pretty good, nice performance.
Re: Thoughts on Microsoft's Time-Travel Debugger
#55What 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.
WPF has seemed to basically been WinFormed, it still works, they might fix the bugs, but it isn't going anywhere and will eventually feel outdated.
Re: Thoughts on Microsoft's Time-Travel Debugger
#56Could someone help explain how this is different from a regular debugger that lets you step back in the call stack? Does Chrome dev tools debugger (that lets you step back in the call stack, even for asynchronous calls) come close to TTD?
when you hit a break point in Chrome, you are suspending a live thread with current memory and stack state.
This tool is more like a profiler, that instead of studying a current snapshot of the state, it will show you how the state changed over time. (also, this is for native apps)
Re: Thoughts on Microsoft's Time-Travel Debugger
#57Tools like this have always been how Microsoft segments the highest-price "Ultimate" version of Visual Studio (or whatever MS marketing has renamed things this month). As best I can tell there is no mention in this article of how this feature will be priced, which winds up limiting how often it will be useful simply because of availability. Let me know when this shows up in the free SKUs ("Express") or perhaps even t…
> even the drug-pusher-like "Community" (first hit is free, unless/until you're making money) edition.
I mean, yeah it's not free-for-all, but "first hit is free" is kind of unfair. A company is not allowed to use it if they have more than "(a) more than 250 PCs or users or (b) one million U.S. dollars... in annual revenues" [1], and if it doesn't meet that criteria, it's usage is limited to 5 concurrent instances. More accurate would be "first hits are free, and you won't start getting charged until you're big enough where you can afford it".
Just making the distinction because I still have friends who think they can't use Community at home if they want to have a side project that makes money.
Re: Thoughts on Microsoft's Time-Travel Debugger
#58Earlier quoted context omitted.
Breakthroughs are situational. Many first tier militaries spend time thinking about urban pacification. Within those contexts, it really is a breakthrough. Just like how stealth aircraft were a breakthrough, and also totally useless in this situation.
Agree, but comparing it to the tank, in WW1 or WW2, where industrialized nations were fighting each other directly is flawed.
Remember Churchill?
https://www.awesomestories.com/asset/view/Turing-s-Letter-to...
Re: Thoughts on Microsoft's Time-Travel Debugger
#59Earlier 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.
That's actually him. The stories of his shitty behavior when he was in college and Didn't Have To Do The Work Because Don't You Know Who I Am (which didn't work out so well) still circulate in my friend groups.
Re: Thoughts on Microsoft's Time-Travel Debugger
#60What 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.
The main problem with Microsoft in the past is that they didn't make money except by selling more software licenses. Things have begun to change with the cloud stuff, but the mentality is still there in the dev tools and frameworks - instead of "if it ain't broke, don't fix it" it winds up being "every time we move the cheese we make more money".
Microsoft's incentives still don't quite align with their developer/customers, but Microsoft does an amazing job pushing toward whatever is tossed out for sale as the new & shiny each year. The entire company is an amazing marketing machine.
https://www.joelonsoftware.com/2002/01/06/fire-and-motion/
Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET – All New! Are these technological imperatives? [...] The competition has no choice but to spend all their time porting and keeping up, time that they can’t spend writing new features.