Chio

From a quick survey of the implementation probably not very well since, for example, it is using dynamic dispatching for all distance calculations and there are a lot of allocations in the hot-path.

Maybe it would be better to post this repository as a reference / teaching implementation of HNSW.

Happy new year! Committed to making this new year my, and your, best year so far!

Thanks for being a great community.

This is an interesting lawsuit as it is a *company* seeking damages due to DMCA abuse by a third party, and my understanding is that this is very widespread (no source sorry). Is anyone aware of any studies done on the total cost¹ (vs benefit¹) of the DMCA due to malicious actors?

¹ defining what is a cost vs benefit (and how much) is probably the hardest part, maybe after acquiring the necessary data.

I don't believe this is how it is actually implemented in _most_ companies. Where I work every PR must have a linked story / bug / etc but anyone has the rights to create a story so it acts more as a way to track what changes actually goes into a release for x-teams to review and see if they need to document it, etc.

In regard to refactors, people tend to just squash them into another change they are making. This makes the git log a bit harder to follow at times, but people did this back when we just used to push to trunk too so I don't think the story is the deciding factor.

I've taken the opposite approach a lot of times. So instead of asking what you can add you might want to look at what apps / bookmarks that you can remove. Do you need a link to the reddit frontpage, or can you narrow it down to one or two specific subreddits that you want to check, or maybe remove it entirely if it does not add much value to your daily life.

Apps that I would recommend however are many of the apps that tries to gamify physical activity. I use Garmin, but I am not sure if the app works without owning the accompanying smart watches and there are plenty of alternatives, and the gamification and accountability that it offers around physical activity makes it a lot easier to get out of the door (which is always the hard part). Physical activity has long been known to have a huge positive effect on mental capacity and health so well worth spending an hour or so every day on.

I agree wholeheartedly on your points regarding async, which is a topic I've tried to avoid so far in all of my Rust projects because of all the reasons you've already raised above and you really don't need it for most use-cases.

To add my own few cents to this very common discussion Rust is hard is the same way that most programming languages that rely "non-standard" paradigms are hard because they challenge your current mental model of programming. However "different", instead of "hard", would be a better way to describe these sort of languages like Rust, Prolog, and Haskell (as well as a ton of other languages).

If you look at Rust from this perspective then it becomes much more valuable to consider learning because it teach you a different way to modelling your data, and how to break-up your code; and while a language like Java may not force you to consider the borrow checker you will probably be a better overall Engineer knowing how to make it happy even when working in other languages.

On the topic discussed in the actual article: I can't wait for scoped threads to finally go stable since being forced for throw an Arc around almost everything you want to share between threads does not really suit Rust which really emphasise zero-copy in their standard library.