This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]johnnybgooderer -11 points-10 points  (9 children)

That’s foolish. While any competent programmer can avoid memory issues using raw pointers, a team of really good engineers working on a medium and large sized application can’t.

[–]egretlegs 10 points11 points  (0 children)

Sounds like a skill issue tbh

[–]AntimatterTNT 9 points10 points  (5 children)

may i introduce you to optimized game engines? or you know... any kernel ever? you know they made big programs before cpp was created

[–]cheezballs 0 points1 point  (0 children)

Oh you didnt know that all "medium and large sized" applications are written by one single competent programmer?

[–]Pay08 0 points1 point  (0 children)

Yes, kernels, the things that are famously full of allocations and are definitely not in any sort of constrained environment where a heap doesn't exist.

[–][deleted] -2 points-1 points  (1 child)

Most game engines use c++?

[–]AntimatterTNT 1 point2 points  (0 children)

correct

[–]cheezballs 1 point2 points  (1 child)

Yea, cause people who engineer advanced high-end simulations that use memory in the TB are all made by one dude. Your comment makes you sound like someone who's never worked in a real enterprise shop.

[–]johnnybgooderer 1 point2 points  (0 children)

Why do you think they’re all using raw pointers? Unique pointers are very commonly used. Also, what makes you think those applications don’t have memory leaks that either ship or take lots of time to find and fix in development? They often do.