I bought a leap v2 and had to return it, the top of the backrest is not straight and this is apparently almost by design and within their tolerance, which I find unbelievable for 1k+ chair.
Have been with the Steelcase Amia for 2 years now and am quite happy.
I think most things you describe are just getting used to product difference / configuration options.
Clicking an email definitely marks it as read.
The calendar schedule not being revealed is a just a privacy option, each person must opt-in to share the exact meeting details.
Having used both gsuite and office I find that they both get job done fairly well
> The calendar schedule not being revealed is a just a privacy option, each person must opt-in to share the exact meeting details.
We've done this as far as I know. We also added each other to our directory. I can see the details of other team mate's calendars in the full view but this does not show up in the mini-view when you add a guest to an event.
With Google, when you create a new event and put in a user's email as a guest it immediately showed you a full list of their exact events with times and whether or not they accepted an optional meeting (an outlined or filled circle). It was great to see at a glance while you're in the process of creating the event.
With MS' calendar all you see is a red block of color around the times they are not available.
> Clicking an email definitely marks it as read.
It doesn't for me when using Chrome. When I click into an email the title remains bold and the inbox count doesn't decrease. Keep in mind this is the web app. I didn't install the dedicated app, but I also used the web version of all of Google's tools too.
The sharing aspect has already been done. It still doesn't show the details in the mini-view where you insert the person's name as a guest which is the most important time to see such information.
You just see a big chunk of red with no details. You don't even see things like "busy". It's just a solid red color.
The key is that there are 5 permission levels: (1) None, (2) Can view when I'm busy, (3) Can view titles and locations, (4) Can view all details, and (5) Can edit.
Is that too much control? Maybe, but it's helpful when you want to share more details with teammates than you do with others, grant admins edit permissions, etc.
The email gets marked as read once you click out of the email to view a different one (which I agree is unintuitive, but it is not true you have to explicitly click "mark as read").
The location for setting mail read on selected is settings-> mail-> message handling-> Mark as read.
Outlook also defaults to not marking messages as unread when the unread filter is on. I presume because profiles were setting the filter and then complaining their messages were disappearing? You can change rose on the same settings page
Everyone talks about how docker desktop will be replaced as it's a commodity and I agree. However I see no one talking about the value Docker hub brings which is now bundled with all paid users.
By paying we didn't have to migrate anything and are now building and pushing every commit on our app as a 800mb image (I know its a little to big...). We are storing hundreds if not thousands of images and uploading / pulling TBs.
This kind of usage appears much pricier in container registry offered by cloud vendors
For hyperhidrosis, if you can tolerate the discomfort, I highly suggest using Iontophoresis. It really changed my social life after trying many other solutions that did not work.
There are now plenty of commercial machines available
The question at hand will always reduce down to the "Two Generals problem" [0]. The outbox pattern is a nice separation of concerns and gives at least once consistency as long as the forwarding happen before writing the event as processed in the outbox. Both side effects happening atomically through all failure cases is impossible.
To solve that issue you need a cooperating destination for your writes which handles de-duplication. Then you get into the weeds of causality, ordering and idempotence. Ugh.
For some real world examples see the AWS Kinesis documentation which says that any application using Kinesis must be able to handle duplicate records [1].
> There are two primary reasons why records may be delivered more than one time to your Amazon Kinesis Data Streams application: producer retries and consumer retries. Your application must anticipate and appropriately handle processing individual records multiple times.
Nice. Seems a bit disingenuous on yugabyte to claim they’re better performant in light of this.
Just want to say that I love your docs. Haven’t used cockroachDB just yet but the docs are clean, easy to follow, devoid of marketing and focused on facts.
> 2019-09-05: YugaByte’s blog post states YugaByte DB “passes Jepsen tests”. We feel obligated to state that YugaByte DB’s Jepsen test suite does not pass, though it may in the future. Race conditions in YugaByte DB’s schema system can cause correctness errors. For example, inserting rows into a freshly-created table with DEFAULT values may result in the values for those columns initialized to NULL instead. We can also now confirm that this issue affects all default values, not just DEFAULT NOW(). It also appears that DDL race conditions might, under certain conditions, render tables completely unusable.
Yikes. I understand the need for marketing and making their product look good but it's going a bit too far saying they pass the tests when they didn't. I can easily see potential customers pausing when encountering that kind of attitude from YugabyteDB's developers. "What else are they dishonest about..." kind of idea.
Have been with the Steelcase Amia for 2 years now and am quite happy.