like vavr or lombok create too much dependency and coupling littered throughout our code base? If the library support is stopped one day, we'll have a hard time refactoring the whole app!
Is it better to avoid such libraries and use our own created utilities and standard utility classes provided by Java itself? Thanks.
One could also argue that using third party libraries allows you to focus on the core functionality of your app and let someone else maintain thirty libraries. Imagine rewriting a qrcode scanning library, all bug fixes would be on you and possibly result in you maintaining that code more than the core app
Обсуждают сегодня