Gray hair can look lovely. I accept
One can’t say the same for skin cancer.
This is a secondary account that sees the most usage. My first account is listed below. The main will have a list of all the accounts that I use.
Garbage: Purple quickly jumps candle over whispering galaxy banana chair flute rocks.
Gray hair can look lovely. I accept
One can’t say the same for skin cancer.


Really? I’ve been told by all my dudes into hardware that AMD is where it’s at for value. Plus, Intel has manufacturing issues. I’m sure there’s good deal out there if you look, but I feel dissonance between this article and what I hear in my circle.


It’s not just that. Imagine the dependency management trying to hold onto 32 bit compatibility.


Now is the time to invest in cat/dog ears.
Not financial advice.
Yup. Noticed it was wrong instantly because I had to study this work way back in high school.


The meme is so nerdy I love it.


The best part is there’s already a default error handler! If the program dies, you know there was an error.
Wasn’t that disproven by Snopes?
That’s the good spice.


We had an intern do this once. We changed our server config to make sure it wouldn’t accept such operations.


Hard disagree. Corporatism is distinctly on the fascist side of the house, and it distinctly has an in-group and an out-group at its very basic ideological level whereas communism in principle seeks to eliminate classes.
Now, you might have classes in practice, sure, but explicit racism/ethnostate situations is definitely not a defining feature of communism. I would agree if you said this sign describes authoritarian regimes! But, I think that communism has a distinct meaning that is separate from being authoritarian whereas fascism is inherently authoritarian (in group oppresses everyone else). This seems to be conflating something to say that it’s communism as well.


Forced password resets.
Entropy defeats recall.
Desk blooms with secrets.
This is not a request, but a prophecy.
I don’t know. My grandma was jacked. She was a rather imposing figure.


Absolutely. I once wrote a server for a factory machine that spawned child processes to work each job item. Intentionally we did not free any memory in the child process because it serves only one request and then exits anyway. It’s much more efficient to have the OS just clean up everything and provides strong guarantees that nothing can be left behind accidentally for a system where up time was money. Any code to manage memory was pointless line noise and extra developer effort.
In fact I think in the linker we specifically replaced free with a function that does nothing.


I don’t blame you. I have to use a professionally sometimes and I am not a fan. It’s an absolute behemoth of the language filled with warts and cruft.
Sometimes it is the best choice for a project, but I prefer languages with simple, orthogonal concepts.


Pfft compilers. Just use assembler.


You call the destructor. It’s simply not automatically done for you with the concept of going out of scope.
Back when C++ was simply a text pre-processor for C, you could see these normal function calls. You can still see them in the un-optimized disassembly. There’s nothing magical about a destructor other than it being inserted automatically.


Also goes for mobile. You use more memory and apps get killed.
You just might get your wish.