1. 7

    Original blog post and slides.

    1. 1

      Thanks, highly recommend the slides.

    1. 1

      Seems that Astropy did receive some funding since this article has been published: https://numfocus.org/blog/astropy-receives-900k-grant-from-moore-foundation

      1. 1

        This didn’t end up having much to do with JavaScript, which surprised me.

        1. 1

          Yeah, their title is kind of misleading, it’s more about programming in general than JavaScript. That’s why I didn’t put the JavaScript tag ;)

        1. 1

          Not loading for me.

          1. 1

            Strange, works fine for me :-$

          1. 6

            Shouldn’t the URL point to the Charts.css website instead of Github repo?

            1. 1

              probably a good call. I’ll update it

              1. 1

                I lied… it won’t let me update the url

            1. 3

              I would have loved to see a Julia section.

              1. 1

                The unoptimised version would look a lot like the python version, but probably perform better if you omitted compilation time.

                You’d use a Dict, eachline, and split. The main performance issues would probably be unicode-aware lowercasing and hashing each word twice in the inner loop (once to check if it’s in the dict, once to set a new value. We might eventually get an in-place update interface for dicts to avoid this duplication, in the meantime you can use some internal funcs or use a third party package).

                Unlike the python version, if you need Moar Performance you can efficiently operate at the byte level and use any of the tricks from the C or Rust implementations.

                1. 1

                  I suppose it will be dominated by startup time and IO. Although I am curious to see if the same issues would arise in Julia as well, splitting of words and slowdowns due to maps.