The large wheel next to the cabin is also messed up. It means the cabin must be smaller than the track width, since the cabin is squized inbetween the wheels. But in reality the cabin is always wider then the wheel base.

I agree that the lines look sharp, but the composition makes no sense. The giant wheel next to the cabin is just weird. Why is the wheel bigger? And why is the cabin not wider than the track width? This looks like a tractor, not a locomotive. The steam is comming from the coal storage, but not from the engine. And why does the coal storage have a chimney anyway? Then there are the weirdly shaped coupling rods. These mistakes make no sense in the context of a steam locomotive, but they look plausable. I’m no AI expert, but it certainly is a weird looking steam locomotive.

…

I’m starting to think this was designed wrong intentionally. What better way to farm engagement then to wrongly draw a train in a meme about autism, on Lemmy?

Best do that with something that hides the taste well. Maybe create a drink so aggressive that it might as well be a cleaning product. Just add some caramel to paint the whole thing black and you’re good to go. People will love you coca product.

I have barely any experience with raw gdb, but debugging is something that allows for a lot of contextual actions. Even just placing a breakpoint is simpler if you can click the line instead of copy-pasting the line number. But also evaluating expresssions while on a breakpoint, or a graph with an overview of all threads. I doubt these are straight-forward commands in gdb, and if they are, you need to figure out the exact parameters (like line number).

Furthermore, I have tried raw gdb once, and got super confused as to what I was supposed to do or look at. Yet every IDE makes it trivial to use debuggers. Learning the options available to you is much easier in a well designed GUI.

GUIs just being front-ends for a CLI tool is a horrible idea. This is why most git GUIs fail so terribly. I have seen too many of those where all the buttons were just replacements for CLI calls. If it is just a front-end for a CLI, then why the heck not just use the CLI?

A good git GUI has not been designed to just wrap the CLI. Instead, it works with the structure of git (commits, branches, tags, etc), and builds around those from the ground up. Only once the functionality has been designed should the question arise: What CLI commands do we need to implement this?

I remember using mumble in a time when smartphones weren’t even a thing yet. Love to see the open source tool outlive everything else!