How do you feel about Julia Observer?

question

#1

As we’re getting to the two year mark of JuliaObserver, I thought it was a good time to check in w/ you guys.

Currently, the website has ~1k weekly users, with an average session time of 3-4 minutes.


If you could, please fill out the following poll. All comments are welcome, so be as honest as you want.

  • I don’t use it
  • I use it but wish it was better
  • I use it and think it’s good enough

0 voters


// hope you're all having a good holidays! here's to another lap around the sun 🥂

The State of the Julia Ecosystem
#2

I like Julia Observer, but i kind of miss pkg.julialang.org/pulse.html

I liked the first graph reporting number of packages per version and the 14-Days stars change. These may be quite easy to add to julai observer though.

I also feel like julia observers design is more suitable for big screens or maybe touchscreens. I’m on a 14 inch screen and would like a higher information density.


#3

I like the Observer and it’s definitively a very useful service. It also got an extra responsibility when got linked directly from Julia home page. So the information it displays should be the most accurate as possible but it turns out that it’s difficult to make corrections. I’ve opened an issue some months ago to fix a bit of that info (a package classification issue) but nothing happened. I understand that it relies on julia.jl to get the info (where I also submitted a PR) but the fact is, no update took place.

In summary, my point is that it should be easier to improve the quality of the information displayed in the Observer


#4

I like the observer. I wish either the observer or julialang/pkg would attempt some editorial guidance. See https://discourse.julialang.org/t/pkg-ecosystem-learning-from-others-mistakes/18028/51 for a long discussion.

What it boils down to is some human-maintained subset of “high quality” packages, even if this ends up as a super subjective and unprincipled directors cut.


#5

I am unsure about its usefulness. I am missing a very simple but large(huge) page, with every package available/registered just to be able to use the browsers text search function. This fancy javascript auto line adding when scrolling down does not give any better usability (it’s by the way annoying in discorse too). And I guess it is not the best for being indexed by search engines. So this is an example for responsiveness without benefit. There are still double entries in the categories (e.g. Statistics, i didn’t check for others).
So all in all I think it should be less mobile/responsive/fancy and more simple with “higher information density”, to quote above.


#6

What I like about it especially is the reverse dependency list, that is, for the current package, show where it is used. This information is not so obvious from browsing raw GitHub.


#7

When searching for packages a scroll down box is presented with packages meeting the search requirements

  • this list goes away too fast if you are trying to read a long list
  • if the list extends below the screen bottom, items at the bottom cannot be reached

Other than these two nits JO meets my needs.


#8

I love it! I like learning a package I’m new to by finding other packages that depend on it and looking at their implementation. Observer is great for this. It does get a bit slow in my browser but I’ve also been known to get frustrated with how slow my microwave is


#9

JuliaObserver is very useful, it’s essential to have a view of packages by category and sorted by popularity (else you get lost given how many packages there are, including unmaintained ones). Though categories are not always right, and it’s a bit inconvenient to rely on Julia.jl for that. I was thinking you could extract the GitHub tags too? That way maintainers can directly control how their package is classified.