4 ms·

because of it's "great new features" "great" for whom? I've seen enough of the industry to immediately feel suspicious when someone uses that sort of phrasing

because of it's "great new features" "great" for whom? I've seen enough of the industry to immediately feel suspicious when someone uses that sort of phrasing in an attempt to persuade me. It's no different from claiming a "better experience" or similar.

SilasX 3y ago
You can find more examples of that kind of puffer if you go to a website's cookie consent pop-up and find the clause after "we use cookies to...".
- transcriptase 3y ago
  I’ve long thought that those “this new version fixes bugs and improves user experience” patch notes that Meta et al copy and paste on every release shouldn’t be permitted.
  - nebula8804 3y ago
    Tell me about it. I look at all these random updates that get pushed to my mobile phone and they all pretty much have that kind of fluff in the description. Apple/Android should take some steps to improve this or outright ban this practice. In terms of importance to them though I imagine this is pretty low on the list. I have dreamed about an automated LLM system that can "diff" the changes out of the binary and provide some insight. You know give back a tiny bit of power to the user. I'll keep dreaming.
    - Nullabillity 3y ago
      It's worse, as someone who does try to privide release notes I'm often cut off by the max length of the field. And even then, Play only shows you the notes for the latest version of the app.
  - fl0ki 3y ago
    Slack's Mac app release notes [1] rotate a few copy pastes, here's the one that shits me the most. > We tuned up the engine and gave the interiors a thorough clean. Everything is now running smoothly again. Yeah nah mate, if every release is the first release where everything is running smoothly, I'm not going to believe it this time either. Makes me wonder if the team has some release quota to fill and will push a build even if nothing meaningful has actually changed. [1] https://slack.com/release-notes/mac https://slack.com/release-notes/mac
    - SilasX 3y ago
      Ugh. That's especially annoying because they're trying to be hip with slang and use a metaphor that requires cultural knowledge that you can't really assume everyone has.
LtWorf 3y ago
I made a library where version 2 is really really much faster than version 1. I'd want everyone to just move to version 2.
- Brian_K_White 3y ago
  But then you are saying a specific great new feature, performance, and not just the claim and concept performance, but numbers.
  - LtWorf 3y ago
    I'm sure they actually had new features…
    - CanaryLayout 3y ago
      Yeah... RISCV routine was put in, then some binary test files were added later that are probably now suspect. don't miss out on the quality code, like the line that has: i += 4 - 2; https://git.tukaani.org/?p=xz.git;a=commitdiff;h=50255feeaabcc7e7db22b858a6bd64a9b5b4f16d;hp=db5eb5f563e8baa8d912ecf576f53391ff861596 https://git.tukaani.org/?p=xz.git;a=commitdiff;h=50255feeaab...
      - gamer191 3y ago
        > some binary test files were added later that are probably now suspect That's confirmed From https://www.openwall.com/lists/oss-security/2024/03/29/4 https://www.openwall.com/lists/oss-security/2024/03/29/4: > The files containing the bulk of the exploit are in an obfuscated form in > tests/files/bad-3-corrupt_lzma2.xz > tests/files/good-large_compressed.lzma > committed upstream. They were initially added in > https://github.com/tukaani-project/xz/commit/cf44e4b7f5dfdbf8c78aef377c10f71e274f63c0 https://github.com/tukaani-project/xz/commit/cf44e4b7f5dfdbf...
        m0dest 3y ago
        It probably makes sense to start isolating build processes from test case resources.

SilasX 3y ago

You can find more examples of that kind of puffer if you go to a website's cookie consent pop-up and find the clause after "we use cookies to...".

transcriptase 3y ago
I’ve long thought that those “this new version fixes bugs and improves user experience” patch notes that Meta et al copy and paste on every release shouldn’t be permitted.
- nebula8804 3y ago
  Tell me about it. I look at all these random updates that get pushed to my mobile phone and they all pretty much have that kind of fluff in the description. Apple/Android should take some steps to improve this or outright ban this practice. In terms of importance to them though I imagine this is pretty low on the list. I have dreamed about an automated LLM system that can "diff" the changes out of the binary and provide some insight. You know give back a tiny bit of power to the user. I'll keep dreaming.
  - Nullabillity 3y ago
    It's worse, as someone who does try to privide release notes I'm often cut off by the max length of the field. And even then, Play only shows you the notes for the latest version of the app.
- fl0ki 3y ago
  Slack's Mac app release notes [1] rotate a few copy pastes, here's the one that shits me the most. > We tuned up the engine and gave the interiors a thorough clean. Everything is now running smoothly again. Yeah nah mate, if every release is the first release where everything is running smoothly, I'm not going to believe it this time either. Makes me wonder if the team has some release quota to fill and will push a build even if nothing meaningful has actually changed. [1] https://slack.com/release-notes/mac https://slack.com/release-notes/mac
  - SilasX 3y ago
    Ugh. That's especially annoying because they're trying to be hip with slang and use a metaphor that requires cultural knowledge that you can't really assume everyone has.

LtWorf 3y ago

I made a library where version 2 is really really much faster than version 1. I'd want everyone to just move to version 2.

Brian_K_White 3y ago
But then you are saying a specific great new feature, performance, and not just the claim and concept performance, but numbers.
- LtWorf 3y ago
  I'm sure they actually had new features…
  - CanaryLayout 3y ago
    Yeah... RISCV routine was put in, then some binary test files were added later that are probably now suspect. don't miss out on the quality code, like the line that has: i += 4 - 2; https://git.tukaani.org/?p=xz.git;a=commitdiff;h=50255feeaabcc7e7db22b858a6bd64a9b5b4f16d;hp=db5eb5f563e8baa8d912ecf576f53391ff861596 https://git.tukaani.org/?p=xz.git;a=commitdiff;h=50255feeaab...
    - gamer191 3y ago
      > some binary test files were added later that are probably now suspect That's confirmed From https://www.openwall.com/lists/oss-security/2024/03/29/4 https://www.openwall.com/lists/oss-security/2024/03/29/4: > The files containing the bulk of the exploit are in an obfuscated form in > tests/files/bad-3-corrupt_lzma2.xz > tests/files/good-large_compressed.lzma > committed upstream. They were initially added in > https://github.com/tukaani-project/xz/commit/cf44e4b7f5dfdbf8c78aef377c10f71e274f63c0 https://github.com/tukaani-project/xz/commit/cf44e4b7f5dfdbf...
      - m0dest 3y ago
        It probably makes sense to start isolating build processes from test case resources.