home.social

#backwardcompatibility — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #backwardcompatibility, aggregated by home.social.

  1. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  2. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  3. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  4. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  5. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  6. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  7. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  8. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  9. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  10. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  11. Oh, look! Apple's giving Rosetta 2 the boot in macOS 28. 🤯 Because who needs backward compatibility when you can just buy a new Mac, right? 💸✨ Also, don’t forget to bless your browser with #JavaScript or you’ll never see the full magic show. 🙄🔄
    developer.apple.com/documentat #Apple #Rosetta2 #macOS28 #backwardCompatibility #newMac #HackerNews #ngated

  12. Oh, look! Apple's giving Rosetta 2 the boot in macOS 28. 🤯 Because who needs backward compatibility when you can just buy a new Mac, right? 💸✨ Also, don’t forget to bless your browser with #JavaScript or you’ll never see the full magic show. 🙄🔄
    developer.apple.com/documentat #Apple #Rosetta2 #macOS28 #backwardCompatibility #newMac #HackerNews #ngated

  13. Oh, look! Apple's giving Rosetta 2 the boot in macOS 28. 🤯 Because who needs backward compatibility when you can just buy a new Mac, right? 💸✨ Also, don’t forget to bless your browser with #JavaScript or you’ll never see the full magic show. 🙄🔄
    developer.apple.com/documentat #Apple #Rosetta2 #macOS28 #backwardCompatibility #newMac #HackerNews #ngated

  14. Oh, look! Apple's giving Rosetta 2 the boot in macOS 28. 🤯 Because who needs backward compatibility when you can just buy a new Mac, right? 💸✨ Also, don’t forget to bless your browser with #JavaScript or you’ll never see the full magic show. 🙄🔄
    developer.apple.com/documentat #Apple #Rosetta2 #macOS28 #backwardCompatibility #newMac #HackerNews #ngated

  15. Oh, look! Apple's giving Rosetta 2 the boot in macOS 28. 🤯 Because who needs backward compatibility when you can just buy a new Mac, right? 💸✨ Also, don’t forget to bless your browser with #JavaScript or you’ll never see the full magic show. 🙄🔄
    developer.apple.com/documentat #Apple #Rosetta2 #macOS28 #backwardCompatibility #newMac #HackerNews #ngated

  16. 🍏🚨. Look, Apple's trying to win the "most backward-compatible #update ever" award by securing the Jurassic-era iPhone 6s with #iOS 15.8.5. 🙄 Clearly, innovation is in their DNA—just like grandpa's old flip phone... 📞🦖
    support.apple.com/en-us/125142 #Apple #iPhone6s #tech #news #backwardcompatibility #HackerNews #ngated

  17. 🚀🎥 "Grok 4 Launch" video: Watch as X Corp. bravely ignores the concept of backward compatibility. 🖥️🔄 Time to play browser bingo and hope your favorite isn't on their kill list! 😂📉
    twitter.com/xai/status/1943158 #Grok4Launch #BrowserBingo #XCorp #BackwardCompatibility #TechNews #HackerNews #ngated

  18. 🚀🎥 "Grok 4 Launch" video: Watch as X Corp. bravely ignores the concept of backward compatibility. 🖥️🔄 Time to play browser bingo and hope your favorite isn't on their kill list! 😂📉
    twitter.com/xai/status/1943158 #Grok4Launch #BrowserBingo #XCorp #BackwardCompatibility #TechNews #HackerNews #ngated

  19. 🚀🎥 "Grok 4 Launch" video: Watch as X Corp. bravely ignores the concept of backward compatibility. 🖥️🔄 Time to play browser bingo and hope your favorite isn't on their kill list! 😂📉
    twitter.com/xai/status/1943158 #Grok4Launch #BrowserBingo #XCorp #BackwardCompatibility #TechNews #HackerNews #ngated

  20. 🚀🎥 "Grok 4 Launch" video: Watch as X Corp. bravely ignores the concept of backward compatibility. 🖥️🔄 Time to play browser bingo and hope your favorite isn't on their kill list! 😂📉
    twitter.com/xai/status/1943158 #Grok4Launch #BrowserBingo #XCorp #BackwardCompatibility #TechNews #HackerNews #ngated

  21. The #popover #api is now baseline and will make #accessible #megamenus easier
    #backwardcompatibility issue:

    if (!('Popover' in window)) {

    load old script
    }

    Has anyone ever tried this? I am worried about the time delay and ask myself if I should just wait a while ....

  22. The #popover #api is now baseline and will make #accessible #megamenus easier
    #backwardcompatibility issue:

    if (!('Popover' in window)) {

    load old script
    }

    Has anyone ever tried this? I am worried about the time delay and ask myself if I should just wait a while ....

  23. The #popover #api is now baseline and will make #accessible #megamenus easier
    #backwardcompatibility issue:

    if (!('Popover' in window)) {

    load old script
    }

    Has anyone ever tried this? I am worried about the time delay and ask myself if I should just wait a while ....

  24. The #popover #api is now baseline and will make #accessible #megamenus easier
    #backwardcompatibility issue:

    if (!('Popover' in window)) {

    load old script
    }

    Has anyone ever tried this? I am worried about the time delay and ask myself if I should just wait a while ....

  25. The #popover #api is now baseline and will make #accessible #megamenus easier
    #backwardcompatibility issue:

    if (!('Popover' in window)) {

    load old script
    }

    Has anyone ever tried this? I am worried about the time delay and ask myself if I should just wait a while ....

  26. In a bold move, #ClojureScript decided to #fork Google Closure like a rebellious teenager claiming #independence, while still living in Google's basement. 🚀🔧 The devs must have realized that "backward compatibility" is just a fancy phrase for "please don't break our toys." 😂
    clojurescript.org/news/2025-05 #GoogleClosure #BackwardCompatibility #DeveloperHumor #HackerNews #ngated

  27. In a bold move, #ClojureScript decided to #fork Google Closure like a rebellious teenager claiming #independence, while still living in Google's basement. 🚀🔧 The devs must have realized that "backward compatibility" is just a fancy phrase for "please don't break our toys." 😂
    clojurescript.org/news/2025-05 #GoogleClosure #BackwardCompatibility #DeveloperHumor #HackerNews #ngated

  28. In a bold move, #ClojureScript decided to #fork Google Closure like a rebellious teenager claiming #independence, while still living in Google's basement. 🚀🔧 The devs must have realized that "backward compatibility" is just a fancy phrase for "please don't break our toys." 😂
    clojurescript.org/news/2025-05 #GoogleClosure #BackwardCompatibility #DeveloperHumor #HackerNews #ngated

  29. In a bold move, #ClojureScript decided to #fork Google Closure like a rebellious teenager claiming #independence, while still living in Google's basement. 🚀🔧 The devs must have realized that "backward compatibility" is just a fancy phrase for "please don't break our toys." 😂
    clojurescript.org/news/2025-05 #GoogleClosure #BackwardCompatibility #DeveloperHumor #HackerNews #ngated

  30. In a bold move, #ClojureScript decided to #fork Google Closure like a rebellious teenager claiming #independence, while still living in Google's basement. 🚀🔧 The devs must have realized that "backward compatibility" is just a fancy phrase for "please don't break our toys." 😂
    clojurescript.org/news/2025-05 #GoogleClosure #BackwardCompatibility #DeveloperHumor #HackerNews #ngated

  31. In Spring 5, HttpMethod became a problem.
    In Spring 6, we could finally fix it.
    New blog post on enums, backward compatibility, and quiet corrections:

    poutsma-principles.com/blog/20

  32. @rhaen Yes, I am migrating several GNU/Linux servers these days, and I am getting increasingly annoyed with programmers who give a shit about backward compatibility.

    The other case I tripped over is Fabric, a deployment tool for Python. Fabric 2 is what you get when you `apt install python3-fabric` on Debian 11. However, Fabric 2 uses a configuration language that is incompatible with Fabric 1. So existing users need to figure out that instead of using the Debian package, they need to do `pip install fab-classic` to get a fork of Fabric 1 with updated dependencies. (There is another fork of Fabric 1 for Python 3 called fabric3, but that is now abandonware, so make sure you avoid it!)

    The good thing is that Fabric 2 and Python just failed with my old configuration file instead of doing nonsensical stuff like Perl did in my previous example.

    #Python #backwardCompatibility #Fabric

  33. Windows 95 went the extra mile to ensure compatibility of SimCity, other games - Enlarge / Microsoft wanted people to have zero reasons not to upgrade t... - arstechnica.com/?p=1888556 #backwardscompatibility #backwardcompatibility #finalfantasyvii #gaming&culture #uncategorized #joelspolsky #windows95 #simcity #tech

  34. Why modern consoles can’t just “run any... older executable” - Enlarge (credit: Aurich Lawson | Getty Images)

    Historically, w... - arstechnica.com/?p=1814080 #backwardcompatibility #gaming&culture #legalemulation #emulation #legal

  35. Sorry, you can’t move your discontinued copy of PT to the PS5 - Enlarge / PT scenes like this will not be viewable on the PS5, even though they were briefly during... - arstechnica.com/?p=1721574 #backwardcompatibility #gaming&culture #playstation #konami #sony #ps5 #pt