#backwardcompatibility — Public Fediverse posts

RE: https://infosec.exchange/@art4/115747129017446982

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:

https://packagist.org/packages/art4/rector-bc-library

Happy new year! 🥳

RE: https://infosec.exchange/@art4/115747129017446982

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:

https://packagist.org/packages/art4/rector-bc-library

Happy new year! 🥳

RE: https://infosec.exchange/@art4/115747129017446982

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:

https://packagist.org/packages/art4/rector-bc-library

Happy new year! 🥳

RE: https://infosec.exchange/@art4/115747129017446982

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:

https://packagist.org/packages/art4/rector-bc-library

Happy new year! 🥳

RE: https://infosec.exchange/@art4/115747129017446982

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:

https://packagist.org/packages/art4/rector-bc-library

Happy new year! 🥳

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: https://packagist.org/packages/art4/rector-bc-library

And feel free to give me feedback.

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: https://packagist.org/packages/art4/rector-bc-library

And feel free to give me feedback.

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: https://packagist.org/packages/art4/rector-bc-library

And feel free to give me feedback.

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: https://packagist.org/packages/art4/rector-bc-library

And feel free to give me feedback.

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: https://packagist.org/packages/art4/rector-bc-library

And feel free to give me feedback.

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. 🙄🔄
https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environment #Apple #Rosetta2 #macOS28 #backwardCompatibility #newMac #HackerNews #ngated

🍏🚨. 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... 📞🦖
https://support.apple.com/en-us/125142 #Apple #iPhone6s #tech #news #backwardcompatibility #HackerNews #ngated

🚀🎥 "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! 😂📉
https://twitter.com/xai/status/1943158495588815072 #Grok4Launch #BrowserBingo #XCorp #BackwardCompatibility #TechNews #HackerNews #ngated

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 ....

ClojureScript forks Google Closure to guarantee backward compatibility

https://clojurescript.org/news/2025-05-16-release

#HackerNews #ClojureScript #GoogleClosure #BackwardCompatibility #OpenSource #ProgrammingNews

A Modern PC With a Retro OS https://hackaday.com/2024/10/22/a-modern-pc-with-a-retro-os/ #backwardcompatibility #nativehardware #retrocomputing #parallelport #floppydisk #dos6.22 #News #doom #PS/2 #amd #dos #x86