Well, I can certainly see how the Ukrainians are so bitter about "what the USA did in Ukraine for last 10 years". They're positively throwing themselves at you.

No, wait; that's a javelin.

He wouldn't finish a day's worth of fact-checking until well into the subsequent administration.

On Slashdot, it's always 1999.

The students aren't to blame when every single adult in their life is telling them that they have to must a college degree to be a real adult, or when curriculum they should have been taught in middle school is deferred to college. The educational industrial complex, together with widespread classism, has duped these kids before they even have a chance to figure it out for themselves. Heck, we often force them to plan out their own future financial destruction before they even have their first part-time job.

The only solution is to starve the beast. I support wiping out college debt if we *also* outlaw college loans. Pay out of pocket, get a grant, or learn a trade skill and support a family 4 years earlier.

As an addendum: in the above example, I said the pointer is not leaked. This is strictly true. But it can lead to a reference to a destroyed object (what you would call a NRE in Java and C#). Thanks to RVO/NRVO, this is much, much less of a concern. If you have a factory function that creates a PBar object, you can create it on the stack in the function, return it as an unadorned PBar, and it will be guaranteed to be returned by the function without being popped off the stack just for leaving scope. This works even if the backing pointer is std::unique_ptr.

getBar() doesn't leak because the backing variable bar is not a pointer. It will be allocated and deallocated with its parent Foo object. Nine times out of ten, this is probably the best thing to do.

But if you DO need bar to be pointer to Bar, and you need to return a reference to &bar as Bar*, then that is where the PIMPL design really shines. The wrapper object (of type, say, "PBar", for example) can passed and returned by value 90% of the time with no performance penalty, thanks to copy elision and RVO. This brings you a step closer to writing code just as expressive as Java and C# without littering your code with std::unique, std::forward, std::swap, et al. If the PIMPL is backed with std::unique, you have the added advantage of single-ownership being strictly enforced at compile time. You wouldn't ever pass around Bar, at that point, just PBar. If you need perform mutative operations on the backing Bar object, you would integrate that functionality into PBar.

For me, though, hiding smart pointer boilerplate is only the second-best thing about PIMPL. The best thing is having a place to put custom allocation: std::allocator performs very poorly in applications with a lot of memory churn.

I didn't read your comment, but I would like to know about your HOSTS file.

1. Microsoft is the largest contributor for open source.
2. The Linux kernel includes code contributed by Microsoft.
3. The Halloween email was twenty years ago. No one on the email chain works at MS, anymore.
4. FOSS beat Microsoft. SCO is dead. The genie cannot be rebottled. Rather than shakes their fists at the sky, MS chose to adapt to the new landscape. This has understandably robbed some people of much-anticipated schadenfreude, as MS seems to be doing quite well.
5. It will never be the year of Linux on the desktop, because the desktop is not important.

IMXP, Imperial is only used in household, day-to-day stuff. Driving, groceries, recipes, and hanging pictures on the wall. In college, we exclusively used metric in anything math & science-related. That was 20 years ago. When I started grade school 35 years ago in the worst school system in the country, we were still taught both sides of ruler.

I'd say we're more "dual-system" than imperial.

Considering every single upper-echelon position has turned over since than, sometimes many times over... yes.

I used to think my degree was worthless because every boss I've ever had in the industry either didn't have a CS degree, or had no degree, at all. Then I realized that much of my workplace recognition over the years was due to the fact that I had a pretty good handle on CS trivia: algorithmic proofs, grammar theory, assembly and all that attendant side knowledge like bit math, etc. So no, I no longer regret getting a CS-degree.

My thinking shifted even more when, 15-20 years later, a lot of new hires I have to mentor learned to code at camp. Let me tell you: they are somehow worse than other folks with no CS-degree. At least an unschooled hacker has that self-motivated spirit that compels them to be competent. All code-campers have is a terrible case of Dunning-Kruger.

If so, our judicial system is as fucked as the other branches.

"under new authorities it was granted by President Trump and Congress"

Then you need to explain why those same incels forgot to hate all over the provided list of very excellent movies (except Avatar. Space Fern Gully was bad, IMHO; and didn't it have straight white male lead, anyway?).

Ok, that does make sense, especially if you think of Command Division as "command of ship" instead of "command of people."