• 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle


  • coltorl@programming.devtoProgramming@programming.dev...
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 year ago

    It’s honestly not that hard, the language was made to be simple. The complexity associated with the language largely has to do with the legacy applications the language supports. If you look at a greenfield project (eg CHADstack (it’s a joke project, but pretty fun to get exposure to some esoteric stuff for a couple hours)) you’ll actually pick the language features up pretty quickly.


  • coltorl@programming.devtoProgramming@programming.dev*Permanently Deleted*
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    edit-2
    1 year ago

    C++, I am a library developer with some embedded experience. I can easily interface with c libs and expose my lib with a c interface. With clang, static analysis catches most bugs before runtime. Everything I write can be compiled nearly anywhere with very little dependencies required. Excellent IDE and LSP support with a ton of documentation on the language features available (admittedly, there are a lot). The standard library is gigantic, useful, and well documented. It is used everywhere, so resources and example source code in C++ are very easy to come by. Project configuration (via CMake) is extremely powerful and expressive (though not technically C++).

    Some languages have some of the elements I listed, but no other language has them all.










  • I know I was being snarky, but I do appreciate the context. The monopolizing bit clarifies it for me as something that you may own but if found to be monopolizing the resource to a detriment of the community, that is not acceptable. So “own” isn’t really used here to mean entitled to, but something that you may possess as an appropriation while acting in good faith.