_vbdg

It used to be really hard, though I believe there's now experimental cmake support. Vcpkg has it, so if you're using that, it's much easier.

And the funny thing is, C++ is so complex it's the last language I'd expect to have multiple optimizing compilers (though rust is probably similar, I imagine.)

When will people learn that government is always to be distrusted, most of all in times of crisis?

I2P is really slow, though.

A Python background explains that, as y'all tend to worry less about memory usage and re-use. This can have its upsides, but it probably creates a bit of a blind spot here, because it's referencing the sort of thing one probably wouldn't do in python.

No, it's priced into most computers. Retail costs over $100 last I checked (and more for pro), though OEMs pay cheaper prices for that sort of volume. There are also sketchy keys available for ~$20.

I appreciate the help, though I've looked inside my ports before and found neither dust nor lint. The problem seems to be mostly with cheaper stuff. I've mentioned this to USB-C enthusiasts before and gotten back, "Well, just by better-quality stuff." The difference is, I never had any problem with the connection on cheap USB-A devices. If the connector seemingly can't be made both cheaply and well, that is a huge flaw with the standard and means it ought to be abandoned wholesale.

HN doesn't permit users to downvote replies to their comments, so you can be sure that wasn't me. Maybe it's obvious to you, but I'm not sure how one qualifies as an expert in the necessity (or not) of removing the word "master" from github branches. Would you please elaborate?

You still didn't tell me who these "experts" are, though it seemed you were referencing several in a prior comment, so I'm unsure how to address that point. I'd of course respect the opinion of an expert, and I'd recognize that I have a very good chance of being wrong, but that makes it even more important to question things. If I'm right, we come to a better conclusion; if I'm wrong, I learn something.

Really? Git doesn't have any actual references to slavery. Even if it did, is everyone now disallowed from using such terminology in a benign manner? I'm not sure calling it "main" makes sense, in any case; anyone who uses git flow knows it's not the "main" branch where most of the day-to-day development takes place. As the article points out, this is a reference to "master" as in a master copy, which is why there's no corresponding reference to slave. If you download the official git book from the website and control-F for "slave", do you know what you'll find? Zero results!

Discussing a crab is not politics, but attributing to it a non-existent gender is intentionally contrary to most people's social beliefs (especially outside of the SV bubble) and is thus political. Calling it a normal boy or girl isn't.

If, however, some community members wish to do that, they open to others the option to speak their minds on the topic, including stating that such an action ought not to be taken because no such gender exists. Contrast this with how most "codes of conduct" are written: they would permit community members to speak in favor of such a decision but not against it, as doing so would be "hateful", "bigoted", or "exclusionary".

I guess I can't, because they're both political statements. Politics is either allowed or not. I assume, however, you have some reason in mind, by how you phrased the question.

Maybe in other places on the internet, sure, but I was referring mostly to the code-of-conduct-gated development communities that pretend not to discuss politics while allowing specific viewpoints above others.

If communities want to go down that road, fine, but then they need to get out of this weird limbo where some views are allowed and some aren't. That means that someone must be just as free to say, "I believe the rust crab should have a normal gender because non-gender-binary is not a thing." without getting banned or cancelled. Right now it's reverted to a very don't-ask-don't-tell-like environment where one can either speak in support of such things or not say anything at all, effectively pretending to agree just as in your military example servicemen had to pretend to be straight.

> the most common spelling still is café

Really? The data say otherwise: https://books.google.com/ngrams/graph?content=caf%C3%A9%2Cca...

Do you have another source that supports the popularity of the diacritic variant? Rather, café doesn't increase in popularity until after 2000, and thus would appear to be an affectation of sophistication.

That strikes me as much closer to linguistic than nationalistic; there's more than one nation that speaks English. Could you clarify what about that statement was flame-y? All I did was ask that adontz make the argument rather than making a dismissive statement.

> SILHOUETTE OF JAPAN

This may sound pedantic, but Japan the island or Japan the nation? It seems to refer to the island(s). On the other hand, the "farsi symbol" is of a particular nation rather than a given set of boundaries. Nations can be renamed, but the island of Japan refers to the chunk of earth. Add to that that nations get redrawn every so often in the middle east and I can understand the position.

> who cares, if it is not used in U.S. right?

This isn't intended to sound rude, but why should an American care? Dismissing the argument that for better or worse many people hold doesn't do any good. Making it might convince them otherwise.

> not having all the characters needed for English

I've heard this argument a few times, and each time it's just as contrived, particularly if you stick to American English. While I'm happy to acknowledge it's not good enough for other languages, ASCII is plenty good for English. Unless you're trying to type cafe with an accented e to be fancy or type that old conjoined-ae character, ASCII is fine for everyday usage. See the fact that most Americans have never installed a separate keyboard layout.

> This also enables third party APIs, such as the popular NVIDIA Cuda compute API, to be hardware accelerated within a WSL environment.

Dollars to donuts this is why Microsoft is implementing this. GPU acceleration is becoming a critical feature for many users (but especially developers) and this will continue. If WSL is to be a serious competitor, this is necessary and I'm glad to see it showing up. This is true of cloud compute, too, and Microsoft is betting big on cloud as its future growth area.

> Only the rendering/compute aspect of the GPU are projected to the virtual machine, no display functionality is exposed.

The Linux gaming folks will be pretty sad about this one. Anyway, this isn't really a Linux port of DirectX. This is GPU compute via DirectX APIs.

So now, I'm just waiting on monitor mode/AF_PACKET for WSL...

Aside from the "proprietary bad" arguments (which is enough to get traction on HN), there are a bunch of practical reasons:

1. It's faster. Mr. Devault, Sourcehut's author, runs a benchmark site that demonstrates this: https://forgeperf.org/

2. The e-mail based workflow is (in my opinion) superior; I don't have to use some clunky web interface.

3. I can run it myself, on-premise, for free.

If one needs a docker container to run a text editor, I think that says all that needs to be said about it.

Interesting note that this guy's choice of PAKE, Cpace, was chosen about a week ago by the CFRG for use in IETF protocols. Cpace is new, but that's a big vote of confidence for it.

I just built a new hackintosh with opencore, and compared to clover, it was so much nicer. The documentation [0] is excellent; I'm able to grok what each option does rather than just guessing. It also feels so much less janky than clover did. Better filevault support, faster, leave SIP on, etc. It's also better in that one can avoid polluting /L/E /S/L/E, which will also allow users to keep running kexts even after Apple deprecates third-party ones.

[0]: https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/...

Ghidra is better than IDA for almost every use case I've found. I was working on reversing a bunch of mipsel binaries; Ghidra's decompiler worked, IDA didn't. I also tried r2 with Cutter, which did a decent job and had by far the slickest UI. Just my two cents.

Cryptography I by Dan Boneh: https://www.coursera.org/learn/crypto

It's a great introduction to fundamental concepts. After you finish, I'd recommend reading this book he co-authored, which goes into more detail and covers more advanced concepts: https://toc.cryptobook.us/book.pdf

Huge thanks to Mr. Nystrom for writing this. It's been very useful and I've learned a ton reading/working through it.

Nah, I think it won't.

1. Not everything needs encryption, so QUIC's built-in TLS doesn't always make sense.

2. Not everything that needs encryption needs TLS specifically. TLS is not a one-size-fits-all solution.

These reflect the fact that QUIC is a transport protocol for the WWW more than a TCP replacement.

By the way, does anyone know why QUIC specifically put NewReno as its official congestion control [0]? Different environments benefit from different algorithms so I don't see why.

[0]: https://tools.ietf.org/html/draft-ietf-quic-recovery-12#sect...