[wyager]

> friendly community (Code of Conduct, blogs, chats, podcasts, etc.)

In my experience, most of these things negatively correlate with stuff I actually want (like software quality or stability). It indicates a software ecosystem that exists mostly as an ersatz social outlet for a certain kind of person. The best softwares I use tend to have none of this stuff - maybe just a mailing list and a bug tracker.

[Jensson]

Yeah, boring technology requires boring owners to ensure that stuff like Python 3 wont happen.

[paulryanrogers]

So one (albeit large) backward compatibility break every few decades is too much?

I wonder how you'd classify JavaScript since the language is very backward compatible, yet the popular libraries built upon it break compatibility often.

[abernard1]

Amen. An abundance of these things signal (to me) developers concerned with themselves, not the technology.

People in this scene are going to be the first to switch languages/frameworks or introduce drama into what should otherwise be pedestrian problem solving exercises.

And on a more concrete note, when it's 3AM and your pagerduty is lit up like a Christmas tree, are blogs, chats, podcasts what you're interested in? No way! You want cold hard documentation and crusty "tell-it-like-it-is" engineers or consultants. They're seldom bubbly, but they command respect and get it done.