Live data from Hacker News

Why I left Medium and moved back to my own domain

arslan.io

11–20 of 250 posts

Re: Why I left Medium and moved back to my own domain

#11
post #4
post #2

"Writing comments to Medium posts feels awkward because each comment is treated as a blog post." This is also awkward from the reader point of view. Trying to follow a comment chain on medium is frustrating as it only shows the first level, diving in switches pages, and often, a need to press a second "load all comments" button. Then the back button to wind your way back up. Is there some sound reasoning for why it w…

Maybe to have the UI less cluttered. Just assuming here.

They are probably trying to focus on the content first - and the discussion second.

It might be a resource issue, because of all the content publication outlets there are they have to make that the best.

Right now, someone can easily post a Medium article here, or on Reddit, and get two different discussions on the same content each with their own features and community standards - without mixing them or trying to define what it means to start a response thread on Medium.

Because Medium's focus is most likely on being a publication platform, they probably see comments and responses to comments as Medium articles within themselves within the context of that thread. The UI seems clunky in comparison to HN or Reddit, or even Digg, but that may be "the point." If so, I still think they got it wrong, but only because they need to more formally execute against this vision.

Today, authors who understand this paradigm right a "response blog post" and link to the one they are responding to and provide context before making a long form response. I think Medium is trying to capture this, but they haven't yet.

Re: Why I left Medium and moved back to my own domain

#12
post #6

I don't understand why people write programming blogs on Medium. I think that managing a live website with its own server (rather than only working on other people's projects) is a very important skill. If you don't want to manage WordPress, try a static site generator like Metalsmith: https://github.com/segmentio/metalsmith Deploy on Digital Ocean or Linode for $5/month. Free hosting options include Github Pages and…

Some people (like me) write programing blogs on medium because it's much easier to get an audience there then on your own domain. It has nothing to do with technical issues. Like it or not, often more people will discover and share medium articles than posts on a no-name domain.

Re: Why I left Medium and moved back to my own domain

#15
post #6

I don't understand why people write programming blogs on Medium. I think that managing a live website with its own server (rather than only working on other people's projects) is a very important skill. If you don't want to manage WordPress, try a static site generator like Metalsmith: https://github.com/segmentio/metalsmith Deploy on Digital Ocean or Linode for $5/month. Free hosting options include Github Pages and…

I did not know Netlify and looked it up. I found this image [0] on their features page. Is that a joke or does their cli tool really use left-pad?

[0] https://www.netlify.com/img/features/section-art/dev-tools.p...

Re: Why I left Medium and moved back to my own domain

#19

Using something like Jekyll to create a static blog lets you put it on AWS S3. For all but the highest traffic sites the bandwidth cost is trivial and you totally remove all the issues with uptime and securing a server.

Same applies to GitHub pages.

Re: Why I left Medium and moved back to my own domain

#20

Using something like Jekyll to create a static blog lets you put it on AWS S3. For all but the highest traffic sites the bandwidth cost is trivial and you totally remove all the issues with uptime and securing a server.

This is exactly how we publish our content. We are currently experimenting with Gatsby as well. We will see how it turns out.

https://github.com/gatsbyjs/gatsby

Post reply on HN