Using GitUp on the Mac as a client. It allows you to select a commit and press Options-S to reset your branch to this commit, it allows you to squash etc.
And best of all it keeps a backup of your entire repository so you can undo whatever git command you just did.
> but in practice there’s cases where it’s treated more like an unchecked exception in Java, i.e., “I can’t recover from this so _I’m_ going to give up but _you_ can keep going.”
Java has a supertype for unrecoverable problems like out-of-memory-errors. It's called "Error", a subtype from Throwable. Exceptions are also Throwables, but they are NOT errors.
> Java is one of the few ecosystems that provides a software distribution ecosystem that doesn't allow distribution of sources alongside binaries.
This is wrong, source distribution is a standard in maven.
> Gradle literally cannot be built from source[1] because it relies on a binary cache of dependencies held by Gradle to build Gradle.
This is wrong as well as pointed out in the thread.
> As a consequence, the Java ecosystem has become a security and maintenance nightmare that other ecosystems simply aren't. As bad as Nodejs is, it doesn't do this.
This is almost hilarious. I'm working at a company at the moment guiding security updates for java and node.js backends. The java backends are not an issue. The node.js backends are almost impossible to upgrade, the javascript-frontends are even closer to impossibility.
1. Because they confuse Java with the standard hibernate/springboot backends that are used everywhere in the industry. Hibernate/springboot is the reason why there are so many monoliths out there that are almost impossible to refactor.
It's not Javas fault, it's Springs fault.
2. They believe Java is slow, but fail to realize that the JVM has actually one of the most optimized runtimes under the sun and can be fast than (unoptimized) C in many cases.
Long story short: Because they have no clue about Java and follow advice without researching it first.
It is normal that kids take up all your time, but "just chaos" doesn't sound right.
Without knowing your situation, maybe this helps: As you probably know first there was authoritarian parenting (rule the kids), then permissive parenting (let them do whatever they want), both of which create problems for the children.
The parenting-style agreed upon today by psychologists is "authoritative parenting", which basically means telling the kids what you want them to do, but giving them a lenient timeframe and freedom to chose how and when they do it. It raises their self-esteem and encourages them to work together with you.
⌘ Key is often equivalent to ctrl on windows.
Ctrl-C,-V,-X copy'n'paste actions are done with that key on Mac.
I think it's much better placed since you can reach it with your thumb and don't have to rotate your wrist when using it as opposed to ctrl, so when typing macs you might have less strain on your hands.
> Having a 6 year old refuse to sleep without a parent in bed because of "attachment parenting" tends to make one wonder if there's not some merit to having gone through some pain in the early stages.
The work here is not to let the child cry in it's early days, but to put it in it's bed, come when it cries, calm it down, go back to bed, come again when it cries etc. Repeat until child sleeps.
The right response is to ALWAYS react to crying by calming the child, and if the crying was not warranted or necessary, explain that to the child AFTER you have calmed it down.
Children are smart enough to understand sentences like "This is really not something to get upset about", AFTER they have calmed down, and explained in a loving matter.
Important fact about the waterfall model, that no-one ever talks about:
The authors thought it was important to actually do it twice [0].
Of course, nobody in the big corporate/government world wanted to pay a second time for work that has already be done, so most of the projects failed and continue to fail.