Bug in reader/writer locks in Windows API

Post by account42 » Tue, Mar 05, 2024, 11:28 AM UTC

bongodongobob wrote: post #110

amluto wrote: post #23

Earlier quoted context omitted.

Is there any vendor of actually good email-as-a-service? O365/Exchange/Outlook/Hotmail is a mess. Google has a support problem. Fastmail has an offline email problem. iCloud is not obviously suitable for professional use. What’s left?

How is O365/Exchange/Outlook a mess? As a user? As an admin? Genuinely curious. As an admin, I love O365.

Microsoft randomly blocks entire subnets of mailservers. If you care at all about independent mail hosting (and you should if you want email to not turn into yet another proprietary walled garden) then you should not use Microsoft's mail products.

Post by account42 » Tue, Mar 05, 2024, 11:38 AM UTC

AnthonyMouse wrote: post #127

deckar01 wrote: post #116

Earlier quoted context omitted.

Not just high friction, but a formal verification like certification would be interesting.

Nah, you don't want bureaucratic gatekeeping. You want the 14 year old in Kenya or Ukraine with technical competence but no ID to be able to report the bug he finds. The point is to exclude people who don't know what they're talking about, not people who can't pay registration fees or produce documents.

Delegating first-level bug triage to the community can also work as long as your company is well liked enough to motivate volunteers. For that you just need a public bug tracker that everyone can post to but only allow regular users (e.g. those who have made useful bug reports before) to confirm something is a not yet known bug and forward it to your developers. This way once you do get notified of a real bug you will have access to not just that one report but also potential duplicates that might provide interesting information - which might have never been filed if the first level was too high friction.

Re: Bug in reader/writer locks in Windows API

Re: Bug in reader/writer locks in Windows API