341–350 of 590 posts
Earlier quoted context omitted.
> At $49/m we could get a decent bare metal server for each of our apps. From where/with what kind of specs? $49/m sounds still well within VPS territory unless I'm wrong.
Hetzner has dedicated server auctions for ~35 USD/mo. All are in EU datacenters though. https://www.hetzner.com/sb
Unlike most of their competitors, I don't think I have ever heard of someone migrating to Heroku. Seemingly the only people who are still using it are using it because they started with it, usually with their free product. I'm no expert or anything, but it seems like a bad idea to cut off that funnel of future customers by eliminating that free product.
I never 'got' what heroku was all about , but i have been working with linode, aws and similar for more than 10 years. I find it pretty easy to spin something up in aws Otoh i know of a medium company (500 employees) that started in heroku and is moving to aws. Apparently they got to the top tier of the DB , and they've stumbled with several limitations by some lack of access .
> Open source programs: If you are a maintainer on an open-source project, and would like to request Heroku support for your project, contact the Salesforce Open Source Program office at ospo-heroku-credits@salesforce.com. Both the text version of this email (ospo-heroku-credits@salesforce.com) and the mailto it actually links (ospo@salesforce.com) appear to be invalid. I tried both and got: > We're writing to let yo…
I was just about to write an email too, I guess I won't... yet?
IF we want to take them at face-value that this is because of fraud and abuse (a trust/respect they have not earned IMHO, or rather they lost many years ago) then this a case of throwing the baby out with the bathwater. Otherwise it's some stupid MBA finding a way to save some money which will ultimately only speed up Heroku's demise. Either way the writing is on the wall. The Heroku that delighted us all is long dea…
> The downfall started before Salesforce Salesforce purchased heroku in Dec 2010. This was before, for instance, ruby creator Matz was an employee (he no longer is). Heroku had only existed for about 2 years when salesforce bought it. I think there are some other features we think of as core to heroku that actually weren't deployed until after the salesforce purchase. I think a lot of people remember it this way, but…
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…
1) We would love an equivalent to the HEROKU_RELEASE runtime variable: A strictly increasing int that is incremented with any change to the environment (deploys or env/secrets). It’s nice to have a single roll up for all of the knobs — “what was the state of the environment” — to tag in things like crash logs. (It’s also something we can’t easily tool ourselves.) 2) One click dashboard rollback button. Didn’t realize…
Earlier quoted context omitted.
That may all be true but I don't see any other way to frame this other than them throwing in the towel for the whole platform and/or conceding to other platforms that are better at spotting fraud/abuse. Require a credit card, require a deposit, allow free dynos for otherwise paying customers. Killing the whole program is a sign they don't care about growth, they don't care to be where a developer first launches a hob…
I don't think you understand how much fraud and abuse is in the hosting world.
IF we want to take them at face-value that this is because of fraud and abuse (a trust/respect they have not earned IMHO, or rather they lost many years ago) then this a case of throwing the baby out with the bathwater. Otherwise it's some stupid MBA finding a way to save some money which will ultimately only speed up Heroku's demise. Either way the writing is on the wall. The Heroku that delighted us all is long dea…
I don't understand this sentiment sometimes. There may be fraud and abuse. There may also be a material cost to a company whose detailed financial situation I'm assuming you are not purvey to. Someone doesn't need to be "a stupid MBA" to have made this decision (in fact my guess would be it involved many cross functional and leadership perspectives given its nature). Also, this is quite possibly something necessary f…
They might not have an MBA but it seems like a "bean counter" sort of decision. Maybe it's easier to just blame the MBAs than assess the whole leadership team's motives when we see short sighted strategies that improve profitability today and kill the product's ecosystem in the long term. I'm getting flashbacks of the Boeing documentary just writing this.
Earlier quoted context omitted.
It's worth mentioning there's a very vibrant piracy community that abuses heroku's free tier for torrent to direct-download bots and myriad other purposes. Thousands and thousands of fake accounts using the resources to their limits 24/7. It's likely also the reason Google's moved away from unlimited storage for educational institutions. I can understand why Salesforce has felt the need to restrict access.
i belatedly came to this realization that this is a common problem for all hosting (CDNs, because free bandwidth, and CI/CD, because free compute, and anything that offers free storage) companies. I call this the PCN problem - free tier hosting for anything means you eventually have to deal with Porn, Crypto, Nazis. everyone handrolls prevention measures, i once proposed an industry council where we swap tips, but ev…