151–160 of 435 posts
Earlier quoted context omitted.
I care. I don't remember that advice, and I never have trouble relocating my fingers in sub seconds.
So you'd rather press F5 to build and F6 to debug instead of tapping "Build" or "Debug"?
Earlier quoted context omitted.
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
If you're using a MBP at the moment - then you're already pressing the fn key to use the functions keys for anything other than the media-stuff they've been designed around for years. Your workflow is exactly the same - you're just using soft keys instead of physical ones.
Earlier quoted context omitted.
does it support reverse debugging yet?
What I want to know as somebody trying to learn C/C++, is Xcode good for somebody who is wanting to try their hand at bare metal stuff? I always hear how bad it is outside of app dev. but can it help me be productive compared to CLI environment or just using a text editor with nifty add-ons?
.NET open source and officialy supported on *nix, some version of SQL Server on Linux, cross platform Visual Studio Code editor, now Visual Studio for macOS...
Earlier quoted context omitted.
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
If you're using a MBP at the moment - then you're already pressing the fn key to use the functions keys for anything other than the media-stuff they've been designed around for years. Your workflow is exactly the same - you're just using soft keys instead of physical ones.
Earlier quoted context omitted.
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
Are you kidding me? How can you not see that this is nothing more than an arbitrary habit that you've grown comfortable with? Imagine the function keys had never existed to begin with. Don't you think we would have come up with a different way of stepping through code with a debugger? I understand that it's annoying to have to change your habits, but you're a developer for crying out loud: Your job is literally to ch…
Sleeping in a bed is an arbitrary habit that you've grown comfortable with, why not sleep on the floor, or in the bath?
The fact is that when developing and debugging, the function keys represent the most efficient way of stepping through code, and a part of this is to do with their physical presence on the keyboard.
I know that I don't have to use them, there are other ways to achieve the same thing, but those things have always been there and I choose the function keys because they are the best option.
Earlier quoted context omitted.
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
If you're using a MBP at the moment - then you're already pressing the fn key to use the functions keys for anything other than the media-stuff they've been designed around for years. Your workflow is exactly the same - you're just using soft keys instead of physical ones.
Earlier quoted context omitted.
I get the impression that WPF is pretty much on life support.
Shit, last time I was on Windows, WPF was the new hotness. What is the latest thing?
Earlier quoted context omitted.
> WRONG. The removal of a dozen keys from an already gimped keyboard is decidedly anti-developer. I am a developer and I could not care less about function keys. Why the duck would developers need function keys? Even for Vim, the age-old advice is to remap Esc so that you keep your hands on the home row. A flexible multi-touch strip of context-aware keys can do much more things -- e.g. map debugger step moves when I'…
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
Use the strip bar in debugger keys mode, or function keys mode for non-updated apps?
Or use printf statements (seriously -- I never advocated for much debugger use, unless it concerns very focused stepping. A lot of people step all around and examine everything and anything for ages with no clear idea of what the bug might be).