It should more properly be written as dæmon. The æ ("ash") character is usually pronounced more like "ee", as in encyclopædia. I've never heard anyone say "encycloPAYdia" :-)
Fascinating! This is why I stick with nice, clean structural linguistics, this applied stuff gets sticky. I just confirmed on Youtube that the (some?) British people do indeed pronounce "Aesthetic" as "ah-stet-ic" not "ee-stet-ic", and upon diving a bit, it seems that the rule is "don't ask for a rule, you fool! It's 'e' now except for when it isn't." Thanks for the interesting tidbit!
The letter æ was used in Old English to represent the vowel that's pronounced in Modern English ash, fan, happy, and last: /æ/. Mostly we now spell that vowel with the letter a, because of the Great Vowel Shift.
When æ appears in writing Modern English, it's meant to be a typographic variant of ae, and is pronounced the same as that sequence of vowel letters would be. So Encyclopaedia or Encyclopædia, no difference.
Highly recommend the protracted arguments in the comments, that's a wonderfully pedantic StackExchange. Big shoutout to someone in 2012 defining "NLP" as an unusual word -- how the world has changed! It's only a matter of time before they open an AP/IB course in NLP...
Hmm, I'm a Californian and I pronounce daemon as demon, understanding the first vowel as the same vowel as for Aesop. Indistinguishable from the vowel in "beam" and "niece".
But I pronounce the first vowel in aesthetic differently. For me, it's somewhat in between the vowels in "bed" and "bad" but closer to the former.
…TIL how to pronounce “Aesop”! Thanks for saving me eventual embarrassment - now I know why other people don’t mix up Aesop Rock and ASAP Rocky!
As a fellow Californian, I’d say we have authority anyway - I was taught in school that Ohio has the least specialized dialect, but that’s based on newscasters and such. The 21st century is the Californian century!
…that is, assuming Brussels’ English is out of the running, I suppose ;)
"Aesthetic" gets even stickier! In the UK I tend to more commonly hear it pronounced as "es-thetic".
The Great Vowel Shift indeed makes written English much more confusing than it perhaps should be. English is already a messy hodge-podge of a language, then our writing system started to get standardised (or standardized, if you're American!) right as pronunciation started to change, leading to the written version of words suddenly no longer being anything like the pronunciation.
The letter "æ" as used in Old English does indeed correspond to /æ/, but we don't use that letter (or even digraph) for this purpose anymore. In all the words where it is still occasionally used, it corresponds not to Old English "æ", but to Latin "ae", which is [ae̯].
The original pronunciation of ae/æ in words originating from Latin or Greek is basically like "I". As usual, English molded it into something else in many cases, which is why we write "demon" these days. But if you insist of "daemon", then it really ought to be pronounced like the original Greek δαίμων.
Yes. Daemon is just the archaic spelling of demon. The ae is a vowel sound that didn't survive to modern times. The word was NEVER pronounced "damon." To my knowledge.
Since the introduction of APFS I've taken to creating a new APFS volume formatted as case-sensitive, and put my git repositories there.
This has mostly been useful for working on shared repositories where, say, a Linux user (or other user on a case-sensitive filesystem) pushes two branches, say `feature/foo` and `feature/Foo` which works fine for them, but on a case-insensitive filesystem, git gets very upset.
Managed Kubernetes exists because Kubernetes is so mind-bendingly complex.
Nomad, on the other hand, is pretty simple and easy to run, and a single binary. There's probably no benefit to having a managed offering.
That said, I wouldn't be surprised if HashiCorp add Nomad to HashiCorp Cloud Platform, which currently lets you deploy Consul and Vault to cloud providers via their system.
Managed Kubernetes exists for the same reason managed PostgreSQL, MySQL, Redis, ElasticSearch so on and so forth exist.
Which is to say it's useful enough to a large amount of people to make it viable as a product offering. Nomad would fail as a managed offering here like like Deis, Flynn, Convox and probably 100 other container management platforms that came before.
As a niche tool to manage sub-1000 boxen it's probably ok. But k8s has won the greater war.
Disclaimer: Worked on Flynn, still run it for my own personal stuff by $DAY_JOB is all k8s.
You got that sub-1000 boxen wrong. Nomad is usually employed where the infrastructure is huge. IMO, K8s is driven by hype and marketing, not by technical merit.
Your enumeration of the managed things is very particular, in that it includes only stores. There's a reason for things that have keeping persistent state as their reason to exist are managed: reliably maintaining persistent state in the cloud is a lot more difficult than reliably orchestrating things that just have to run.
If public cloud providers would offer Nomad, then it would only be a question of time until managed Nomad would be a thing.
Managed _something_ does not mean it's "mind-bendingly complex", but rather that people don't want to take care about it and focus on their own stuff like building applications.
Salt states can very quickly/easily become unweildy as, unlike Ansibble, you can throw Jinja2 everywhere. It becomes far more tempting to create multiple states with a Jinja2 loop, or worse, macros, and before you know it you have a huge mess of what I like to call "spaghetti Jinja".
I am using Firefox with profiles for years (maybe even decade). Run Firefox from command line with -P flag to start profile manager or -p <profile> to run particular profile. Rest is matter of shortcut/custom icons to launch.
I was going to say this. Also I havent used FF profiles in a minute but the dialog that lets you select a profile has a checkbox to auto select that profile or something. If you unselect that it should always prompt you about profile. I wish Firefox would make this UI as easy as it is in Chrome. I refuse to login on Chrome to Google.
I have a bookmark to "about:profiles" on my main toolbar (not my bookmark toolbar, I hide that) in Firefox to launch my Work profile and Personal profile. I never use the commandline "-P" option.
My Work profile has a few key bookmarks and extensions in it, but history and cache are never saved and is not linked to a Sync account.
Proving my point that there's no _good_ UI for managing profiles with Firefox. And no, about:profiles doesn't count. Chrome makes it nice and easy and obvious.
