Talking with Tom Dale about Ember FastBoot and the Return of Scrappy JavaScript

Tom Dale with Terence Lee and Matt Creager

Last week, Terence Lee and I caught up with Tom Dale at EmberConf to talk about FastBoot, when you should avoid native apps, and why JavaScript on the server and the browser might start to converge. Check the end for the full recording!

So let's start with the drama, would you say Ember has declared war on native apps? [laughs]

[sigh] Yeah. Yeah, I think that's fair. Yeah. Sure. Why not? Let's go with that.

A lot of other frameworks, take this approach of bringing web technologies and dropping them into native experiences - React Native being the prime example. It seems that Ember wants to bring back the glory days for web technologies - is that right?

Yeah, absolutely. I don't have anything personal against native apps. I use a lot of them, and I think that there are a lot of situations where native apps provide a better experience. And I don't care at all about what technology you use. I care about the user experience.

Read more →

Sunsetting Heroku’s Legacy Platform API (v2)

Two years ago we released the Heroku Platform API (v3), providing a supported way to automate and instrument Heroku and making it even easier for you to build new products. Today we are deprecating the legacy, unofficial version of the API that preceded it (v2), as its usage is limited and we are focusing development on the newer, officially-supported API.

Read more →

React, Ruby and CI: An Interview with Matthew Eckstein

Matthew Eckstein is the VP of Engineering for charity: water. For more information, visit: www.charitywater.org. Read our charity: water customer story to learn more about how Heroku has helped their organization deliver clean water to millions of people around the world.

Tell us a bit about charity: water

charity: water is a non-profit organization that brings clean and safe drinking water to people in developing nations all around the world.

We rebuilt our online fundraising and donation platform on Heroku and are super excited to share our story today, March 22nd on World Water Day.

When we first moved to Heroku, we decided to rebuild our system from the ground up. The engineering team was already familiar with Heroku, which made it an easy choice.

Read more →

Heroku Behind the Curtain: Patching the glibc Security Hole

If you’re a developer, it’s unlikely you’ve ever said "I wish I could spend a whole day patching critical security holes in my infrastructure!" (If you do, we’re hiring). And if you’re running a business, it’s unlikely you’ve ever said “Yes! I would like my developers to lose a day’s worth of feature-building on security patches!”.

At Heroku, we believe you shouldn’t have to spend the time required to patch, test, and deploy security fixes. Because of that, some of Heroku’s most important features are ones you never see: we keep our platform reliable and secure for your apps so you don’t have to.

Recently Google Security and Red Hat both discovered a high severity bug in a fundamental system library—glibc. This library is in common usage across the internet. If a server with a vulnerable version of the library were to make a DNS request to a malicious resolver, the DNS server could potentially execute code on the system making the request.

Read more →

Finally, Real-Time Django Is Here: Get Started with Django Channels

Django Channel header

Today, we're thrilled to host Jacob Kaplan-Moss. Jacob's a former Herokai and long-time core contributor to Django, and he's here to share an in-depth look at something that he believes will define the future of the framework.

When Django was created, over ten years ago, the web was a less complicated place. The majority of web pages were static. Database-backed, Model/View/Controller-style web apps were the new spiffy thing. Ajax was barely starting to be used, and only in narrow contexts.

Read more →

Browse the blog archives, subscribe to the full-text feed, or visit the engineering blog.