5 ms·

I hope GitHub changes their vibecoded badges, what does RETIRED even signify in this context? Why does the preview have to be in ominous red?

• mort96 4mo ago
  Hahaha that's amazing, just a big red "RETIRED" badge above their blog post? What the hell
  • petetnt 4mo ago
    Breaking changes have had that tag for ages
    • mort96 4mo ago
      Really? Retired? What does that even mean in this context, why not "breaking" or something else that suggests breaking change?
      • behindsight 4mo ago
        > Retired? What does that even mean in this context "retired" is probably a followup to functionality that was "deprecated". I agree "breaking" would be clearer
        • mort96 4mo ago
          What exactly is it that's now retired that used to be deprecated? Isn't this just a collection of breaking changes to defaults?
          • behindsight 4mo ago
            if you go to the full changelog on the blog and click on the "retired" button, the url will have type=deprecations as the parameter. It's a holdover from previous posts where there were more clearly defined deprecations. but yes, in this case it's more of a behavioural change of defaults, so they just picked the closest vaguely mapped retired/deprecations tag. 1: https://github.blog/changelog/?type=deprecations https://github.blog/changelog/?type=deprecations
      • deleted 4mo ago
        [deleted]
• sheept 4mo ago
  The changelog design has been like that since last year,[0] which predates today's slop design of small caps and monospace text (probably because they both are based on the same design trend). A year ago, vibe coded websites leaned more on sans serif and gradient text. [0]: https://github.blog/changelog/2025-05-05-improvements-to-changelog-experience/ https://github.blog/changelog/2025-05-05-improvements-to-cha...