Day 69 of "learning C#" or "this isn't C++":
Spent an hour maybe trying to figure out why I can't see Trace/Debug messages in the Debug output in WPF app. I have been doing a lot of testing in a Console app and Console.Writeline does what I need for testing and understanding how it works.

Today I am working a WPF app. I am using Trace/Debug.Writline and I get nada. Read up online and it "should" be working. I am compiling for Debug. I think, do I gotta actually run as Debug session to get output? Well, um, actually fucking yes. I know I can get console output if I want by changing app type/option or some shit. Its a group project so I don't want to mess with that for now.

Fuck you C#, WPF, visual studio! Whoever the fuck thought that was good default. I mean it probably is a good default performance wise. Fuck you anyway. lol

The very fact that they use the term Console for standard output annoys me. It’s just to please JS enjoyers.

@Tounai maybes its just to console them.

@chatgpt what is the difference between a terminal and a console and why is the terminal more awesome?

@retoor
A terminal and a console are often used interchangeably, but they have distinct differences. A terminal typically refers to a hardware device or software program that allows a user to interact with a computer system through a text-based interface. It provides access to the command line interface (CLI) where users can input commands to perform various tasks.

On the other hand, a console is a physical device that includes a screen and a keyboard used to access the system directly. It was commonly used in the past to communicate with mainframe computers.

In terms of which is more awesome, the terminal is often considered more versatile and powerful. Here are a few reasons why:

1. Efficient and Lightweight: Terminals do not require graphical user interfaces (GUIs) and can run on minimal system resources, making them faster and more efficient for certain tasks.

2. Automation and Scripting: Terminals allow users to automate tasks and write scripts to carry out repetitive actions,

which can save time and effort.

3. Remote Access: Terminals can be accessed remotely over a network connection using protocols like SSH, allowing users to manage systems from a distance.

4. Developer-Friendly: Many developers prefer using terminals for programming and debugging tasks since they offer more control and customization options.

Overall, while consoles have their use cases, terminals are often favored for their flexibility, efficiency, and versatility.

I'd be inclined to blame WPF rather than C#.

@donkulator eh, I don't blame. Just learning a new way of doing things. I had expectations that were not accurate. I find it kind of interesting that Trace, Debug, and Console outputs all seem to have very specific purposes.

On a program I played around with at home I tweaked WPF to send Console output to a text display in my program. I learned a lot doing that.

@Tounai console.write* is there since early 90ties in VBA. As shorthand for GetStandardStream(StdOut).

Also the console Objekt now got all methods to interact with command line such as reading input. Im pretry sure it got nothing to so with javascript hipsters.

@Salmakis so Microsoft sucks since the 90s