@Kuba Python provides both of these forms in recent versions and I know a lot of people really like the second
I still stick with the first because it was the original and the way I learned it, but I'll probably move to the second so as to not become an old fogey
Of course since python is partially compile there's actually a performance benefit to the second
Ah sorry misunderstood what you were getting at. You're talking about a set of pre-defined additions?
@b3m2a1 I prefer the second one because: - more general you can expose NL[n_]:=StringRepeat["\n", n] etc - Many backticks make templates unreadable - Named slots break automatic numbering of slots, e.g. if we remove `otherField` then it's slot will be counted as the second one.
They highlight operators in red and they don't care if a symbol is built-in or user-defined. They highlight option symbols differently which makes no sense.
Here is the same snipped on SE
The colors for SE where defined a long time ago and I don't remember if we supplied the css for that.
> Can we do anything about that?
No, most definitely not. The SE company is impossible to work with. After the disaster with our header image which took a year to switch after we provided everything ourselves, I'm not up to putting any of my free-time in and hoping to get a feature request done. Sorry.
@halirutan well, you see, there are issues with GH. I was rather thinking about working with GH rather than SE. To improve GH highlighter. But I am not sure what needs to be arranged, what is the role of your WolframLanguage-Google-Prettify etc.
GH highlighting is so bad that I think I prefer a plain code block
The symbols t1 and t2 are used to prevent updates to one tooltip from affecting the other (as would happen with downvalues). The idea is to trigger a replacement of the entire tooltipped object once the tooltip is requested the first time (via the Dynamic in the outer Tooltip). The problem is that this requires re-typesetting the tooltipped expression itself as well. Unfortunately, I have not found any other way to only evaluate the tooltip once when first needed. Any ideas?