Andrei Kashcha

Results 132 comments of Andrei Kashcha

:+1: Maybe a smaller feature would be to crawl every issue in a repo?

Not sure I understand your question. Here is the discussion of the main design decisions: https://github.com/anvaka/fieldplay#how-this-project-works And in this section you can find more about building it locally: https://github.com/anvaka/fieldplay#local-development

Yup, looks like it's stale now. @vdaubry any chance you can refresh it?

Thank you! I think having ability to parse actual code and categorize each line is a very powerful idea. However, that would be too expensive/time consuming for me to do....

That is awesome! Thanks for sharing! Have you considered adding your data sets into https://github.com/caesar0301/awesome-public-datasets ?

Absolutely! I added sql (all files with `.sql` extension): https://anvaka.github.io/common-words/#?lang=sql And rust (all files with `.rs` extension): https://anvaka.github.io/common-words/#?lang=rust What would be the most accurate file extension for Clojure/Lisp/Kotlin/CMake?

@rmflight I had R before. Unfortunately visualizations were not usable for R - they were made mostly from numbers. That's because I can only differentiate languages by file extension. As...

Added: * [Lisp](https://anvaka.github.io/common-words/#?lang=lisp) * [Clojure](https://anvaka.github.io/common-words/#?lang=clj) * [Kotlin](https://anvaka.github.io/common-words/#?lang=kt) * [CMake](https://anvaka.github.io/common-words/#?lang=cmake) * [Swift](https://anvaka.github.io/common-words/#?lang=swift) Please let me know if something doesn't make sense or is missing

Added both: * [Haskel](https://anvaka.github.io/common-words/#?lang=hs) (only .hs and .hsc extensions, as described by [linguist](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml#L1736-L1747)). * [Elixir](https://anvaka.github.io/common-words/#?lang=ex)

@ZevEisenberg yes, unfortunately I don't have anything advanced yet. I guess one could use user defined function which would classify source code text more accurately... For now I'm just considering...