DataFrames.jl
seaborn
DataFrames.jl | seaborn | |
---|---|---|
9 | 77 | |
1,696 | 11,969 | |
1.0% | - | |
7.0 | 8.4 | |
17 days ago | 11 days ago | |
Julia | Python | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DataFrames.jl
-
Julia's latency: Past, present and future
I don't think we've seen the final state of it though. v1.9 really gives people the proper tools for solving latency problems. Before, invalidations hurt a little, but it was also kind of a wash because LLVM code didn't precompile, so you could spend time setting up a Snoopprecompile and fix some invalidations and end up LLVM bound saving 1 second out of 20. But with package images it's almost always better to fix precompilation. The only thing hampering time much now is the `using` time went up, but as mentioned in the Reddit post there's a lot of ideas for what to do there. The other thing is package extensions, which cut down the amount of code to load. There's tons of PRs floating around the ecosystem turning things into extensions, and thus cutting down the overall code that is actually ran and loaded.
This means that in a few months, people will start to see some major tangible benefits from following the compilation improvement practices laid out here and https://sciml.ai/news/2022/09/21/compile_time/. I think then you'll have a lot more people start to take all of these new tools seriously and it will be standard to incorporate them into packages. Right now they are still kind of niche things for packages with known TTFX problems, but I think come v1.9 you'll see every major package use all of these methods.
> Different packages are affected differently
I think this is one of the pieces that's effected by this. I don't think "Julia has become optimised for running Plots.jl" is quite correct. Julia's compilation and runtime is much more optimized for well-inferred code, which Plots.jl is not. However, the compiler developers have been using Plots.jl as a test case for all of these new tools, and therefore its SnoopPrecompile and invalidations have gotten some dramatic improvements because those required ecosystem changes I mentioned are being done by the compiler team for this specific package. Plots.jl had things like precompilation snooping way back before there was even a package for it, the earliest I know of was around v1.0. Meanwhile, DataFrames.jl only setup its precompilation snooping 7 months ago (https://github.com/JuliaData/DataFrames.jl/pull/3182), which I would presume was just in time for the v1.8 mark on your plot and is one of the big reasons for having a sudden drop (which continues into v1.9 because of package images).
What I mean to say then is that, I think all packages will get the improvements we've seen from Plots.jl, but package authors will need to update their packages in order for that to happen. Some packages have already done this, many have not.
-
IJulia: The Julia Notebook
IJulia also supports viewing and manipulating tables. To create a table, first install the DataFrames.jl package by running the following command in a new cell:
-
Machine learning with Julia - Solve Titanic competition on Kaggle and deploy trained AI model as a web service
It were just a few percents of all possible manipulations that you can do with data using DataFrames.jl library. Read more about it in the documentation.
-
Unleashing the Power of Julia: Top 5 Must-Have Packages
DataFrames.jl
-
Automate the boring stuff with Julia?
DataFrames.jl and XLSX.jl for JSON, CSV, and XLSX files
- What would it take to recreate dplyr in Python?
- Dataframes.jl version 1.0: Tools for working with tabular data in Julia
-
Teaching Python
Julia also has the CSV.jl library for reading/writing csv files, the DataFrames.jl library for manipulating data like pandas, and Images.jl for image processing/analysis. However, since Julia is so much newer than Python, the Julia libraries are almost never as feature rich as their Python counterparts.
-
Polars (Rust DataFrame library) join algorithm fastest in db-benchmark
Looks like it's single threaded according to this open issue: https://github.com/JuliaData/DataFrames.jl/issues/2626
seaborn
- "No" is not an actionable error message
-
Apache Superset
If you are doing data analysis I don't think any of the 3 pieces of software you mentioned are going to be that helpful.
I see these products as tools for data visualization and reporting i.e. presenting prepared datasets to users in a visually appealing way. They aren't as well suited for serious analytics.
I can't comment on Superset or Tableau but I am familiar with Power BI (it has been rolled out across my org), the type of statistics you can do with it are fairly rudimentary. If you need to do any thing beyond summarizing (counts, averages, min, max etc). It is not particularly easy.
For data analysis I use SAS or R. This software allows you do things like multivariate regression, timeseries forecasting, PCA, Cluster analysis etc. There is also plotting capability.
Both these products are kind of old school, I've been using them since early 2000's, the "new school" seems to be Python. Pretty much all the recent data science people in my organization use Python. Particularly Pandas and libraries like Seaborn (https://seaborn.pydata.org/).
The "power" users of Power BI in my organization tend to be finance/HR people for use cases like drill down into cost figures or Interactively presenting KPI's and other headline figures to management things like that.
-
Seaborn bug responsible for finding of declining disruptiveness in science
It's referring to the seaborn library (https://seaborn.pydata.org/), a Python library for data visualization (built on top of matplotlib).
-
Why Pandas feels clunky when coming from R
While it’s not perfect and it’s not ggplot2, Seaborn is definitely a big improvement over bare matplotlib. You can still use matplotlib to modify the plots it spits out if you want to but the defaults are pretty good most of the time.
https://seaborn.pydata.org/
-
Releasing The Force Of Machine Learning: A Novice’s Guide 😃
Seaborn: A statistical data visualization library based on Matplotlib, enhancing the aesthetics and visual appeal of statistical graphics.
-
Seven Python Projects to Elevate Your Coding Skills
Matplotlib Seaborn Example data sets
-
Mastering Matplotlib: A Step-by-Step Tutorial for Beginners
Seaborn - Statistical data visualization using Matplotlib.
-
Top 10 growing data visualization libraries in Python in 2023
Github: https://github.com/mwaskom/seaborn
-
Best Portfolio Projects for Data Science
Seaborn Documentation
-
[OC] Nationwide Public Transit Ridership is down 30% from pre-lockdown levels; San Francisco's BART ridership is down almost 70%
You've done a great job presenting this. Maybe you already know, but seaborne is an extension of matplotlib that makes it pretty easy to "beautify" matplotlib charts
What are some alternatives?
polars - Dataframes powered by a multithreaded, vectorized query engine, written in Rust
bokeh - Interactive Data Visualization in the browser, from Python
Tables.jl - An interface for tables in Julia
Altair - Declarative statistical visualization library for Python
DataFramesMeta.jl - Metaprogramming tools for DataFrames
plotly - The interactive graphing library for Python :sparkles: This project now includes Plotly Express!
Plots.jl - Powerful convenience for Julia visualizations and data analysis
ggplot - ggplot port for python
MPI.jl - MPI wrappers for Julia
plotnine - A Grammar of Graphics for Python
Curry.jl - Currying for Julia
matplotlib - matplotlib: plotting with Python