Live data from Hacker News

Thoughts on Microsoft's Time-Travel Debugger

robert.ocallahan.org

11–20 of 77 posts

Re: Thoughts on Microsoft's Time-Travel Debugger

#11
post #8

Earlier 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?

electron

Re: Thoughts on Microsoft's Time-Travel Debugger

#12
post #10

As 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).

Re: Thoughts on Microsoft's Time-Travel Debugger

#13
post #5

What 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.

Depends on your choice of distribution. Some distribution will distribute compiled binaries for each architecture. And there are flatpaks that are distribution agnostic.

For your own applications you will most likely use a container anyways and that gives you fairly reproducible builds.

Re: Thoughts on Microsoft's Time-Travel Debugger

#14
post #5

Earlier quoted context omitted.

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.

Depends on your choice of distribution. Some distribution will distribute compiled binaries for each architecture. And there are flatpaks that are distribution agnostic. For your own applications you will most likely use a container anyways and that gives you fairly reproducible builds.

Just... go away.

Thanks.

Re: Thoughts on Microsoft's Time-Travel Debugger

#16

What 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?

Some examples: XNA, Silverlight, WCF, etc.

Re: Thoughts on Microsoft's Time-Travel Debugger

#19
post #5

What 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.

Backwards compatibility across releases of the same product, sure. But some products hit their end of life and that's it.

If a product is deprecated, it may not receive security updates or fixes and such. As a user that puts you in a tough situation.

Unfortunately as a user there's not a lot you can do to influence the governance of those products or try to do something to keep them around. If the vendor decides to sunset a product that's it. That's all I am trying to say.

Post reply on HN