I don't have Studies to back this up, but anecdotally:

* Playing fine violins takes a lot of practice with the specific instrument to begin to unlock its potential. I was scratching the surface after a couple months; people with longer-term loans say it takes years.

* Strads in particular are surprisingly hard to make sound good at first. I'd say there was a good two weeks where I sounded better on my $2500 Chinese-made violin than I did on the multi-million dollar Strad. (del Gesus sound great out of the box. This is widely agreed upon but I don't know why it is)

* In terms of pure craftsmanship there are many contemporary makers who are working as well as Strad and del Gesu, and I don't place much stock in them having access to uniquely good wood or magic varnish or anything like that.

* However, for poorly-understood reasons the act of playing a violin "opens up" the sound and also gives you access to more and more tone colors. A 300-year-old violin that's been played a lot will therefore have a much bigger tonal palette than a contemporary violin, even if any individual tone color isn't strictly better than the tone of a contemporary violin.

* The corollary is that in the year 2300 I believe top-end contemporary instruments will be as good as Strads are now.

* If you just thought "what if we simulate the vibrations of playing on new instruments to expedite their aging", you're not the first! Some luthiers hook new instruments up to a specialized amplifier and effectively play music through the violin for a couple weeks before selling it. A lot of people claim this helps a lot, but I don't have first-hand experience of it.

HWIAs are convenient, but they do confuse the issue.

If I release a new library tomorrow, do I not need to write docs for it?

Would you please expand on this?

Another neat thing was that there used to be a full-time SDET who spent a lot of time writing Cypress reproductions for known bugs. When you picked up the bug, you could un-skip the test that was right there waiting for you.

All that said, of course it's far from perfect!

0: https://github.com/metabase/metabase/ Backend unit tests are in test/, Frontend unit tests are in frontend/test, end-to-end tests (Cypress) are in e2e.

> if the new Scottish Languages Bill is to succeed in securing the Gaelic and Scots languages in the face of immense pressures, then the needs of the communities speaking those languages must be at the heart of it

Gaelic advances in the modern era include:

* the foundation of Sabhal Mòr Ostaig, a Gaelic-medium university

* the rise of Gaelic-medium education as an option for primary and secondary school

* Gaelic-language radio and TV stations

* The launch, a few years ago, of SpeakGaelic (https://speakgaelic.scot/) with loads of learning materials (mentioned in the OP).

Problems include the continued dilution of Gaelic-speaking communities (native speakers either die or move somewhere with better job prospects; non-speakers buy up holiday homes or Airbnb investment vehicles in the area) and the perception that career prospects are much better for people educated in English (perhaps with a bit of French or similar on the side) than those educated in Gaelic.

1. Search (across the application)

2. Find on page

3. Adjust zoom

I then moved to Scotland, where exactly zero people have defaulted to Mc instead of Mac. However, the computer systems of both the NHS and the University of Edinburgh apparently don't store the case of strings and reconstruct the capitalization after the fact. Both systems list me as MacDonald and there's nothing I can do about it.

I'm relatively okay with this—before computers McDonald, MacDonald, Macdonald, and M'Donald were all functionally equivalent. But now I do worry about the implications of having official documents with variant spellings