News for hackers. Stuff that matters.
Re:Log4j: The pain just keeps going by aclatuts on Wednesday July 20, 2022 @02:02PM (#32169751)
I find Python is very prone to a lot of breaking changes even with minor version changes. And not just that, even minor versions have to match up specifically with another libraries minor version. It seems to be a community or ecosystem problem with Python, which is why I avoid Python as much as possible.

In every other ecosystem when minor version are updated there are very rarely issues, and there are little issues with compatibility with minor versions of libraries.

Re:Log4j: The pain just keeps going by btilly on Wednesday July 20, 2022 @02:45PM (#32170377)
My (somewhat dated) experience says that Ruby is all the way worse than Python on this.

In part due to a culture that encouraged monkeypatching. With the result that what behavior you get depends on who last monkeypatched it. So a dependency 3 deep that loads the module you expected to load last suddenly causes the monkeypatch you were depending on to disappear...

Re:Log4j: The pain just keeps going by treeman79 on Wednesday July 20, 2022 @04:46PM (#32172084)
Monkey patching was the greatest thing ever. Until the community realized how bad it was. Don’t see it much these days
Re:Log4j: The pain just keeps going by skrtskrt on Wednesday July 20, 2022 @02:43PM (#32170340)
eh, people love to break stuff on minor version changes of Go libraries to
Re:Log4j: The pain just keeps going by wizofaus on Wednesday July 20, 2022 @03:34PM (#32171010)
At least you find out at compile time...