Dont take this is flippant or lame 'AI BOI' etc...

But what if you had a GPT summarize the error messages and tell IT to look for certain things...

Why not train an llm on all your error messages and fixes?

I know that sounds sophmoric, but its an honest Q.

---

I worked at one of the first VOIP startup in the late 90s - before cisco had entered the game...

We had all our server error logs printed on a LINE PRINTER in the server room...

(This was on Mission Street above the Dennys - with PISS alley behind the building)

My CTO (I was IT Mr. Mgr at the time) - required that I went through the error logs every morning with a HIGHLIGHTER to read each error message for hacking attempts...

You have no idea how life-sucking that part of my job was....

If you have specific issues around error messages and tracebacks please feel free to let me know directly or to file issues on Github. We really do care about the legibility of errors and tracebacks and me and my team have put a lot of effort into them in the last few years. But there's always room to do better and I'd love to know where the pain points are.

(The intersection of tidyverse and shiny tracbacks are a known pain point that's hard to resolve. Unfortunately shiny and tidyverse did a bunch of parallel work that took us in slightly different directions and now it's hard to re-align.)

One thing we are missing is a guide to reading traceback for newer users. Often experts can get a good sense of where the problem is, but we've failed to teach newer users how to get the most value from a traceback.

There's clearly been a ton of progress in this area; the only issue is that feature development is even faster :) I'll keep an eye out for specific issues that seem helpful to raise.

The biggest one I have right now is a little niche, but probably useful to address. Moderately complex dbplyr pipelines on wide tables have a tendency to generate very long queries, and if there's an error, the generated SQL returned tends to overflow some text or line limit allotted to show the error at the command prompt. My workaround is to use sink() to dump the error to a file, which is a little painful as the sink() API and documentation are not the most straightforward or intuitive. (Hmm, I wonder if a withr wrapper would help me make something simpler to use...)

Hmmmm, I think that's something we could probably help with in dbplyr by providing something like `last_sql()` that would return the most recent SQL sent to the database. (By analogy to ggplot2::last_plot() and httr2::last_request()/last_response()).

I filed an issue so I don't forget about this: https://github.com/tidyverse/dbplyr/issues/1471

Why Polars and not Dask?

> My fondest hope is that in the coming decades there arises a new, thoughtfully designed language with the Lispy flexibility of R, but also optional type safety and static analysis affordances.

I think many of us saw Julia as the successor to R. Unfortunately, the package ecosystem---one of R's strongest points---still has a long way to go.

I was excited about Julia too but it now seems to be a relatively niche HPC language. It's about saving CPU time more than user time.

My sniff test for a successor language to R is whether it can replicate the tidyverse API with 100% fidelity. The API is already optimal for tabular data analysis, especially the dplyr core. It can be thought of as a specification for other languages to implement.

There is a great deal about how R works that is negotiable. But if the language can't implement dplyr to spec, or somehow doesn't "want to", it's not the language for the audience served by the tidyverse.

Follow-up: I did a little legwork and found some Julia folks who were also inspired to implement tidyverse as faithfully as possible: https://github.com/TidierOrg

Here's how dplyr-style chains look in their system:

  using TidierData
  using RDatasets

  movies = dataset("ggplot2", "movies");

  @chain movies begin
      @mutate(Budget = Budget / 1_000_000)
      @filter(Budget >= mean(skipmissing(Budget)))
      @select(Title, Budget)
      @slice(1:5)
  end

Not a character-for-character match to dplyr, but gets much closer than most other attempts!

I love this framing :)