I want a pinhole camera in my monitor so I can make eye contact with the other side when I'm looking at them. That's the biggest lacking feature to me on pc video conferencing.
Having worked with Intel fab from inside Intel design and with TSMC at a different company, Intel fab would do very well to standardize and work on supporting their customers. If they decoupled and provided better processes, it would greatly improve the experience for those working with the fab. As it is right now, the Intel fab has always been the tail that wags the dog. They've carried Intel off and on for so many years that if design wants something and the fab pushes back, well design gets to pound sand and find some workaround to the fab's processes.
The pronunciation of "Gloucester" (gloster) and "Leicester" (lester) follow a similar scheme for the "-cester" bit which leads to "Worcester" being pronounced "wooster", but Worcestershire sauce is often pronounced "wooster sauce" which doesn't make much sense.
Apparently, Frome in Somerset is one of the hardest place names to pronounce in England, though it certainly doesn't compare to some Welsh towns. (I say it as "froom")
I think the sauce is either Worcestershire Sauce, or Worcester Sauce, either is acceptable.
Worcestershire and Worcester follow the same patter as Gloucestershire/Gloucester, Leicestershire/Leicester and (Towcestershire doesn't exist)/Towcester. Towcester, incidentally, being the same pronunciation as "toaster".
The one that annoys me is Cirencester, which is usually "sai-ren-ses-ta", and only occasionally "sai-ren-ster".
I like the Northamptonshire village of Cogenhoe, which is obviously pronounced cook-no.
It sits on the River Nene, which is pronounced Neen or Nen depending on which bit of Northamptonshire you live in (Northamptonshire is not very big...)
It amuses me when english words are pronounced differently to make them seem posher. We have a nearby town called Yate (rhymes with gate), but the posh version rhymes with latte.
"That's just incorrect. It's pronounced "wooster-shuh". The double-O is short, as in "book". Worcestershire Sauce is sometimes simply called "woosters", as in "a dash of woosters".
> Frome in Somerset is one of the hardest place names to pronounce
Hardly. It's pronounced "froom". That's not so hard.
>There’s a town in Massachusetts called Worcester, pronounced something like Wooster/Woostah/Woostuh.
And there's a Gloucester[0] (pronounced 'Gloster' or, more likely in MA 'Glostah') there as well. And there's one[1] in Virgnia too, (Wikipedia says it's pronounced 'Gloster', but I don't know the VA accent well enough to know if that's locally correct).
There are other similar place names around the US, mostly on the eastern seaboard, for obvious reasons, as well.
The pronunciation is what it is. The orthography is the problem.
(Many words place names long pre-date any kind of attempt to regularize English spelling, and in any case come from fusions of Brythonic, Norman, Roman, Norwegian etc languages. This is why it's difficult to predict the pronunciation of one word from the spelling of another.)
Maybe, but 'we can't provide logical rules for names acquired over a millennium ago' seems like a poor reason to say 'therefore we shouldn't apply consistent rules to recent conventions'.
Someone asked about physic ... well people used to use physick in [late medieval?] British English... but that's for what we might call medicine now.
Oh, defending the pronounciation is easy, because the problem is not with the pronounciation at all -- it's all about English language spelling not keeping pace with the changes with the pronounciation.
You start with a pinch of dyslexia and end with a bit of a lisp. Pretty straight forward when you imagine what it would sound like in a game of telephone between 10 5 year olds.
I thinks it's possible with the access we both have to the other country's media via Netflix, prime, Hulu, et c., that our accents re-merge. When I was a kid, British accents were a little harder and Scottish accents were impossible, but after 15 years of Netflix, I don't even notice British accents anymore and Scottish accents are noticeable, but understandable.
When I was a kid, no way could I understand a Geordie accent. I was raised with a RP accent, but I lived in Liverpool; I could understand ordinary scouse fine.
But my mates would sometimes launch into a very broad scouse accent to tease me; I could only just understand that.
Things have changed. Nobody nowadays speaks Geordie with the very broad accent that I couldn't understand as a kid.
I have a fairly typical AMD 3600 cpu and 5700xt with a mid tier common mobo. All stuff that's super consumer and a few years old now. And I still encounter tons of random issues. And updates that break stuff that used to work.
Sure, its a lot worse for brand new laptops. But it never entirely works to the level you'd get from macOS.
Well, macos only has to support a low-digit number of sanctioned configs, so that’s much easier. For whatever it worth, I found linux’s device support the very best — while windows does likely have some random binary for a given device laying around the internet, it is often borderline malware, and may not work too well on a newer windows version (though credit where its due, windows’ backwards compatibility is phenomenal). Linux has a vast amount of supported devices out of the box, no “windows is looking for a solution”.
Me too! Was astounded by the price of a standard solution and said to myself, "I can do that cheaper [ assuming my time is worth less than minimum wage.]" Still works, 7 years after install.
