
*Laughs in Calculus of Variations*

*Laughs in Calculus of Variations*

So you are in fact the opposite of this meme.
I assume you’re referring to the technicality that the thirteenth amendment allows unpaid labor to be legally compelled out of prisoners, and that’s a valid thing to be outraged about, but your statement is wildly misleading to anyone who isn’t already aware of that technicality.
The existence of the loophole is terrible and should be amended, but it’s nowhere near the humanitarian crisis that widespread chattel slavery was. Ironically that will probably make it that much harder to be fixed since it’s more difficult to draw pubic outage towards it.
Your description actually illustrates how terribly inaccurate the metaphor was. If enslaved people imitated the people who enslaved them, they’d be sitting in a rocking chair on a porch sipping lemonade.
The US has a unique and relatively recent relationship with chattel slavery so people are more sensitive to it now.
The earliest record of the master/slave terminology being used in engineering is 1904 by which point slavery was already outlawed in almost every country, including the US. You’re right to say that chattel slavery in the US was a uniquely grotesque form of slavery, but there is no system of slavery in history where slaves are primarily imitating their masters. No matter what anyone’s sensitivity to the topic is, it’s a bad fit for what’s being described.
There’s equal evidence for the groyper claim as there is for the trans roommate claim, which is to say nothing but hearsay being pushed out by the Governor of Utah.
Wise people plant trees whose shade they’ll never stand in.
If two characters are hurting your 260 character limit then you have other more serious problems to contend with.
Until people start applying the same logic everywhere for consistency, not just in file names.
Just you wait…
Did the software industry learn nothing from Y2K? Was it too long ago already for people to remember the mess we made for ourselves?
Saving two characters in a file name is not worth the hell you are leaving in your trail by shoving this nonsense in an obscure corner of production code that people are going to forget about until it’s too late.
I recently had an accountant file something for the IRS that was dated as expiring in 1940 when it should’ve been 2040. I had to catch it myself after reading through 70 pages of dense forms before it was sent off, and I could’ve easily missed it.
Digital records have existed long enough now that it’s downright irresponsible to leave off the century for anything where having an accurate date might even slightly matter.


Maybe they can do a resolution of inquiry as a first step, demanding the executive branch provide the document to congress.

No no, that would hurt the feelings of the man-children that get triggered by vegans existing. They’re too sensitive, they can’t take it, it would be an act of cruelty towards animals that have no personal agency, which we all know is something vegans can’t condone.
There are several ways to achieve an effect equivalent to operator overloading in Rust, depending on exactly how you want the overloading to work.
The most common is
fn do_something(arg: impl Into<Args>) {
...
}
This lets you pass in anything into the function that can be converted into the Args type. If you define the Args type yourself then you can also define any conversion that you want, and you can make any construction method you want for it. It’s a small touch more explicit than C++'s operator overloading, but I think it pays off overall because you know exactly what function implementation all different choices of arguments will be funneling into.
I’ll admit there’s one thing from C++ that I frequently wish were available in Rust: specialization. Generics in Rust aren’t exactly the same as templates in C++ but they’re close enough that the concept of specialization could apply to traits and generics. There is ongoing work to bring specialization into the language, but it’s taking a long time, and one of my projects in particular would seriously benefit from them being available.
Still, Rust will have specialization support long before C++ has caught up to even a quarter of the benefits that Rust has over it.
Even with modern C++ it’s loaded with seg fault and undefined behavior footguns.
The times when C++ feels more ergonomic than Rust are the times when you’re writing unsafe code and there’s undefined behavior lurking in there, waiting to ambush you once you’ve sent it to production. Code that is 100% guaranteed safe is always, and I really want to emphasize this: always more ergonomic to write in Rust than it is to write in C++.
Show me any case where C++ code seems more ergonomic than its Rust equivalent, and I will always be able to show you how either the C++ code has a bug hiding in it or how the Rust code can be revised with syntactic sugar to be more ergonomic than the C++.
C++ was far and away my favorite language (I used it professionally for 10 years and was always excitedly keeping up with new ISO developments), until I learned the basics of Rust…
Now it’s my firm belief that the world will become a better place when C++ stops existing. C++ just has no positive role to play in a world where Rust exists at the level of maturity that it already has.
Whatever they might try to do to C++ to make it less intolerable will be in vain until they’re ready to break backwards compatibility. And once they’re willing to break backwards compatibility to legitimately improve the language, they’re just going to end up with a messy knock off of Rust.
I don’t think they were suggesting that the therapist was reinforcing any of this, just that the therapist was horrified by what they went through.


I’m not trying to shill for Google but I really think it would be a mistake to break up Google without breaking up Microsoft simultaneously if not first. If they actually manage to crack open Google’s search and browser monopoly, who do they really think is going to start filling in that void? Local mom and pop search engines…? No it’s primarily going to be Microsoft with Bing and Edge, and I’m absolutely certain that whatever people don’t like about Google having its monopolies is going to be orders of magnitude worse if Microsoft gains ground there.


The “reform is impossible” is a self-fulfilling prophesy because it leads leftists to never try to get involved, which means they’ll never get a seat at the table, which means they’ll never be able to steer the party.
I certainly can’t prove that the influence of big money can ever be overcome within the party by grassroots organization, but you also can’t prove that it’s impossible (you can only prove that it’s difficult, which is something I certainly won’t dispute).
You certainly can’t prove that a true socialist movement will ever gain traction in America. It seems like the general public is so brainwashed they would rather be indentured servants of large corporations than lift a single finger to seize the means of production.
So we’re left with two unprovable paths to consider, and here’s the thing: the two paths are not mutually exclusive. Leftists can try both at the same time with neither being disruptive to the other. So this is the pragmatism: consider all possibilities and put the eggs into more than one basket.
Or would the band name be “Actual Dragons”?