Live data from Hacker News

An Update on Heroku

heroku.com

311–320 of 366 posts

Re: An Update on Heroku

#311

Earlier quoted context omitted.

They’re not competition if you own them! Typepad continued for over a decade after it was purchased. Auth0 is still in maintenance mode afaik. It can last as long as revenue pays for the FTE to maintain it, or until corporate reallocated the FTE to higher revenue-per-FTE-hour opportunities.

Auth0 still has a ton of people working on it at Okta. If they’re facing execution problems, it’s not due to a lack of resources.

Auth0 and Okta serves two different market segments. You’d use Autho0 for your customers and Okta for your employees.

Re: An Update on Heroku

#312
post #237

As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irrelevance. Salesforce gave Heroku a ton of funding to build out a vision that was way ahead of its time. Docker didn’t even come out until 2013, AWS didn’t even have multiple regions when it was built. They mostly served as an investor and le…

> people more concerned with process than results Sounds like something Steve Jobs observed at apple https://youtu.be/l4dCJJFuMsE?si=QOCBUqcUPWu8AsAX

Link with spyware removed: https://youtu.be/l4dCJJFuMsE

Re: An Update on Heroku

#313
post #301

Earlier quoted context omitted.

This! It absolutely boggles my mind that nothing else exists to fill this spot. Fly and others offer varying degrees of easier-than-AWS hosting, but nobody offers true PaaS like Heroku, IMHO.

The Heroku style of PaaS just isn't very interesting to most large businesses that actually pay for things. The world basically moved on to Kubernetes-based products (see Google and Red Hat)--or just shutdown like a lot of Cloud Foundry-based products. Yes, many individuals and smaller shops care more about simplicity but they're generally not willing/able to pay a lot (if anything).

It seems like you’re right, but it’s strange that the data world seems to be moving in the opposite direction, with PaaS products like Snowflake, DataBricks, Microsoft Fabric, even Salesforce’s own Data Cloud eating the world.

Re: An Update on Heroku

#314
post #237

Earlier quoted context omitted.

> people more concerned with process than results Sounds like something Steve Jobs observed at apple https://youtu.be/l4dCJJFuMsE?si=QOCBUqcUPWu8AsAX

Link with spyware removed: https://youtu.be/l4dCJJFuMsE

Spyware?

Re: An Update on Heroku

#316
post #139
post #10

"We know changes like this can raise questions, and we want to be clear about what this means for customers." Proceeds to not be clear about what this means for customers.

If any Heroku customer is reading this and not immediately going "we need to move off Heroku ASAP" all future problems are their own fault.

I get what you're saying but the onus is (and should) definitely be on the company to inform customers - and there's many laws to that effect.

Re: An Update on Heroku

#317
post #241

Earlier quoted context omitted.

I'm just going to chime in here and say thank you, there still really isn't in my mind a comparable offering to heroku's git push and go straight to a reasonable production I honestly find it a bit nuts, there's offerings that come close, but using them I still get the impression that they've just not put in the time really refining that user interface, so I just wanted to say thank you for the work you and the GP di…

I’ve been using Render for close to 5 years, and it’s excellent. I can’t think of anything I use that it doesn’t do as well or better than Heroku did last I checked.

[dead]

Re: An Update on Heroku

#318

As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irrelevance. Salesforce gave Heroku a ton of funding to build out a vision that was way ahead of its time. Docker didn’t even come out until 2013, AWS didn’t even have multiple regions when it was built. They mostly served as an investor and le…

I worked with some of the folks from there, and honestly you make it sounds like tech debt is inevitable consequence haunting projects from year one. I disagree, I think the folks just did a sloppy job of "let's bungee strap it all together" for speed, instead of more serious planning and architecturing. They self-inflicted the tech debt on them and got drowned in the debt interest super fast.

There's someone out there who built the scalable version of Heroku at another garage startup. But we never heard of them because Heroku beat them to market.

Re: An Update on Heroku

#319
post #301

Earlier quoted context omitted.

The Heroku style of PaaS just isn't very interesting to most large businesses that actually pay for things. The world basically moved on to Kubernetes-based products (see Google and Red Hat)--or just shutdown like a lot of Cloud Foundry-based products. Yes, many individuals and smaller shops care more about simplicity but they're generally not willing/able to pay a lot (if anything).

It seems like you’re right, but it’s strange that the data world seems to be moving in the opposite direction, with PaaS products like Snowflake, DataBricks, Microsoft Fabric, even Salesforce’s own Data Cloud eating the world.

PaaS has always been this thing that isn't pure infrastructure or pure hosted software that you use as-is. Salesforce has something over 100K attendees of partners and users to its annual conference. It's always been this in-between thing with a fairly loose definition. I'd argue that Salesforce was long a cross between SaaS (for the users) and PaaS (for developers). You can probably apply the same view to a lot of other company products.
Post reply on HN