3 ms·

Well, this is a fascinating murder mystery that establishes 3 compelling suspects - Grammarly, Chrome, and a gif - and then just ... ends, right before the big

Well, this is a fascinating murder mystery that establishes 3 compelling suspects - Grammarly, Chrome, and a gif - and then just ... ends, right before the big reveal.

0xNotMyAccount 3y ago
I have a friend who worked at Gusto, and my wife tried using Gusto for her small business (they handle payroll for small business, got a big boost from the pandemic). The lack of technical resolution here is so Gusto, it hurts.
- Andrex 3y ago
  They nuked my account after trying to charge an expired card three times. The customer response team was extremely quick and responsive telling me their hands were tied. Fuck Gusto.
  - Kognito 3y ago
    Hate that. “Sorry, the system says no” Had similar situations with PayPal and Uber recently where their support have absolutely no information or ability to take a decision. Support essentially becomes a glorified text-to-speech system.
  - deleted 3y ago
    [deleted]
- robocat 3y ago
  That's unfair: isn't this is exactly how most strange bugs get "fixed" by most companies? It is an abnormal developer and an even more abnormal business that actually spends enough time to find the root cause of outré glitches. Especially when you start having to debug complex third party systems to debug them properly - requires skills and motivation plus a company that will encourage a developer to do that. The story is not specific to Gusto - it is the story of every developers life. I have chased down bugs in my OS and my browser - it is rarely well rewarded! Fixing a compiler bug should be on my bucket list! A long time ago I worked around a compiler bug by inserting a label: (I think the label prevented certain optimisations where the label was put).
- tclancy 3y ago
  I mean, this story is a hell of a rundown of debugging. The fact they don't have insight into the ways Chrome or Grammarly work isn't something to apologize for.
Maxion 3y ago
I feel so unsatisfied
deleted 3y ago
[deleted]
fifafu 3y ago
Maybe it’s because Grammarly enables full accessibility support in Chrome to be able to access all elements in the browser (similar to a screen reader). This has caused me various issues in the past (e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=1364487 https://bugs.chromium.org/p/chromium/issues/detail?id=136448... ). However it’s probably good that the Accessibility functions get more exposure due to this.
chrismorgan 3y ago
The GIF cannot be responsible: as untrusted web content, if it can trigger a crash, the responsibility lies with the local software stack. So you have only two suspects: Chrome and Grammarly. The GIF is at most an accomplice.
- sfink 3y ago
  more like a murder weapon
  - chrismorgan 3y ago
    Thanks, that’s much better. I wasn’t at all happy with “accomplice” but my mind was blanking on what it should be.

Well, this is a fascinating murder mystery that establishes 3 compelling suspects - Grammarly, Chrome, and a gif - and then just ... ends, right before the big reveal.

0xNotMyAccount 3y ago

I have a friend who worked at Gusto, and my wife tried using Gusto for her small business (they handle payroll for small business, got a big boost from the pandemic). The lack of technical resolution here is so Gusto, it hurts.

Andrex 3y ago
They nuked my account after trying to charge an expired card three times. The customer response team was extremely quick and responsive telling me their hands were tied. Fuck Gusto.
- Kognito 3y ago
  Hate that. “Sorry, the system says no” Had similar situations with PayPal and Uber recently where their support have absolutely no information or ability to take a decision. Support essentially becomes a glorified text-to-speech system.
- deleted 3y ago
  [deleted]
robocat 3y ago
That's unfair: isn't this is exactly how most strange bugs get "fixed" by most companies? It is an abnormal developer and an even more abnormal business that actually spends enough time to find the root cause of outré glitches. Especially when you start having to debug complex third party systems to debug them properly - requires skills and motivation plus a company that will encourage a developer to do that. The story is not specific to Gusto - it is the story of every developers life. I have chased down bugs in my OS and my browser - it is rarely well rewarded! Fixing a compiler bug should be on my bucket list! A long time ago I worked around a compiler bug by inserting a label: (I think the label prevented certain optimisations where the label was put).
tclancy 3y ago
I mean, this story is a hell of a rundown of debugging. The fact they don't have insight into the ways Chrome or Grammarly work isn't something to apologize for.

Maxion 3y ago

I feel so unsatisfied

deleted 3y ago

[deleted]

fifafu 3y ago

Maybe it’s because Grammarly enables full accessibility support in Chrome to be able to access all elements in the browser (similar to a screen reader). This has caused me various issues in the past (e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=1364487 https://bugs.chromium.org/p/chromium/issues/detail?id=136448... ). However it’s probably good that the Accessibility functions get more exposure due to this.

chrismorgan 3y ago

The GIF cannot be responsible: as untrusted web content, if it can trigger a crash, the responsibility lies with the local software stack. So you have only two suspects: Chrome and Grammarly. The GIF is at most an accomplice.

sfink 3y ago
more like a murder weapon
- chrismorgan 3y ago
  Thanks, that’s much better. I wasn’t at all happy with “accomplice” but my mind was blanking on what it should be.