New name for Mathematica

[DecimalTurn]

There was a PR made recently on the Linguist repo. It changes the official name of the Mathematica language to Wolfram Language.

This won't cause any problems for languish at the moment since that merged PR won't affect GitHub until the next Linguist release, but might as well make the adjustment in advance. Is that something that can be solved simply by adding an entry to canonicalNames ?

languish/scripts/src/merge.ts

Lines 11 to 28 in a90b1e1

	let canonicalNames = {
	"AL Code": "AL",
	BlitzBasic: "BlitzMax",
	"Classic ASP": "ASP",
	"Csound Document": "Csound",
	"Csound Score": "Csound",
	FORTRAN: "Fortran",
	"Graphviz (DOT)": "DOT",
	Matlab: "MATLAB",
	Nimrod: "Nim",
	PAWN: "Pawn",
	Perl6: "Raku",
	"Perl 6": "Raku",
	REALbasic: "Xojo",
	Sass: "Sass/SCSS",
	SCSS: "Sass/SCSS",
	VimL: "Vim script",
	} as { [name: string]: string };

[tjpalmer]

Thanks for the notice!

I'd actually have to review things since I haven't been in the code for a while, but canonicalNames might be the right place.

Meanwhile, I never updated for Q3 because the data sources were being less reliable than usual, both for GitHub and for Stack Overflow. But maybe I should go back and try again.

[tjpalmer]

And if things are working again (just so much bother to deal with them, blech), I likely should look into the Wolfram renaming before finalizing Q3.

[DecimalTurn]

Meanwhile, I never updated for Q3 because the data sources were being less reliable than usual, both for GitHub and for Stack Overflow.

For GitHub, is it still related to potential bot activities? I noticed you removed issues from the default view in a40a7ef for that reason, but I'm assuming stars might also be affected.

[tjpalmer]

Meanwhile, I never updated for Q3 because the data sources were being less reliable than usual, both for GitHub and for Stack Overflow.

For GitHub, is it still related to potential bot activities?

No, it's just their service being slower and less reliable than usual. For bots, I should actually look into seeing the user on the events. Bots often label themselves as bots, so it might be possible to weed out much of their activity.

[DecimalTurn]

Ah, I see! I also just went to check on GitHut 2.0 and saw your comments about the sluggish queries there as well.

This makes me think that perhaps instead of waiting to run queries every quarter, it might be better to spread them out. Have you also considered running the queries via GitHub Actions on schedule? I used that approach for https://github.com/DecimalTurn/Visual-Basic-Data and it worked relatively well.

[tjpalmer]

Ongoing queries might work out. I get events from bigquery but "primary language" for each repo from the github api. I could be querying both in an ongoing fashion. If everything were just on bigquery, that would be awesome, though.

The stackoverflow server also was failing on me when I was trying it after Q3. Maybe that also could go on a daily basis. But that would also be better if they just dumped data into a table on bigquery.

The sad part about all this is that my interest in maintaining is waning at the same time they're getting flakier. So it's hard to bring up the motivation to re-engineer things.

[DecimalTurn]

Yeah, that sucks for sure. I'm not sure I can be of much help on the bigquery side of things as I don't have experience with that, but if there's something regarding the API that I can do to help, let me know.

However, looking at the issues from the gharchive.org repo seems to indicate that there is some problems with the API data as well, so we might have to wait for GitHub to get it together...

[alecgargett]

The sad part about all this is that my interest in maintaining is waning at the same time they're getting flakier. So it's hard to bring up the motivation to re-engineer things.

That is sad. Thank you for all the work you've done so far. I've really enjoyed this app. I haven't found anything else out there as good as this for getting a sense of the overall trends over time.