martin-g commented on PR #1093: URL: https://github.com/apache/wicket/pull/1093#issuecomment-2639873447
> I'll wait for what the final decision will be: Jakarta or JSpecify. For me both are meh. - The annotations will add a lot of noise - The changes will make cherry-picking harder, unless someone volunteers to backport them to 9.x too - I am not coding Java since several years (happy user of `std::result::Result<T, E>`!) but in my past experience the lack of JSR-305 usage and NPEs caused by Wicket APIs was not a (big) problem But others decided to use it in Wicket then I'd vote for JSpecify. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
