- This enables abusive parenting styles and forces adult children to need to unlearn this lie in order to come to terms with their abuse;
- This enables parents having an outsized influence on adult children, such as controlling their sexuality, interests, physical location, etc;
Frankly: the parents have an obligation to care for their children because they generally chose to have children or chose to keep them once they were had. The child did not choose to be born and does not have a choice on the quality of their parentage. It's unacceptable to then place the burden on the child for choices they didn't make and have no control over.
The moral question here is more fundamental than your over-generalization of the founders’ intent. Human beings have a right to self determination, and they have the freedom of association. You don’t lose that right just because you were born in America.
Could you share more details on push_to_router.sh? Is it a wrapper around calling nixos-rebuild through ssh?
tar -czf - nixconfig | ssh 192.168.1.1 \
'tar -zxf - && sudo cp -r ./nixconfig/* /etc/nixos/ && sudo nixos-rebuild --show-trace '"${rebuild_flag} ${name_flag}"
So it's great for any code that you want to ensure reliably runs, but having methods that can't fail also opens up new possibilities, like you can:
- Write a method that implements a subscription, charging a card and sleeping for 30 days in a loop. The `await Workflow.DelayAsync(TimeSpan.FromDays(30))` is transparently translated into a persisted timer that will continue executing the method when it goes off, and in the meantime doesn't consume resources beyond the timer record in the database.
- Store data in variables instead of a database, because you can trust that the variables will be accurate for the duration of the method execution, and execution spans server restarts!
- Write methods that last indefinitely and model an entity, like a customer, that maintains their loyalty program points in an instance variable. (Workflows can receive RPCs called Signals and Queries for sending data to the method ("User just made a purchase for $30, so please add 300 loyalty points") and getting data out from the method ("What's the user's points total?").
- Write a saga that maintains consistency across services / data stores without manually setting up choreography or orchestration, with a simple try/catch statement. (A workflow method is like automatic orchestration.)