ChipTuner on Nostr: Are you interested in systems programming or application programming? I assume ...
Are you interested in systems programming or application programming? I assume application.
I personally suggest starting with C then quickly moving to C++. C++ is a superset of C with fun fancy features. When in doubt you can always fall back to functional/procedural programming if needed. Others will disagree because they think C is just fundamentally broken or unsafe (propaganda imo) and you may pickup bad patterns. Yeah there is a lot of sloppy C in examples out there for sure. Deeply understand your fundamentals, don't skip anything in the syntax and you'll be alright. Learn "defensive programming" and you're unlikely to make an unrecoverable mistake. Mistakes will happen, you will cause a buffer overflow now and then, probably a segfault and a stack smash, but youll get better and there are tons of tools to help with that.
You can trust your compiler but don't rely on it. I test myself on every line/edit catching errors before I try to compile it, trying not to become reliant on the compiler like they try to teach you in CS school. In CE school bugs can be far more time consuming on hardware.
As Michael mentioned, were working on a C++ development kit for nostr, and I'm working on a cryptography library called noscrypt.
https://github.com/ShadowySupercode/aedile-ndk
https://github.com/VnUgE/noscrypt
I personally suggest starting with C then quickly moving to C++. C++ is a superset of C with fun fancy features. When in doubt you can always fall back to functional/procedural programming if needed. Others will disagree because they think C is just fundamentally broken or unsafe (propaganda imo) and you may pickup bad patterns. Yeah there is a lot of sloppy C in examples out there for sure. Deeply understand your fundamentals, don't skip anything in the syntax and you'll be alright. Learn "defensive programming" and you're unlikely to make an unrecoverable mistake. Mistakes will happen, you will cause a buffer overflow now and then, probably a segfault and a stack smash, but youll get better and there are tons of tools to help with that.
You can trust your compiler but don't rely on it. I test myself on every line/edit catching errors before I try to compile it, trying not to become reliant on the compiler like they try to teach you in CS school. In CE school bugs can be far more time consuming on hardware.
As Michael mentioned, were working on a C++ development kit for nostr, and I'm working on a cryptography library called noscrypt.
https://github.com/ShadowySupercode/aedile-ndk
https://github.com/VnUgE/noscrypt