4 ms·

It's a shame about the tone of this post. I think it might not suit HN. As a Google Cloud customer, though, I think you do manage to be spot on about a lot of t

by jfoster 12y ago

It's a shame about the tone of this post. I think it might not suit HN. As a Google Cloud customer, though, I think you do manage to be spot on about a lot of the things Google are doing wrong when it comes to the Cloud Platform. Today I came across an App Engine SDK bug that was reported almost 5 years ago, has a several years old patch in the comments, and still hasn't been remedied by Google. App Engine users who encounter it have to find the bug, apply the patch to the SDK, and repeat that upon each SDK update.

dlor 12y ago
Could you send me a link to the issue? I can hopefully get that fixed.
- throwaway2349 12y ago
  TIL: Google doesn't know where its own bug database is.
- d0vs 12y ago
  Not OP but here's another example: https://code.google.com/p/googleappengine/issues/detail?id=6469 https://code.google.com/p/googleappengine/issues/detail?id=6... The patch is trivial
  - nulltype 12y ago
    urlfetch is the worst, at least MVM will be getting rid of that. I would just use the socket api instead of urlfetch, like I do here: https://code.google.com/p/googleappengine/issues/detail?id=601&q=post%20delete&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component https://code.google.com/p/googleappengine/issues/detail?id=6...
    - jfoster 12y ago
      Wow. That's a classic example of the lack of investment into App Engine. Filed 7 years ago, acknowledged, and still open with no one assigned to it.
      - nulltype 12y ago
        It's true, if Google wants GCP to be good, they will have to use it themselves. I definitely don't trust public bug reports to fix issues. At least if you have a support plan they are good at responding and sometimes fixing things. There's no way anyone in Google uses URLFetch, which explains why it's so bad.
- jfoster 12y ago
  It is: https://code.google.com/p/googleappengine/issues/detail?id=3646 https://code.google.com/p/googleappengine/issues/detail?id=3... Thank you for that!

by jfoster 12y ago

dlor 12y ago

Could you send me a link to the issue? I can hopefully get that fixed.

throwaway2349 12y ago
TIL: Google doesn't know where its own bug database is.
d0vs 12y ago
Not OP but here's another example: https://code.google.com/p/googleappengine/issues/detail?id=6469 https://code.google.com/p/googleappengine/issues/detail?id=6... The patch is trivial
- nulltype 12y ago
  urlfetch is the worst, at least MVM will be getting rid of that. I would just use the socket api instead of urlfetch, like I do here: https://code.google.com/p/googleappengine/issues/detail?id=601&q=post%20delete&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component https://code.google.com/p/googleappengine/issues/detail?id=6...
  - jfoster 12y ago
    Wow. That's a classic example of the lack of investment into App Engine. Filed 7 years ago, acknowledged, and still open with no one assigned to it.
    - nulltype 12y ago
      It's true, if Google wants GCP to be good, they will have to use it themselves. I definitely don't trust public bug reports to fix issues. At least if you have a support plan they are good at responding and sometimes fixing things. There's no way anyone in Google uses URLFetch, which explains why it's so bad.
jfoster 12y ago
It is: https://code.google.com/p/googleappengine/issues/detail?id=3646 https://code.google.com/p/googleappengine/issues/detail?id=3... Thank you for that!