Ditching Medium
joshjahans.com
Ditching Medium
1–10 of 125 posts
Re: Ditching Medium
#2It's funny that you can clear cookies and reset the limit counter. Kind of annoying to have to do it often though.
Re: Ditching Medium
#3Programming blogs are kind of meh to me in general, and will be until the code-display aspects finally get ironed out.
Re: Ditching Medium
#4Programming blogs are kind of meh to me in general, and will be until the code-display aspects finally get ironed out.
Could you elaborate on the problems of displaying code in blogs?
Re: Ditching Medium
#5Programming blogs are kind of meh to me in general, and will be until the code-display aspects finally get ironed out.
Don't worry. We'll soon get this WebAssembly thing just right, and the situation will change. You'll love the code-display aspects, and the blog-display aspects will drive you nuts.
Re: Ditching Medium
#6On the topic of programming blogs, are there any libraries to automatically detect code snippets within text? I know there are some StackOverflow posts talking about possible approaches to this, but not sure if anyone has actually built an open source solution.
Re: Ditching Medium
#7Programming blogs are kind of meh to me in general, and will be until the code-display aspects finally get ironed out.
The solution is pretty clear to me but to my knowledge it doesn't exist and the economics of creating it are not that favorable.
You need to have a free github/publisher side cache which mirrors the public github repository of the code example. The example should be rendered server side without a javascript library for syntax highlighting / formatting. This way the author, or more likely a reader because the author abandoned the post a second after writing it, can make progressive updates and deprecations - sort of like stackoverflow where an answer can live on past the life of its author.
This is not a rife target for a start-up and most likely would have to be offered by a larger player. The service needs to be long-lived and reliable from an operational perspective and its pricing model is not clear as most developers would not pay a dime for it. Github is the most favorable target, I'd pay an extra couple dollars a month to "upgrade" my github account for this functionality. Github Gists are already pretty close to what we need but miss out on a few key features for use in independent blogs (presumably a rate limit and a limited scope that may be too narrow for an example, it might need a full repository).
Re: Ditching Medium
#8A downside of a pure growth first, monetization second strategy.
Re: Ditching Medium
#9I moved my old blog to a new domain name recently, and wasn't able to keep using Medium because they no longer support custom domains. So now I'm using WordPress for my blogging software and also using their hosting as well. That's too bad for Medium, because Medium's blogging software is superior in my opinion. They've just made a few boneheaded mistakes. My theory is that Ev Williams wants to create the next Twitter, and that's the reason behind his poor decisions. Williams should have just worried about creating the best blogging software and blog hosting solution and things would have kept humming along just fine. Greed can make people do silly things.
Ev, if you happen to read this: 1) bring back custom domains. 2) start charging a monthly fee for hosting custom domains like WordPress does 3) Create a native advertising service that publishes promoted stories into the main Medium.com story feed.
Re: Ditching Medium
#10A downside of a pure growth first, monetization second strategy.
I mean this is as much bad behavior on the part of users as it is bad behavior on the part of publishers. Users flock to products that are super polished and have tons of celebrity users (both made possible by huge fundraises), but then flip out when they're asked for $5 a month to pay for the service they're getting.