3 ms·

Same reason why you see so many posts of "(thing) for Rust", "(other thing) in Go", etc. Some people are interested by the thing, others will be interested by

Same reason why you see so many posts of "(thing) for Rust", "(other thing) in Go", etc. Some people are interested by the thing, others will be interested by what it was implemented with.

wyldfire 9y ago
> others will be interested by what it was implemented with Agreed but I think the point is regarding which "with". Let's say your hot-dog-not-hot-dog project leverages glibc, linux, json, LLVM, scipy, pandas, OpenCV. When you write a title to feature your project on HN or similar, should you pick "hot-dog-not-hot-dog in OpenCV" or "hot-dog-not-hot-dog using glibc"? Yes, it's true that you couldn't have gotten it done at all w/o a libc. But that's probably not what you should lead with.