Probably depends on where your gross margins would be with cloud and if you're higher or lower growth. If cloud will let you grow faster (HA/DR on-prem is hard) and you'll still have 75-80%+ gross margins, why slow top-line growth to do on-prem?
It’s not a real concern for vast majority of businesses. It’s a common excuse but practically no business is outgrowing a cheaper than cloud solution. Maybe on-prem isn’t right first step, but that doesn’t force you to cloud. There’s dedicated servers and everything in between.
On prem is maybe not the best first step but Colo or dedicated servers gives you a cleaner path to going on-prem if you ever decide to. The cost of growth is too high in cloud.
Learning how to run servers is actually less complicated than all the cloud architecture stuff and doesn’t have to be slower. There’s no one sized fits all, but I believe old boring solutions should be employed first and could be used to run most applications. Technology has a way of getting more complex every year just to accomplish the same tasks. But that’s largely optional.
My guess is they want to have a PIN as a short-term credential analogous to the Touch ID, that is, it only works for X hours per password auth before needing password auth again, and then you only get X tries on the PIN before it either locks the PIN out and you need the full password to reactivate it (or I guess it could wipe the laptop à la iPhone).
26.1 feels significantly less laggy (UI frame rate), especially on low power mode, than 26.0.1. But it's still not back to 18.x level of performance. Battery seems to be improved on 26.1 over 26.0.1 also but that seems to be hardware-generation dependent.
Three and a half years ago nobody had ever used tools like this. It can't be a legitimate complaint for an author to say, "not my fault my citations are fake it's the fault of these tools" because until recently no such tools were available and the expectation was that all citations are real.
Awesome -- dozens of the top people in their fields have been working on the contamination problem and publishing about it for almost two decades.
The curation team was integrated with mission design and operations from the beginning,
as early as 2004 (section 3.0). That integration allowed curation-specific needs such as
contamination knowledge to be incorporated into the mission design early, when adjustments had
minimal cost impact. Not only did this early integration inform planning for sample
characterization, cataloging, allocation, and the development of detailed sample handling and
containment approaches; it was also an investment in the longer term needs of the community.
Here we describe these preparations for OSIRIS-REx, as a reference for sample scientists and
curators and as a model for future sample return missions.
reply