An opinion about the future of dev.to and the failure of medium
There is 1, one, primary reason why dev.to wins out, IMHO, over medium: 'pay wall'. I can't speak for anyone else here but I've sometimes spent hours verifying and documenting articles I've posted on dev.to and medium alike. As of this date I've pulled any articles I've written on medium specifically because, when the articles became popular, they were pushed behind the dreaded pay wall -where no one can read them unless those persons pay medium. I've written hundreds of articles under many pseudo names over the years and I've seen this behavior over and over (from livejournal, deadjournal, myspace, facebook, masestedon, tumbler, ...the google blog thing, etc.). All of these sits end the same way: cannibalizing user/poster data for survival. I hope dev.to doesn't go the same route.
Let's face it. While we'd like to believe that magical faeries work behind the scenes to make dev.to great, the fact of the matter is that real people are working night and day to provide a forum whereby we, the content providers, ...provide content. As content providers we don't want to be bothered with advertisements and such -at least I don't. However, the real people working for dev.to need to earn a living wage -or, hopefully better. It's a business, not a charity. And as content providers we expect "some level" of respect from the company that hosts our content -or else we will find some other place to form a community.
With that said, in my 25 years of blogging experience -I never said I was a 'good' writer btw -dev.to has the capacity to give developers / programmers a place to express our ideas and thoughts. dev.to provides a place where we, the content providers, can post our new projects and ask questions about 'how' and 'what' relative to programming -even, sometimes, very personal experiences. And that is all NOT behind a paywall. But we, as content providers, have a burden to address: How can we keep dev.to in business, pay the people working for dev.to a fair wage, and retain our own sense of community?
In the previous sentence I mentioned "how do we, as content providers, "pay the people working for dev.to a fair wage". I can't emphasize the importance of this statement enough. If you have the chance to say, "I learned about this service from dev.to" do it! If you don't know how or you feel the opportunity was lost then do contact dev.to staff (imho) and ask how you might promote them better -or make suggestions.
Otherwise, our little community of wonderfully brilliant and amazing persons, and content thereof, will move, again, somewhere else... again. And that would suck. In my mind dev.to could/should be the first place I look for 'longer than basic' stackoverthrow style answers to things. The amalgamation of ideas and concepts and, most importantly, points of view, on dev.to is priceless!
Consider that some concessions might have to occur, hopefully not regarding privacy, which will help the company partake a larger footprint.
[disclaimer: I don't work for dev.to. I'm just posting my point of view.]