I'm glad to see more Microsoft dev tools on other platforms but don't lose sight of why this is happening. Microsoft is shifting their business to the cloud. They make their money off Azure and other services. In other words, they are making their money mainly off of developers now and its in their best interest to get on the good side of devs which is why they suddenly have a vested interest in open sourcing tools a…
> don't lose sight of why this is happening. Microsoft is shifting their business to the cloud. Why is this a bad thing? Microsoft is a company, they exist to make money. A huge new market for them is 'Cloud' and they're doing everything they can to make that as appealing as possible.
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?
I have used both Xcode and Text editor & Terminal for C/C++ development. In my opinion both work equally well but I would advise you to use the Text editor and Terminal method because it means you need to learn how things like build systems, LLDB, Valgrind and more work. This knowledge is essential when the IDE does something Unexpected and you need to fix it.
So Microsoft is treating the Mac more seriously as a professional platform while Apple is treating it less seriously? I'm not saying this in a snarky way; I mean it literally as a change of corporate strategies in both companies. Microsoft seems to be saying, If you are a pro mainly using the Mac for professional work, we want to do a better job of empowering you, and Apple seems to be saying, If you are a pro mainly…
People aren't going to do development on a tablet or a smartphone anytime soon.
> People aren't going to do development on a tablet or a smartphone anytime soon.
My set up proves you wrong: Nexus 7, bluetooth keyboard, a Debian chroot with git, vim, python and apt. I take that with me to sketchy places instead of my laptop. I think a 10-inch tablet could be more comfortable to read, but I love the Full-HD screen and pocketability of the 2nd-gen N7. I find it amazing that 3 years later and no other Android tablet has a screen resolution that's comparable.
> 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.
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.
Do YOU know the difference? Would it hurt to be more concrete? I'm going to venture a guess based on my assumptions, which are probably wrong, but then we can at least start a discussion: -VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another -VS Code doesn't support runtime debugging (breakpoints) -VS Code doesn't have a visual editor -VS Code doesn't ha…
Disclaimer: I'm not using the C# extension > VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another F2 "Rename Symbol" (works on Go with gorename). Can't imagine using Roslyn doesn't (or won't soon enough) allow the same. From the readme: Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc. > VS…
>Obviously VS Code is not an IDE (as VS is)
OBVIOUSLY? :D VS Code starts looking more and more like an IDE to me :-) Still looking forward to hear what people define as an IDE!
Thank you for your detailed response by the way, not picking on your post, just curious what everybody finds so "unIDEish" about VS Code.
> 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.
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 change how other people do work, to make it more efficient, easier to learn and so on. We all know that our users often resent us, because we change how they have to do their work. But we do it anyway, because we believe deeply (and mostly rightly) that the benefits of progress outweighs the short term annoyances of having to change habits. But when we're the ones who have to change, hoo-boy, suddenly the sky is falling. Give me a break.
> 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.
The debug step keys will show up in the touch bar? If they are not stupid enough to swap them around sometimes, then they should stay in the same position.