C memeGregor@gregtech.eu to Programmer Humor@programming.dev – 205 points – 1 months agoA screenshot from youtube, Virbox18Post a CommentPreviewHotTopNewOldEh... ship it. RAM is cheap."Uh, Boss, our customers are sending us the invoices for their RAM purchases."OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMSAlso electron. Because somehow a full blown separate FF instance is more ram efficient than electron.Well, Electron uses Chrome, so yesThat's why I preallocate the max memory I will need just like I was taught to do in Fortran. You can't leak what you don't have. Heap allocation failure > gradual memory leak Checkmate atheists.This is why I only allocate on the stackPeople who are enthusiastic about using pointers in C++ are doing it wrong. Never use a pointer when you can get away with a reference.For C++, yes. But "reference" is just a way of using the pointer when it comes to CSure, but that's technically allocation-agnostic either way.Based nasa compliant engineerThis guy gets it Static allocation for the SIL ratingsStack overflow intensifiesI only use the registers. ~I’m sorry~rip random amiga machineThe line causing the memory leaks is actually the lack of a line: free().
Eh... ship it. RAM is cheap."Uh, Boss, our customers are sending us the invoices for their RAM purchases."OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMSAlso electron. Because somehow a full blown separate FF instance is more ram efficient than electron.Well, Electron uses Chrome, so yes
"Uh, Boss, our customers are sending us the invoices for their RAM purchases."OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMSAlso electron. Because somehow a full blown separate FF instance is more ram efficient than electron.Well, Electron uses Chrome, so yes
OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMSAlso electron. Because somehow a full blown separate FF instance is more ram efficient than electron.Well, Electron uses Chrome, so yes
Also electron. Because somehow a full blown separate FF instance is more ram efficient than electron.Well, Electron uses Chrome, so yes
That's why I preallocate the max memory I will need just like I was taught to do in Fortran. You can't leak what you don't have. Heap allocation failure > gradual memory leak Checkmate atheists.
This is why I only allocate on the stackPeople who are enthusiastic about using pointers in C++ are doing it wrong. Never use a pointer when you can get away with a reference.For C++, yes. But "reference" is just a way of using the pointer when it comes to CSure, but that's technically allocation-agnostic either way.Based nasa compliant engineerThis guy gets it Static allocation for the SIL ratingsStack overflow intensifiesI only use the registers.
People who are enthusiastic about using pointers in C++ are doing it wrong. Never use a pointer when you can get away with a reference.For C++, yes. But "reference" is just a way of using the pointer when it comes to CSure, but that's technically allocation-agnostic either way.
Eh... ship it. RAM is cheap.
"Uh, Boss, our customers are sending us the invoices for their RAM purchases."
OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMS
Also electron. Because somehow a full blown separate FF instance is more ram efficient than electron.
Well, Electron uses Chrome, so yes
That's why I preallocate the max memory I will need just like I was taught to do in Fortran. You can't leak what you don't have.
Heap allocation failure > gradual memory leak
Checkmate atheists.
This is why I only allocate on the stack
People who are enthusiastic about using pointers in C++ are doing it wrong. Never use a pointer when you can get away with a reference.
For C++, yes. But "reference" is just a way of using the pointer when it comes to C
Sure, but that's technically allocation-agnostic either way.
Based nasa compliant engineer
This guy gets it
Static allocation for the SIL ratings
Stack overflow intensifies
I only use the registers.
~I’m sorry~
rip random amiga machine
The line causing the memory leaks is actually the lack of a line:
free().