Chapter 11?
Slack _alone_ is enough to keep Salesforce profitable for decades to come.
181–190 of 590 posts
Chapter 11?
Slack _alone_ is enough to keep Salesforce profitable for decades to come.
TBH I'm surprised that it took this long to move to this! Back when Heroku first arrived, PaaS was a new idea. It was available ~2009, well before services like AWS Lambda existed. This was such a paradigm shift that no one knew what to think of it. It takes time to build trust around such a big shift. The best way to do this is to offer to try it for free. Hence, the Free Tier. People tried it, and were blown away b…
I can't remember what book it was that was I reading, working through some language/framework of the month. They had you register an account on GitHub, and then on Heroku. You'd push the chapter's exercise up there, deploy it, and then never look at it again. I always wondered how many millions of repos/apps were out there because of stuff like that.
Free apps will shut down after periods of no traffic, so these kinds of projects aren't costing compute, but i suppose there's some overhead in storage.
Earlier quoted context omitted.
Please let me know in the replies what you'd like to see at Fly that would make it as good, if not better, than Heroku. I recently started working at Fly to focus on making Rails & Ruby app deployments awesome, and of course Heroku set that benchmark almost a decade ago. I can't promise I'll get to everything, but I can promise that it will help me better prioritize what I should be focusing on to make Fly better for…
On the top of my list is being able to use a local repository and providing no credit card.
If you launch Fly from the CLI to test the free tier, you don't need a credit card. Obviously when you exceed the limits of the free tier, you'll need to provide a credit card.
fly.io is better anyway. Its a real shame how far salesforce dropped the ball on heroku
I mean, was there any sign to the opposite?
Reading the sentence "Salesforce acquires Heroku" basically reads to me as "Giant megacorp buys trendy internet-y company so their name appears in newspapers positively and they have a department where they can put their employees that are too smart for their current job and would otherwise quit".
I think they will support the $7/month hobby demos, right? Google and Oracle can afford to provide a free micro VMS, smaller companies like Heroku can not. Google and Oracle probably get good value for letting people have free, never expires, micro VMSs.
Earlier quoted context omitted.
It doesn't require a login when accessed using a private browsing window or a browser profile that hasn't been logged into Heroku before.
I wonder what purpose this particular dark pattern serves? Edit: Perhaps accounts that authenticate on this page, and that are also taking advantage of free tiers, are being segmented for upsell. It is at least an indicator they are interested enough to read this news.
I mean how much money could they possibly be losing from hobby dynos etc...
fly.io is better anyway. Its a real shame how far salesforce dropped the ball on heroku
Well shit. After the Heroku Dashboard issues I moved my OSS project demo instances and PR reviews process to Fly.io, then Render.com, then Railway, then back to Heroku because it was the only one that had a truly free and well integrated process. Sigh.
What would make the process more integrated on Render?
I think my primary issue with Render.com was the shared database for PR previews. The way I am setup on Heroku is I run a demo instance that resets hourly and build PR reviews from the Heroku Dashboard when necessary. All with no cost. The shared database makes the PR reviews effectively useless because of the need for the ongoing demo database.
I was also turned off by the default service plan being a non-free one. I got a surprise bill in my first month of testing this because I had not specified the free plan in the service configurations.
Also one of the weirdly nice things from Heroku was the ability to run cron jobs for free. Lacking that I had to create a GitHub Action to handle resetting the demo data every few hours. Just an additional pain.