.

Did you actually mean Windows Millennium Edition, or was that a typo?

He's going through a massive divorce that could cost him billions.

Which divorce? He must have had an ironclad pre-nup with Riley.

Assuming its 'his' to begin with. Not hers already?

Exactly. It's the marriage that costs you half your assets, not the divorce.

I'm quite sure that Musk is the one responsible for the increase in value of his companies, not someone who's been uninvolved in running them.

Having someone parent your kids while you work 120 hours a week is pretty useful. It's the opinion of the courts that that job is worth exactly half of whatever the working spouse brings home. If you don't like that arrangement what's the point of being married in the first place?

...said somebody totally unacquainted with marriage.

I am able to concentrate on growing my career because of my spouse, not in spite of them.

That's not the case for everyone.

I agree. I'm a white guy who's gone through some very difficult stuff. When SJWs talk to me about my privilege, it just enrages me. Academic left discourse turned me from a middle-of-the-road guy to someone adamantly against the entire program of social justice.

Guilting people into reducing emissions has been ineffective. Better would be to embrace geoengineering.

Clearly, it'll be the world's first domed city

Honestly, why? Most of the time, you want to write C++, with exceptions, and the STL. You can make this kind of programming as robust as you want against memory allocation failure.

If you don't want to use this style of programming, for whatever reason, check out sys/queue.h. It's already on your system, if you're using some kind of Unix.

If you are using an RTOS (which many timing-critical applications run on), you should be worried about memory allocations happening under the hood.

If you don't have full control over when memory is being allocated/reallocated, your system is now non-deterministic.

With pure C, you can know exactly when those few extra instructions for resizing your dynamic array are going to happen.

Same in C++. There's `std::vector::reserve`, which grows the vector's underlying physical buffer, without logically adding any new elements. If you `reserve` enough capacity before inserting anything, it's even a `O(1)` operation.

Vector and possibly string have that. The vast majority of STL structures do not.

All containers from the C++ standard library (please don't call it STL, that's Stepanov's original library) can be parameterized by an allocator. You can use whatever allocation policy you like best. However, most people use the default allocator because it's good enough.

In any case, while C++ has lots of defects, “loss of control relative to what C gives you” isn't one of them.

(a bit of topic - but I'm humbly trying to learn more...) I've got zero experience writing allocators. Is there some common ones you use provided somewhere? Do you write your own? (in which case can you point me to where to learn to do that properly)

I don't write allocators myself, but Boost has a pool allocator library [http://www.boost.org/doc/libs/1_60_0/libs/pool/doc/html/inde...], which conforms to the Allocator concept defined in the standard library [http://en.cppreference.com/w/cpp/concept/Allocator].

Thank you

Yeah, that's true.

Thank you. There is somebody else on this fucking planet who understands that memory is not limitless manna from heaven.

Indeed. It's incredibly disingenuous, not to mention a risk to the public health, to scream "STD!" equal loud for HPV and HIV.

There's a reason you can't sell your kidneys...

Poor people are the most likely to be exploited and the most likely to use their donated organs. It's been shown that empirically economically incentivising organ donation crowds out altruistic organ donation, a non negligible source of supply and that those who donate for money do not experience a long term economic benefit but do experience long term health consequences.

By ignoring the reality of the situation you create a demand for people to cause severe risks to their health for short term problems, preying on the least educated group of people who have a severe information asymmetry... You also crowd out an altruistic source as it no longer becomes a societal issue but rather an economic one.

You also create an unnecessary class problem as middle and upper class people have access to organs, but not poor people who are the actual source of supply...

Good. I'm sick of people walking over copyleft licenses generally. It's only because of copyleft that there exists a pro-sharing social norm in the software development community. If you kick down the GPL, the norm will shift back toward proprietary software everywhere. You, young developer, have no idea just how shitty a world that is.