macOS IDE to use for C++ on M1 Mac

[gloryofgreece]

I am a new owner of M1 Mac Mini. I am just learning some C++ programming and sometimes leetcoding. I noticed that one can't use code::blocks on m1 natively and I think eclipse/vs community are just a bit too heavy for what I am working on. xcode is really complicated.

For C++ pros on this community, what IDE do you use on your m1 macs?

 

[casperes1996]

Not per se IDEs but depending on situation; visual studio code, nano/vim and jetbrains. I’ll also use Xcode to edit from time to time but mostly I only use Xcode for swift

 

[ipxsystems]

Another vote for VSC.

 

[lloyddean]

Terminal.app and BBEdit invoked from it; so no IDE really

 

[TiggrToo]

Not per se IDEs but depending on situation; visual studio code, nano/vim and jetbrains. I’ll also use Xcode to edit from time to time but mostly I only use Xcode for swift

We think the same. VSCode and JetBrains are both pretty much always running, and I’ve been a vi user since the 1990s!

 

[lloyddean]

Xcode, making the hard things easier and the easy things hard!

If you're learning C/C++/Swift languages and not learning a "platform" try an on-line editor, compiler and run environment along the lines of ...

<https://rextester.com/l/cpp_online_compiler_clang>

There are many such on-line resources.

 

[casperes1996]

We think the same. VSCode and JetBrains are both pretty much always running, and I’ve been a vi user since the 1990s!

Is it now we dunk on the emacs people?

 

[sgtaylor5]

Viper is a Vi emulation package for Emacs.

 

[lloyddean]

New in Xcode 13
Preferences → Text Editing → Editing → Enable Vim key bindings

 

[casperes1996]

New in Xcode 13
Preferences → Text Editing → Editing → Enable Vim key bindings

Yeah. If someone’s reading this however and thinking “What’s vim? Should I enable this?”… Don’t. Vim is cool and all, but if you don’t already know how to use it it’s going to confuse the pants off ya, when you try tying d20 as a variable name in your dice rolling app, and 20 lines of code disappear, haha

 

[Senor Cuete]

I am a new owner of M1 Mac Mini. I am just learning some C++ programming and sometimes leetcoding. I noticed that one can't use code::blocks on m1 natively and I think eclipse/vs community are just a bit too heavy for what I am working on. xcode is really complicated.

For C++ pros on this community, what IDE do you use on your m1 macs?

This demonstrates an important fact: learning any language/IDE is a huge investment in time, with a steep learning curve. Switching to a new one is a big task. For this reason people will always tell you that the one that they know is great. Frameworks like Cocoa are very powerful and also complex. If you take the time to learn XCode / Cocoa you will have complete mastery of your Mac but this is a lot to learn.

 

[lloyddean]

This demonstrates an important fact: learning any language/IDE is a huge investment in time, with a steep learning curve. Switching to a new one is a big task. For this reason people will always tell you that the one that they know is great. Frameworks like Cocoa are very powerful and also complex. If you take the time to learn XCode / Cocoa you will have complete mastery of your Mac but this is a lot to learn.

Especially given the sad state of Apple Documentation currently.

 

[Senor Cuete]

Yes lloydean and things really went down-hill when Apple decided to invent Swift.

 

[lloyddean]

Yes lloydean and things really went down-hill when Apple decided to invent Swift.

That will happen following a secret decision to rewrite and implement the application development API's in a completely new language.

Saw it coming when Swift was announced and little to no updated documentation appeared but that doesn't dull the pain.

 

[casperes1996]

That will happen following a secret decision to rewrite and implement the application development API's in a completely new language.

Saw it coming when Swift was announced and little to no updated documentation appeared but that doesn't dull the pain.

The documentation available for some of the newer Swift stuff is also really great. While there are still a lot of missing things, what's accompanied the current iterations of SwiftUI has been really excellent documentation

 

[lloyddean]

The documentation available for some of the newer Swift stuff is also really great. While there are still a lot of missing things, what's accompanied the current iterations of SwiftUI has been really excellent documentation

Agreed, and it looks promising.