To add to the list, here's my rust-noob implementation of the Kalman filter.
Show HN: Algorithm Cookbook in Rust
11–20 of 73 posts
Re: Show HN: Algorithm Cookbook in Rust
#12"My other goal is to show developers that C++ and Java kinda suck" -- really?!
Re: Show HN: Algorithm Cookbook in Rust
#13"My other goal is to show developers that C++ and Java kinda suck" -- really?!
Yeah, it's a pretty poor way to represent Rust to an audience that is ostensibly it's target audience.
Re: Show HN: Algorithm Cookbook in Rust
#14"My other goal is to show developers that C++ and Java kinda suck" -- really?!
Yeah, it's a pretty poor way to represent Rust to an audience that is ostensibly it's target audience.
Any developer who can't name something that "kinda sucks" about their language probably isn't ready to learn a new language.
Re: Show HN: Algorithm Cookbook in Rust
#15MIT license is good, but I always wish that sample code was available under CC0 -- and presented with explicit permission to copy and paste without preservation of notices. (A request to link back optionally when practical is fine.) That makes it easier for sample code to achieve the ends of maximum code reuse and popularization of the underlying technology.
Agreed. I once tried to submit a small snippet I found on stackoverflow to an open source project. Stackoverflow user content is licensed under creative commons, cc-by-sa (see https://stackoverflow.blog/2009/06/25/attribution-required/ ). I included attribution, but it was rejected. I totally understand why. CC0 is much preferred in this case.
FYI, newer Stack Overflow code is licensed under an MIT license with a link in code comments serving as attribution. See https://meta.stackexchange.com/questions/272956/a-new-code-l...
Re: Show HN: Algorithm Cookbook in Rust
#16Earlier quoted context omitted.
Yeah, it's a pretty poor way to represent Rust to an audience that is ostensibly it's target audience.
Any developer who can't name something that "kinda sucks" about their language probably isn't ready to learn a new language.
The quoted comment isn't about particular shortcomings in a language, it's a blanket pejorative, and it doesn't reflect well on the author's credibility.
Re: Show HN: Algorithm Cookbook in Rust
#17This is great. I am curious if anyone else knows of a similar cookbook for Golang.
I have implemented quite a few algorithms and data structures for fun here [1]. It's not authoritarive by any means, and not everything is in Go (there's also some Rust, Swift, TS and JS), but maybe a few things could turn up useful.
Re: Show HN: Algorithm Cookbook in Rust
#18Earlier quoted context omitted.
Agreed. I once tried to submit a small snippet I found on stackoverflow to an open source project. Stackoverflow user content is licensed under creative commons, cc-by-sa (see https://stackoverflow.blog/2009/06/25/attribution-required/ ). I included attribution, but it was rejected. I totally understand why. CC0 is much preferred in this case.
FYI, newer Stack Overflow code is licensed under an MIT license with a link in code comments serving as attribution. See https://meta.stackexchange.com/questions/272956/a-new-code-l...
Looking at that link I don't think it was implemented. The footers on stack overflow pages still indicate cc-by-sa.
Re: Show HN: Algorithm Cookbook in Rust
#19Offtopic/meta. I'm wondering about a technology that allows us to NOT re-implement an algorithm cookbook every time a new language shows up.