Witch hunts were capital punishment inflicted on pagan worshipers, not human sacrifices, and they were several tens of thousands in the span of three centuries.
Executions in Spain, Portugal, and Italy combined are estimated to have been 1000 in total. [1]
Is there an easy way to run a browser on some phone/tablet and everything else on a desktop just to isolate the web and JS from accessing your desktop?
No they're not, even with a `cache` value of 1. Sequence values are issued at insert rather than commit. A transaction that commits later (which makes all updates visible) can have an earlier value than a previous transaction.
This is problematic if you try to depend on the ordering. Nothing is stopping some batch process that started an hour ago from committing a value 100k lower than where you thought the sequence was at. That's an extreme example but the consideration is the same when dealing with millisecond timeframes.
Right now there's meh Deep Learning support on the m1 max. TensorFlow is ~supported~, PyTorch is not. Apple has their Neural Engine and CPU/GPU architectures sort of hidden and so it's hard to port or support them.
You can replace 'microservice' with 'class, but completely asynchronous and any interaction with it can fail without caller knowing if it succeed or failed at all'.
I have some experience with Akka. The amount of praying you have to do during production issues, no surprise it feels like a religion.
We tried it about 4 years back. Maybe there are some better debugging tools now, but for us both learning curve and prod issue pain did not make it worth it.
I guess it depends on size of your app and expected load.
When your app is small and you got almost no users, zappa is great: your lambdas are lighting fast and you're in aws free tier.
When your app grows to like 200k SLOC and 50+ lines in requirements, chances are that it starts quite slow. Do you really want to pay for that?
When your load is high enough, well, aws lambdas become quite expensive even without zappa overhead compared to, say, EC2. https://servers.lol/ should say if serverless makes sense for any defined usecase.
Additionally, lambdas have hard restrictions (like 15 minutes limit) and sometimes it's a dealbreaker for you.
In some countries, it's quite different. In Russia, you own anything you made as long as
* you don't touch it while you're on duty
* you don't use the employer's equipment
Obviously, you still can't use any information classified as 'trade secrets' at your current job because it's covered under another law.
You can even work in a directly competing company (or start one) WHILE being employed because job contract can't legally regulate your off-duty time and you can have unlimited number of side-jobs, as long as it's under 20-hours-a-week, in addition to your current full-time job. You don't even have to notify your full-time employer about it. The 'non compete clause' doesn't work. And your full-time employer can't even fire you (legally) just because you work in/own a competing company, as long as you follow all the regulations.
Even the 'I don’t just want to buy your 9:00-5:00 inventions. I want them all' in the job contract can't work if I understand the Russian laws correctly.
There are way too much homophones and you don't always have the luxury of the context. Learning a symbol for each root (not word!) is not that bad, English spelling is almost as bad, actually.
Spoken language is quite limited compared to written Japanese.
Assuming yes, do their users have significant problems understanding the written text when pronounced in an audiobook? Are there well-known conventions or shortcuts or explanations that audiobook readers insert into their speech to signal the correct meaning of the word?
Do Japanese audiobooks provide evidence for or against the idea that doing away with kanji in writing would not harm understanding significantly?
Fiction audiobooks do exists (although not nearly as common as in English-speaking countries), but audiobooks can't possibly work with non-fiction and especially technical texts unless you are going to use English words for literally every single term. I mean, Japanese has only about 100 moraes and way too much words are just 2-3 moraes long.
Some English words can already be writen without using the alphabet. For example, '2015'. I believe numerals in English are used exactly as emoji (or Chinese characters) in Japanese now: embedded inside the sentences, which are composed according to the grammar of language.
>The input difficulties of emoji today seems temporary.
It depends on language, in Japanese input methods a lot of emoji can be written exactly the same way you write rest words.
> It depends on language, in Japanese input methods a lot of emoji can be written exactly the same way you write rest words.
The SwiftKey keyboard on Android offers this feature. If you turn it on and type 'angry', for example, it offers both the word and the emoji as predictions.
It works pretty well for English, but I'm not sure how well it works for other languages SwiftKey supports.
