From what's listed in the news story, we don't know that, but the point of the article is not to single out Oracle, but to realize that financial accounting for cloud software products is a grey area that affects many firms -- including those that sell it, and even the buyers, and having clearer standards will benefit everyone.
The gray area is how one counts revenue as cloud or non-cloud. Some software can be used in both modes, and the question is how one categorizes them. For example, Microsoft Office 365 can be used in cloud (in style of Google docs) but it can be installed locally. The gray area affects many firms, and is not isolated to Oracle.
You have a good point. It's a spectrum. There are software companies that thrive by using different models. Some are based on open source, some are based on closed source and some even mix the two. Some other companies as listed elsewhere are ad-companies and give away software to bolster their eco-systems.
It seems that Jet.com (Ana Amazon-like competitor, I haven't used them yet, so don't know the experience) has a $35 threshold for 2 to 5 day free-shipping.
Good point about market maturity. If people are holding on to phones longer, sell them more accessories that people replace periodically, and make the base unit more also high margin (if they accomodate the official bumpers). But it's the consumer's choice -- they don't need to buy new bumpers if they are content with what they have. It's a variant of the razor & blades model.
If the lengthening indicates that vague subject lines such as "Hello!" or "Changes" is being replaced by something more specific like "Meeting at 3 p.m. agenda changed", then it's a good thing. I also like all the info in the subject line, such as "Free pizza in the break room <eom>"
Those are excellent points. Old small flip phones sometimes had a small place for a strap loop so you can fish it out of a bag by the strap, and of course also to hold on to it. Phone straps are popular in Japan, and I've seen some that connect to the headphone jack, but it doesn't really work well, so the sturdier ones connect to a bumper.
A bumper-design (maybe a groove to hold a bumper) is a good idea too. One can argue that making phones easier to damage encourages people to replace it with new ones so manufacturers have hidden incentive to avoid such safety features, but ultimately if someone comes up with a better design like you state, people will flock to it.
I didn't know about this book, and thank you. I think reading the style and opinion of key contributors to industry, science, nature preservation and other areas also helps me understand their motivations and world views. It's not just a listing of facts, but trying to get into their mind-set. I feel I do not get that from wikipedia.
On Feb 20th, 2016, it was reported that Secretary of State Kerry warned the kingdom of Saudi Arabia and Pakistan of non proliferation treaty consequences if the kingdom acquired such weapons. This news report may be related to that.
True. By the way, the Galaxy S7 is supposed to have a metal case but it still has wireless charging too so the engineering seems to be feasible.
In my experience the distance between the pad and charger receiver made a big difference, thus putting on a thick case made charging difficult to proceed quickly.
I agree. With automobiles, people seem to be more aware of the constraints and the balance of capabilities to make a vehicle that fits a segment. I.e. sports cars aren't always comfortable. One day, people may understand tradeoffs in phones and realize that long battery life may require a thick phone.
Encryption and security has always been a balance between convenience and capability. Although HTPPS and such are mostly transparent to end-user, we can see that slow adoption of public key encryption (GPG) indicates that people either need to be educated or the user experience needs to improve drastically. It's taken many years but there's a long road ahead.
Somewhat understandable for a firm in rough waters, but it does raise the issue of scope. What if you go out to lunch and drink and come back? Is that allowed, or is that something you do on your own time and outside? I suspect there are gray areas if you try to parse the rules too carefully. I think common sense prevails, such as not getting hammered while you work.
It's a major point to make sure errors are properly emulated as well. Same issue was dealt with in VMware Workstation as well, which managed to behave accurately for devices such as floppy disks.