527 karma · joined April 24, 2019
In the case of the Sabbath elevator, obviously it was not mentioned explicitly in the Bible, so it's what the Rabbi thinks. So why believe the Rabbi when the logic doesn't seem to be 100% there? I think the reason is there is massive social incentive to comply instead of asking questions about such widely accepted ideas.
It does seem you're speaking from more personal experience than mine, so I defer to you, but I'd like to reiterate that I'm just trying to provide a plausible explanation for why one who doesn't have such a strong belief might still end up doing it (the hypothetical person in the post of the poster I was replying to who's asking themselves why a Sabbath elevator makes sense), but I'm not trying to say that's all there is to it. People who don't question it in the first place because their thought process is that the Halacha is telling them what God meant and thus they are merely following God's instructions don't question whether a Shabbat elevator makes sense in the first place.
Instead, they're following these rules as a social decree. In their circles, it is the obvious and accepted thing to do to follow these rules, which the community's leading Rabbi sets (or well, gives guidelines which are socially considered binding). If you don't follow the rules, then you're a weird one, and religious communities tend not to be accepting of the different, so they will shun you for turning on the light on Sabbath (if you keep doing it..)
So for one born into a religious community, you're taught to do so and there is a strong social incentive to do so: if you don't, you're first branded an odd one, and in some cases shunned, depending on how severe your straying off the path is. If you were told that were you to use the elevator normally, your parents would be very upset with you and may stop talking to you altogether, you'd think about it twice, even if you don't personally feel that you want to follow Judaism.
Finally, the religious authorities have a power incentive to do this: by setting rules and maintaining their position as the authorities who set rules, they keep a lot of power over a large number of people. Often this even manifests financially, as a respected religious authority can give Kosher certificates (and many products which are not food, like phones, can also be Kosher) - of course, the certification costs money, just like a SOC2 audit. Same goes for Sabbath certified electric devices - someone gave their stamp of approval, and the developer paid for it.
So to summarize - religious authorities enjoy power and money by being those who set the rules, everyday people have a strong social incentive to follow the rules as breaking them is taboo.
I think about it like following requirements set by certain certifications. Not all requirements make sense in every context - sometimes you may feel silly complying, knowing you're doing it just to check a box, even though there's no practical value to it.
But there is a value to passing the audit and getting the certificate saying you comply from EY or whoever, so you abide by the requirements, even when they don't make sense, so you can show your ~Kosher~ ISO certificate when you need to.
I'd like to point out that this isn't all there is to it - there are very obviously other incentives to do things this way (e.g. personal belief), but I'm just trying to make an analogy with terms from the HNer's day to day to show why you might follow religious rules even if you're (say) a teenager who doesn't care one bit.
However, (2) seems to say that women, bring to the table a different set of experiences and knowledge than men. Their knowledge is significant since it represents, on some level, approximately half of society. Finally, because women are underrepresented in C level management, this set of experiences means that women have advice and knowledge that can meaningfully influence corporate decisions - that knowledge would be more difficult to come by for men.
So they only appear contradictory when parsed at face value, but actually - at least to me - they seem to be referring to completely different subjects.
Often your main goroutine will just be starting other goroutines, in a multiple-services-one-process architecture, and it doesn't care whether they succeed or not, and its code need not be aware of whether they're critical. If they are, they should panic and crash the program. Just like a main function that crashes.
Doing things with the nursery is restrictive which has its benefits, but I don't agree that it's just strictly always the preferred approach. I prefer an approach like Go's, where you can choose whether to use nurseries (errgroups), and the implementation for them is provided by the language authors. Sure, you are able to start and manage goroutines in this way, even if you don't care about their lifetime - as they are effectively individual programs, but you shouldn't HAVE to.
So when you care about goroutines running only while their starter goroutine is at a certain scope, you can do so. But you don't have to, and when you don't need it - you don't need to pay the price. Go appears to take an approach that provides primitives that are as least restrictive as possible to make it easy to read code, but then also has a batteries included approach with its libraries.
For example, when writing code that performs an operation with the potential to panic, but that you want to convert to an error, something you can do is name the error return value and then modify it in the defer, after recovering from a panic, according to the cause of the panic. It's not obvious that that pattern would work well if defer could also execute on scope end - what does recover do then? Will it affect the following recovers? Also, if the function continues executing but you modified some variables, it makes it complicated to reason about what could be in those variables.
Defer running at function end is much more easier to reason about: functions execute their standard control flow until a return or panic is hit, and then defers are executed, without returning to standard control flow.
And then they actually went through with it - so many private organizations took action. And yet, the government did not force their hand.
This probably shows a lack of understanding of cultural differences by the person surprised by the use of the term rather than the speaker.
Because of this, an AV product could work fine for every department of the company, but have an extreme negative performance impact on software devs. To give you an idea, it could mean the difference between a 5 minute and a 1 hour build. These issues are inherent to a generic AV product so often the fix is simply to add those folders to an exclusion list.
Does it provide security for those folders? Nope. But the alternative could make it impossible to get work done.
At a glance, this seems not possible in Zig because it's a compiletime flag?
I've had a UAP AC LR at home for a few years and we've got about 6 UAP AC HD at work. We used the phone app to provision and after that you can pretty much forget about it. Great for small startups that want great coverage and dont have someone who's supposed to mess around with it.
Browsing their site may also introduce you to some keywords you can use to search for more.
Consider a startup script that hangs forever. Better it fail than hang. Or ls hanging forever when instead the filesystem could fail the operation after 30s.
There's nothing complicated about it, so there's no reason your code can't implement timeouts and cancellation the same way: timeouts are a cancellation triggered autonomously after some time passes.