1. You have to handle race conditions if there is ever more than one process writing to the DB at one time
2. It’s ambiguous whether a number is an ID. E.g. when looking at logs
3. Numbers leak information about table size, row age, and crucially future row IDs.
They've absolutely crippled 1password to make local vaults as difficult to buy and use as possible. They don't roll out updated versions as often, many versions don't get support for local vaults for years, they make it nearly impossible to buy the non-subscription version, and you can no longer upgrade older licenses to use new versions.
Their entire business model is really sleazy and they've gone out of their way to alienate people who don't want to pay for a subscription and hosting service for something as simple and secure as locally encrypting passwords. I was a loyal customer for a long time but after a few years of them jerking non-subscribers around, I got tired of it and tell any friends and family to stay away from it.
Every company that has moved to a subscription and cloud-based product has essentially traded a one time $30-50 license to getting that (or more) every year, and the product is usually inferior from my experience.
> Every company that has moved to a subscription and cloud-based product has essentially traded a one time $30-50 license to getting that (or more) every year, and the product is usually inferior from my experience.
Two mild counterpoints:
(1) While "from my experience" is always definitionally anecdotal, most applications that I'm aware of that have moved to (or started with) a subscription-based model have released new features on a rolling schedule that's at least as fast, if not faster, than the "one-time license" model. On the Mac/iOS, there's Ulysses, Fantastical, and Drafts off the top of my head; cross-platform, the JetBrains IDEs all come to mind. (They're not precisely the same model due to their "perpetual fallback license" approach, but they're definitely trying to drive you to subscribe.) And, for all the mostly-deserved hate Adobe gets, their release cycle appears to have picked up speed since they moved to a subscription model.
(2) The one-time license model works great for applications that don't need any updates in the future beyond perhaps bug fixes. If you want ongoing support and new features, where does the money to support that come from? In years past it would have come from upgrade pricing, but programs went years between new releases and there was nothing that compelled users to upgrade if the old program was still working on their hardware. I get that as a user that's great, but for developers, it's, well, rocky. It was livable a decade ago because those big application programs were way more expensive. At today's prices, where $39 seems kinda steep, that may not be a workable business model.
As for 1Password specifically, I run it on a work laptop, a personal laptop, an iPad Pro, an iPad Mini and an iMac, and keeping the various "local vaults" in sync was always a bit of a pain in the ass -- and of course there was no way to access that vault over the web on a different machine if I really, truly needed to. And I know more than a few people using 1Password for Families. I don't think it's a "really sleazy" business model at all. It may be a business model that you don't like, but that's not the same thing.
Yeah, he didn't exactly need an Apple watch to tell him something is going on. That's a bit under double what his heart rate should be. Equivalent to what someone in reasonable shape would have when they're jogging. It's amazing he never got it checked out before.
It's possible he may not have noticed, or may not have realised that his RHR was unusually high. I mean, in day to day living how many of us are really conscious of what our hearts are doing outside of periods of heavy exertion?
120 is an "uncomfortable" heart rate though; you'd feel it at rest, it would somewhat get in the way of concentrating or sleeping. (Although it's easy to dismiss as resulting from anxiety or infection.)
As even the tiniest bit of research will show, that is insanely high. Well over 99th percentile for that age group, according to US CDC. While it might be counterproductive to get anxious about minor symptoms, when one of the most critical indicators of overall health is off the charts I think "you should be worried" (with "go see a doctor" as the express or implied followup) is the humane response. "Meh" or denying the statistical reality is IMO irresponsible.
The average person's resting heart rate is 70 bpm. The "maximum" heart rate is roughly 207 - 2/3 of your age.
So for someone who is say 30, your maximum rate is ~187. But a rate over 90 when resting is considered outside normal levels.
If you have no history of cardiac disease and aren't taking any medications that would cause an increased rate, if your resting rate is 113-120, you need to be checked.
I'd consult if mine was over 90 at night for no apparent reason (usually below 50, but went as high as 80 during a hard hiking week). Monitoring my nightly heart rate (Samsung Watch) gave me quite an insight on my general shape. When sickish, definitely not going as low as usual...
Yeah, my dad died of a heart attack at a relatively young age, and I've been paranoid about my cardiovascular health ever since. Half an hour of that HR at rest and I'd be off to the ER.
I’m definitely aware that I suffer from hypochondria, but what if I’m just imagining that I do? All joking aside, I never even thought about getting help for that, maybe I should.
It's very common, and it often starts after an illness or health scare. In some people it gets worse and worse, they start going to the ER all the time because they feel something is wrong etc. It can be debilitating. If you feel like it's having a negative impact on your life, don't hesitate to seek help. It's always easier to nip it in the bud sooner rather than later.
Hah, too late now, I kind of got over it on my own, but it was debilitating for a while. The catch 22 is that the brain that's tricking itself isn't aware that it's tricking itself. Once I realized over time that I was imagining it, I was able to put it behind. Also, no doctor that I went to see for my imagined problems ever suggested that I should seek treatment for health anxiety, which I guess I don't blame them for because they are supposed to take people's complaints seriously.
No, that's not quite what it is. You can have an unusually rapid, but regular (i.e. normal sinus) rhythm and that's called tachycardia. During tachycardia, the electrical impulses that control the muscles of your heart fire in the correct sequence, intensity, and spacing between impulses, they just go through a cycle much more quickly. If you looked at an ECG and measured the distances between the peaks and valleys, they'd be at consistent distances, just really close.
During a-fib, the electrical impulses are all off. The peaks and valleys are irregularly spaced and the amplitudes vary from cycle to cycle. This usually results in a rapid heart rate as a second order effect because, due to the "misfiring" not enough blood is pumping through and your heart is working harder to make up for the difference.
1Password 7 re-adds local vault support to Windows for standalone license users at the very least. Not sure about subscription users... as there seems to be conflicting information about this.
Alas, not helpful here. The logging is done in PROMPT_COMMAND, meaning by the time you can type another command things are already logged and editing your history won't help. Hopefully (though I see no evidence of this, I've also only skimmed the material) things are marshalled somewhere locally and can be inspected/edited before being sent to the server.
You're doing a disservice to yourself and the people who have to work on (or more likely fix) your code by having this attitude. Plenty of people are capable of producing great work and still spending the time to actually understand the systems they are working on.
There aren't that many giants; there are a lot of people with a few years of experience that think/claim they're giants.
Mmmm... We'll just have to disagree on this. I can track a great number of octaves, from business strategy down to operating system scheduling and locking strategies, CPU instruction pipelines and scheduling, semiconductor fabrication techniques, and even down to the lifetime exergy of the whole equipment/software/facilities supply chain. But I can only do a little bit at a time, an as-needed basis. I can't be too concerned with instruction set design or supply chains while I'm optimizing an SQL query or building a D3.js web visualization. It's just too remote from the task at hand. If you, in contrast, can simultaneously understand and reason about every technology along the continuum from delivered apps and services down to the impedance constraints in the CPU layout process, good show! That's a surpassingly rare skill, but perhaps there are some Sherlocks among us.
I think it's obvious that I'm not advocating you have innate knowledge of everything down to semiconductor fabrication in order to be a competent javascript programmer. I would argue you want at least a basic understanding of the internals of the software you're relying on.
You're writing SQL queries and claim you don't have the time to research how the database you're using works internally without destroying your productivity? You can write SQL without knowing the database's indexing strategy or how it optimizes queries, but it's likely to be of a lesser quality than someone who has taken the time to do so.
