SevenNation

> ... This site works primarily by analyzing for each user the frequencies of the most common words and phrases in the English language. Accordingly, the easiest way to avoid being identified is to simply use different words than you ordinarily would when writing. More sophisticated models than the one I made can use punctuation, comma usage, and capitalization to identify you so try alternating those as well. Services like Quillbot can help with you this but depending on your circmstances you may not want to send your writings to a third party service.

HN offers many other threads which could be tied together, including:

- time of posting

- ratio of replies to top-level comments

- comments being mainly upvoted or downvoted

- sentiment (mostly angry, dismissive, questioning, etc.)

- most common topics (keyword analysis of post being replied to)

- ratio of new posting to post replies

- first-to-comment on a post

- lone comment on a post

- etc...

It seems very likely that sooner or later every pseudonym for posting content will get discovered and linked. The lesson here is don't post anything that would cause you undue shame or harm if linked directly to your legal name.

> The largest elephant in the room to address is probably Rust. ...

Breaking this down, I can only find two practical problems the author has with Rust:

- long compile times

- the ownership model ("the borrow checker")

The rest of this paragraph appears to be much more general in nature.

Given that the project is only 58,000 lines of D/C++, it's hard to believe that compile time alone is so bad as to drive a decision toward an experimental language like Jai.

So it appears that the main problem the author has is the ownership model ("the borrow checker"). It would be interesting to know more, but the author does not elaborate.

AFAICT, the Rust compiler can be viewed as enforcing the good practices that C++ developers already recognize. So how can this be an issue at all, especially given the ability break out of the ownership model into unsafe Rust (or use other tricks) if the situation calls for it?

The code makes it clear that the --release flag is being used, but not the text. Sometimes optimization posts written by authors trying to up their skills end with a "...and then I turned on the release flag and tada - 80% improvement." It might be useful to point out that release mode is being used to compile.

> With Rust, though, one needs to learn entirely new ideas — things like lifetimes, ownership, and the borrow checker.

Those three things are actually just different facets of the same thing: ownership. The bad news is that you must learn Rust's ownership model to use Rust idiomatically. The good news is that you can do a lot without learning Rust ownership model at all. Just clone all your values. Not advisable for production code, but great for getting over the ownership model hump.

I didn't see anything about the hiring process needed to get high-documentation culture to work. Many developers don't write well. Some don't empathize with the reader and so can't communicate complex ideas effectively. Others lack the ability to abstract their ideas. Many will be coming from the exact opposite of a high-documentation culture and so simply will not value good documentation.

Asking people with poor writing skills to work in the way described here seems like it could lead to problems without a selection process favoring good writers, or at least a training system to get new hires up to speed.

Here's a simple question: what is NATO's goal in this conflict?

If it is, as some officials have suggested, to throw the Russian army back across the pre-2014 borders, how exactly could that happen?

If militarily, that almost certainly means NATO-equipped and possibly trained Ukrainian forces attacking Russian forces located inside Russia on a regular basis.

How many ways are there to do this without triggering a nuclear escalation?

> Even after this news emerged, Podolyak maintained that NATO should enact a no-fly zone in Ukraine, which would likely require Western pilots to fight their Russian counterparts directly, putting four nuclear-armed nations at war. Kyiv continues to deny that it fired the missiles.

Then there's the question of what might drive Ukraine to exaggerate or plant evidence implicating Russia in attacks on NATO territory, or to hide evidence contracting that position. Hopefully, The Tonkin Gulf Incident, and the disgraceful way it justified an unjust war after whipping the American public into a bloodthirsty frenzy, is still on the radar.

Facilitating the exchange of stored value for goods and services without a trusted third party.

> ... What is the point of it without exchanges?

The point is that exchange of bitcoin for goods and services is possible without trusted third parties. Whether you approve of what is being traded is a separate question.