I would rather be charged for what I'm using instead of an amount that's fudged to amortize unexpected incidental costs over all users. Maybe some kind of additional insurance against extra costs might be a feature that some users would use, but I prefer to self-insure than help others defray costs.
The upfront pricing was just an estimate of the total based on previous data. I much prefer it, because it incentivizes the driver to take the most efficient route, since they get paid based on arrival and not the way they go.
In the pay as you go system, you are at the mercy of the driver, and they are actually incentivized to take a longer route.
I've definitely had drivers take longer routes under the pay as you go system. I would complain to Uber and they would refund the money, but it was still a hassle to complain.
Interestingly, in places where Uber still has up front pricing for riders, drivers are paid on time and distance. Uber is taking the risk of the estimate being too high or too low.
Perhaps you're comparing a multithreaded version with a single threaded version, or a single-host build vs distributed build.
When adding new features to a compiler, you might want to verify that the old and new versions have the same output given the same input. If your compilers produced non-deterministic output, this exercise would not be possible.
I took the statement "different compilers" to be completely different projects and codebases. Of course reproducable builds make sense in that situation. But why in the world would you ever expect gcc to 100% always match the output of llvm? That doesn't make sense.
Savings like these are generally passed on to stakeholders; existing contracts (e.g. vendors, clients, employees, contractors) are rarely automatically renegotiated to reflect lower cap ex
WeWork isn't a great apples-to-apples comparison with a residence; it's more like a hotel. This lease almost certainly includes insurance, maintenance, cleaning, and maybe even services like a stocked kitchen, receptionist/office manager, security
The uniformity across all devices is great in Safari too. Synced passwords between my work laptop, home laptop, phone, and iPad is such a convenience. Also great if I'm reading an article at home and then want to bring it up on the phone for my commute and then my work laptop when I arrive--totally seamless.
Yes, generally if you work full time, your employer contractually owns any IP you produce unless you disclose that you're involved in outside projects.
They might own what you do on company time with company resources, but full-time employment does not entail your employer owning the intellectual property you produce on your time with your own resources.
But my understanding is your employment contract can pre-assign that property to your employer, and that contract will be enforceable in (e.g.) California if the IP relates "at the time of conception or reduction to practice of the invention to the employer's business, or actual or demonstrably anticipated research or development of the employer".
Totally depends on your employment contract. Plenty of large places and even smaller places take a “we own everything you create” clause.
Now, now enforceable it is often depends, but the Oculus case is just one major example of how a company can assert ownership of IP created outside of work hours.
Right, I was addressing the OP who said that full time employment means that your employer owns the intellectual property you create on your own time, which isn't the case by default.
And for large companies, even if they don't "own everything you create" they often have their fingers in enough pies for anything you could come up with to be construed as being a conflict of interest.
