Embeds are a great feature of the Web that lets you include third-party content into your posts. Think YouTube videos, Google Maps, and more! All you have to do is copy and paste the embed code from the provider's website.
Searching for embed code can be tiresome, though. Each provider has their own way of exposing the code, so users are left to hunt for it. Wouldn't it be better if you could just copy the URL from the top of your browser and paste it into your post?
A discussion on GitHub this morning was the inspiration for this post. It addresses something I've been wanting to do in my software for years, but due to user demand, I haven't.
Why would I want to remove something that so many users seem to want? I'm glad you asked.
I believe software should be smarter than we expect it to be. People shouldn't have to think about resizing images when they're writing a blog post. They should just drag, drop, and continue writing.
So why is it that we expect users to resize their own images before uploading them? We've all been here before:
Uploads management is a concept I've always struggled with in Postleaf, but it's a necessary evil. Users have to be able to view and delete files they upload; but at the same time, I've never felt that it should be an integral part of the app.
Last night I had to face the fact that Postleaf isn't going to ship until it has a damn good Uploads Manager.
The first version of Postleaf was written in PHP and lives on as Leafpub. It's a beautiful piece of software that I'm very proud of, but I decided to move the project to Node.js for a few important reasons. This is by no means a knock on PHP, which will always have a special place in my heart, but more of a changing with the times realization.
If you've ever worked with Node.js before, you'll know that it's fast. Very fast. While PHP did get a nice performance boost in version 7, it still remains bloated with a huge number of core functions and extensions that seem to weight it down.