sometimes I think SO regrets the SE sites and is trying to kill them by not supporting them...
meta.stackexchange.com/a/353990/463832 this meta answer definitely deserving of upvotes. if SO commit to rolling out new versions of syntax highlighting on a regular basis then that would be a huge upgrade for us (new symbols need highlighting and it certainly seemed like a big hassle to get that done before...)
@CarlLange if you look at the official demo, too, it looks like they're missing highlighting for # and stuff (and that's even in their demo example!) highlightjs.org/static/demo
If I take a look at what they seem to be calling that code, it thinks the first is delphi and the second is rust. It doesn't matter if I use Mathematica, mathematica, mma, or wl, though, so clearly if highlight.js gets a language name it doesn't understand, it just tries to infer a different one
Here's an annoying thing I didn't know about. Using a block like this doesn't specify a language on SE
```mathematica
...
```
instead you need to use lang-mathematica for it to use it
but their version of highlight.js doesn't support Mathematica, which I found by checking the actual JS they served me, which has a bunch of blocks like some.obj.registerLanguage("...", ...) but neither Mathematica, mma, nor wl are in those keywords, despite the fact that Mathematica has been in the highlight.js GitHub source for over a year
When hightlight.js hits us in like a week, we'll probably need to make a fuss on Meta about it...
What to do if highlight.js supports a language but Stack Exchange doesn't?
There's an entire Mathematica StackExchange, and so Mathematica syntax highlight is clearly very important to us. But when I did some digging to find the highlight.js bundle that SE seems to be serving, Mathematica isn't i...
ResourceFunction["SimulateAnimalVision"]["Human:Deuteranopia", img] makes you doubt the usefulness of the resource function repo....It would be nice to have a filter to test for color-blind friendliness in Mathematica.
@CarlLange Thanks. I'm not an expert on colorblindness, and what I think I know is built from consistency in what I find on the web, esp. from organizations dedicated to it or to accessibility. While some results of the resource function are closer , some seem farther away. Sometimes I wonder whether what I think I know is flawed.
@MichaelE2 Yeah, I know very little about it myself but I find it mildly odd that the method used in the resource function is simply to remove an rgb component
@CarlLange Yeah. In my case, I'm interested in making teaching materials that are accessible to actual color-blind students, so there's a real benefit to doing it right.
I haven't had much cause to use it but I have been pretty interested in WL's color theory functionality, so I'm pretty sure it's possible to create a reasonably sophisticated model with just the built-ins
There's a nonexpert like me on Community who did something (community.wolfram.com/groups/-/m/t/1278303). It's much closer than the resource function, but not in complete agreement. Well, even some of the reference filters I used for comparison don't agree perfectly.
I'm finally switching from Mac to Pop!_OS (and getting a nice 12-core processor in the deal). I'm a bit nervous that the Mathematica experience is going to be much worse on Linux since SW doesn't seem to ever use Linux (and that's how you know it'll work OK, of course)
I guess that's not true, I've seen him run remote kernels that are definitely on Linux. I'm more worried about the frontend
has anyone had a need for a AssociationSelect (like AssociationMap) to wrap up the idiom Association[Select[Normal[assoc1], test1[#[[1]]] && test2[#[[2]]] &]] ?
@C.E. Yeah, the mathematica file is 95KB uncompressed, so that about holds up. It's basically just a big ol list of symbols so I wonder just how much it could be improved by