Having used the API with a polyfill, it is a bit verbose and may seem a little obtuse at times. However, it allows you to explicitly differentiate between Date, Time, (Plain)DateTime, and ZonedDateTime. I have had to fix plenty of bugs because a datetime in the browser, datetime on the server, and UTC got mixed up at some point, and this API makes that a lot more difficult (and not likely to happen accidentally).
It need not be someone in the US, just a country which is not one of a few named adversaries. A Singaporean owning company would comply with the law just as well.
I'll second the sibling poster here by saying anything useful you want to do with WordPress will probably have a non-negligible cost, and usually a subscription. WooCommerce for instance requires a subscription to add a minimum quantity to a product! I volunteer for a non-profit that uses it, and it's absolutely insane how many plugins will give you a little for free but charge $5/month or $50/year for just slightly more features.
About a decade ago, there was a huge kerfluffle about making the plugin directory include pricing and payments (like an app store). Matt was hugely against it. I think they did themselves a huge disservice. Pricing is opaque until you install the plugin, often requiring you to go "off site" to install the paid version (or it silently uses a different plugin repository). Lastly, there is no quality control or even ensuring that best/ethical practices are being followed.
So, you end up with this scummy feeling every time you install a plugin and discover its pricing.
If you were to guide them today, what would you set them up that's not WP that gives functionality similar to wp+woo?
(asking for someone who has a site using wp+woo. I don't plan to switch us - the switching cost is too high to be worth it - but I do want to have something in my pocket for the future.)
A couple of factors keep most hurricanes away from the mountains. There's a strong gulf stream current that tends to lead hurricanes up along the east coast, sometimes as far north as NYC. And also the Gulf of Mexico can draw hurricanes away. Hurricanes dump so much rain on land that they have to be constantly replenished by water sources, otherwise they'll peter out pretty quickly. Land also exhibits something like drag on hurricanes and tends to slow them down.
I bet there have been some hurricanes whose edges have grazed central NC, but the most intense weather (heavy, sideways rain, storm surges, and 200mph+ gusts) are experienced at the edge of the eye. It's rare that hurricanes are so big and intense that land far away from water experiences the worst of it.
I'm running SUSE Tumbleweed. Fast package manager, up-to-date versions of just about every package you could want. Never had any driver issues or issues installing.
Ge'ez and its adaptations are abugidas, which means one symbol is a full syllable. For Amharic there are over 200 individual symbols. [0] That would be a big keyboard! It does seem that most in-use languages in Africa are alphabets or abjads, which could be adapted to keyboards. [1]
Would these African abugidas be served well with a keyboard like the mobile 10-key Japanese swipe keyboards? [1] Japanese has much fewer sounds so it all fits in a pretty small package but it works so much better and faster than romaji in that context. Maybe it could be adapted with slightly more keys and complex swipe patterns, like up then right/left etc (it looks like for ge’ez at least, such patterns might actually be intuitive eyeballing the patterns in the characters, but someone native would know best).
It'd be nice, but I don't think that model would be workable here.
Somewhat oversimplified, but the two Japanese syllabaries hiragana and katakana are around 50 distinct characters each, so that a core 3x4 board of "keys" responding to tap(-and-maybe-swipe (up|down|left|right)) will give you roughly the full set of each. Generally, tapping the key designates the consonant; swiping (or not) gives you the vowel. There are 5 vowels, and roughly 10 consonants. There's a couple of other symbols added on as modifiers for voicing, etc. Again, oversimplified, but that's roughly it.
(Side note, and I'm guessing here, but I suspect this model probably evolved from T9 texting)
From a brief inspection of https://en.wikipedia.org/wiki/Ge%CA%BDez_script, the Ge'ez syllabary/abugida (used e.g. for Amharic) needs 6-8 vowels across at least 26 consonants, and then some more combinations for labialization/velarization, and then some more for application in specific other languages.
Following the Japanese model, that'd be a pretty big grid :) Phonetic input seems a more workable model to me at least.
So probably the user on the video types in a phonetic approximation of the words using the latin alphabet, and the software translates it to the abugida symbols?
Seems plausable, especially because he types several latin characters to get one symbol.
Interesting to note that sometimes he also uses digits.
Programming books are definitely becoming more hit or miss, as the volume of books has increased dramatically in the last 10-15 years. There are still great books, but there are a lot more bad ones out there. There's a lot more software out there, and a lot more people learning about it.
I had a horrible experience with Packt. I had subscribed andwas in the middle of reading a book. The book suddenly became unavailable, so I created a ticket. They threw a few tokens at me, and asked if they could just close the ticket, even though there was no mention of whether the book was going to be available again.
Then weeks later they signed me up for six(!) separate mailing lists without asking me, one for each tag I had flagged as interested.
