I clone it in my local work-space, and make a few commits over the course of a few days. So my local is A B C
During this time other changes have been merged into upstream, so upstream looks like A D E
I now have two options. I can try to merge from upstream or rebase off of upstream. Merging introduces a messy commit history that quickly becomes difficult to follow. Rebasing removes my local commits, applies the changes in upstream, and then re-applies my local commits.
So after rebasing my local is A D E B C. There are no messy merge commits. And ideally, I can squash my local changes into a single feature commit, so upstream ends up incredibly tidy.
At no place in this process is there any dishonesty or lying. I haven't changed the history upstream, which is the source of truth. What's the issue here?
The problem is a lot of people are already dying because of the current system. If you are in that situation, the downsides of revolution aren't really relevant.
The media in general hypes up Tesla way more than any other automaker. Like every Tesla crash makes headlines. Name any other automaker that faces the same scrutiny.
I think it's maybe more likely a result of car sales being down in general. Nisan light vehicle sales are down 7.8% (~35,000 vehicles) when comparing the first 4 months of 2018 to the first 4 months of 2019.
Some tech companies kinda do it by paying employees in stock. The highest paid employee at Amazon only makes $150,000 cash, while the company creates shares of stock to fund the rest of their compensation. Those are actual shares that get taxes as income, not options.
Since Amazon doesn't participate in stock buy-backs, like most tech companies do, most of the salaries are actually funded by stock holders in the dilution of their shares.
The point being made is that if all that is stopping you from financial ruin is a $5 coffee a few times a week, you're pretty much already in financial ruin. The coffee really isn't and shouldn't be the thing making the difference.
Yeah, so I work at a huge health tech company. A lot of the issue is actually private insurance.
Currently in the US the largest health insurance provider is actually medicare/medicaid. When a patient with medicare goes to the doctor, the government says "This is what we will pay for that procedure, no exceptions." The hospital has a choice to either accept that rate, or to lose out on the massive medicare market.
Private health insurances plans have vastly fewer subscribers, and don't have the power to negotiate prices like the government does.
But regardless, why is health care and insurance a for-profit industry? It creates incentives to put profits ahead of people's health.
> there's a valid counterpoint in that only women assume the risks and responsibility of pregnancy and childbirth
> The draft and pregnancy are fundamentally different things that can't be made equivalent.
If they are fundamentally different and can't be made equivalent, then having a male-only draft in no way compensates for women having to give birth. Which directly contradicts your first statement that it is a valid counterpoint.
Say upstream is at A.
I clone it in my local work-space, and make a few commits over the course of a few days. So my local is A B C
During this time other changes have been merged into upstream, so upstream looks like A D E
I now have two options. I can try to merge from upstream or rebase off of upstream. Merging introduces a messy commit history that quickly becomes difficult to follow. Rebasing removes my local commits, applies the changes in upstream, and then re-applies my local commits.
So after rebasing my local is A D E B C. There are no messy merge commits. And ideally, I can squash my local changes into a single feature commit, so upstream ends up incredibly tidy.
At no place in this process is there any dishonesty or lying. I haven't changed the history upstream, which is the source of truth. What's the issue here?