Bluetracker

Tracks Blizzard employees across various accounts.

Okay here's my latest in "Microsoft who picked that default Windows behavior, please stop immediately" Command Prompts closing when the .exe crashes so you can't read the error output. Seriously what genius thought that was a good automatic behavior??

Okay here's my latest in "Microsoft who picked that default Windows behavior, please stop immediately" Command Prompts closing when the .exe crashes so you can't read the error output. Seriously what genius thought that was a good automatic behavior??

DevSpacePrez

Posted 3 years, 7 months ago (Source)

Okay here's my latest in "Microsoft who picked that default Windows behavior, please stop immediately" Command Prompts closing when the .exe crashes so you can't read the error output. Seriously what genius thought that was a good automatic behavior??

DevSpacePrez

Posted 3 years, 7 months ago (Source)

Yes I know you can manually open a command prompt and browse to the .exe so the output gets preserved But goddamn why is that always necessary? Because we're terrified a user may not know how to close a window?? If you can't close a window you're not gonna get far in this OS

Chadd Nervigg

Posted 3 years, 7 months ago (Source)

@DevSpacePrez I'm pretty sure this is just a remnant of the fact that programs used to be much less interactive. They were an executable chunk of code that you could run and they would do their thing and then finish and be done. That's just a really rare use case these days.

<blockquote class="quoted">
    
</blockquote>
Okay here's my latest in "Microsoft who picked that default Windows behavior, please stop immediately"

Command Prompts closing when the .exe crashes so you can't read the error output.

Seriously what genius thought that was a good automatic behavior?? (<a href="https://twitter.com/i/web/status/1488297337214537729">None</a>)
<hr/>

<blockquote class="quoted">
    
</blockquote>
Yes I know you can manually open a command prompt and browse to the .exe so the output gets preserved

But goddamn why is that always necessary? Because we're terrified a user may not know how to close a window??

If you can't close a window you're not gonna get far in this OS (<a href="https://twitter.com/i/web/status/1488297507943682048">None</a>)
<hr/>

<blockquote class="quoted">
    
</blockquote>
@DevSpacePrez I'm pretty sure this is just a remnant of the fact that programs used to be much less interactive. They were an executable chunk of code that you could run and they would do their thing and then finish and be done. That's just a really rare use case these days. (<a href="https://twitter.com/i/web/status/1488298446855360513">Chadd Nervigg</a>)
<hr/>

Bluetracker

Okay here's my latest in "Microsoft who picked that default Windows behavior, please stop immediately" Command Prompts closing when the .exe crashes so you can't read the error output. Seriously what genius thought that was a good automatic behavior??

Tweet