this post was submitted on 23 Aug 2023
76 points (93.2% liked)

Programming

17691 readers
138 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
76
thrown into a backend project as a backend dev with a language I don't know, how fucked am I? (lemmy.world)
submitted 1 year ago by [email protected] to c/programming
53 comments fedilink hide all child comments
 

The title itself is a recipe for disaster. Also this is a semi rant.

Yesterday I was informed that I will have the honour to implement the core functionality - which is an interface layer to use the driver of a very expensive hardware shit - of the software I’ve been working on as a frontend dev.

There are two possibilities for the language: C++ or C#. The one that was proposed/imposed is C#, which I know nothing of, while at least I have some hobbyist experience with C++; when asked if I could take some time to familiarise myself with C# I was basically laughed in the face, saying I will learn on the field and at least some of them have some experience with it.

Should I insist to go with C++, or is that an even worse idea in an already fucked up situation?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

Circular references can also impede garbage collection, don't forget.

And to further clarify, a proper object wrapping a resource like the ones you listed will release them when it is eventually collected, in the finalizer/destructor. However, you can't know when that will happen, so we have IDisposable.Dispose() which can be used to release whatever critical resources the object is holding right away. :)

[–] [email protected] 1 points 1 year ago (1 children)

This is very wrong. Circular references are no problem for the garbage collector at all (https://stackoverflow.com/questions/8840567/garbage-collector-and-circular-reference). You basically don't need to worry about manual memory management at all, if you're only dealing with managed code.

[–] [email protected] 1 points 1 year ago

I was specifically thinking of circular event handler references, which I know was a thing at some point in the past. If .Net has improved since then, great.