hthrowaway5

6 ms·

1.
by hthrowaway5 4y ago
I'm simply telling you Heroku is not a stable platform that you can trust. It's up to you to figure out what to do. I haven't offered any solutions. Just because it's a slick product to get going doesn't mean that y
2.
by hthrowaway5 4y ago
I wouldn't move off of Heroku because of the incident. I would move off of them because of their response to the incident. They plainly lied. Responses take weeks and are very incomplete. They have so few people they can't possi
3.
by hthrowaway5 4y ago
tl;dr: Heroku is taking customers away that if competitors had it: they would be able to receive more capital It's not unlike Google Search. Google Search has atrophied over the years but because it's still the best in the market,
4.
by hthrowaway5 4y ago
From the email: > We value transparency and wanted to notify you of an issue affecting your account. My guess is they sent it to users with pipelines that have env vars. It's funny since this sentence demonstrates they don't
5.
by hthrowaway5 4y ago
that and dreamforce (over and over again)
6.
by hthrowaway5 4y ago
> At Salesforce, we understand that the confidentiality, integrity, and availability of your data is vital to your business [...] Hey Bob, why didn't you tell your customers a month ago to rotate their creds just to be safe? This is
7.
by hthrowaway5 4y ago
Well hopefully once it's gone the competition will be able to get more market share to build quality product. Heroku has been starving the entire ecosystem for years. I don't have experience with any other PaaS's so I can&#x2
8.
by hthrowaway5 4y ago
The lie was: > We also wanted to address a question regarding impact to environment variables. While we confirmed that the threat actor had access to encrypted Heroku customer secrets stored in config var, the secrets are encrypted at re
9.
by hthrowaway5 4y ago
Yep, they outright lied about env vars. Incredible. It pains me to see even occasional defenders of Heroku. They're not the company they were 10 years ago. They've been gutted and left for dead years ago but the product was so go
10.
by hthrowaway5 4y ago
At one point (a very long time ago now) it was declared that Dogwood was the future and as a result Go would be the language of choice at Heroku and Erlang would be no more. Trouble is that Erlang ran all the important Cedar code (it might
11.
by hthrowaway5 4y ago
As someone that was a very active Heroku user for years and then worked there for years: I wouldn't trust it as my host. There is nowhere near enough people maintaining it in order to have confidence it'll run without reliability
12.
by hthrowaway5 4y ago
You may not have been happy with pricing but it really wasn't our reason for failing. We made plenty of money, see our former CEO's comment here: https://news.ycombinator.com/item?id=31373300 I bet if we had 10x
13.
by hthrowaway5 4y ago
The only way they're going to succeed is if sfdc quadruples (or more) their headcount. We were struggling with product development and maintenance with the skeleton crew we had back in 2015 and probably had 3x as many people then.
14.
by hthrowaway5 4y ago
You support folks were absolutely stellar. Great at working with customers but also adept at coding enough to resolve an incredible amount of customer problems. If anyone is ever in a position to hire support staff and you see "Heroku&
15.
by hthrowaway5 4y ago
Most of their attrition is due to the slow rate of product improvements. So yeah, it's demoralizing for sure. I've heard this as a reason for leaving for almost a decade though so it hasn't been a new problem but it seems to
16.
by hthrowaway5 4y ago
Strange to me that you put Dropbox on here since they've really struggled to succeed on their own. I think Steve Jobs was right when he said it was a "feature, not a product." Selling to Google or Apple I think would've
17.
by hthrowaway5 4y ago
I agree with you. There is something about Salesforce in particular I feel people don't trust to be a good steward of acquired products. I don't feel it's deserved even though I worked for an acquired company that certainly
18.
by hthrowaway5 4y ago
Agreed. Heroku was an incredible success but using it in 2022 would be downright negligence. (Although I would argue that Salesforce was also responsible for creating most of what we love about Heroku. That acquisition happened far ea
19.
by hthrowaway5 4y ago
12 years ago! Heroku of 2010 was a success. Heroku of 2015 was a success. Heroku of 2022 is a zombie of its former self headed straight towards implosion.
20.
by hthrowaway5 4y ago
* They seemingly can't recover from this GitHub debacle (it's been a month without GitHub Sync). * They had a massive security breach where core-db was breached. Hashed user passwords and encrypted env vars were leaked. (And a hel
21.
by hthrowaway5 4y ago
(Former Herokai) Heroku is beyond the point of recovery at this point (barring a sale to Github or something). Those dedicated engineers need to give up because at this point they're harming everyone: * The industry – suffering because
22.
by hthrowaway5 4y ago
(Former Herokai) It is definitely not false but you misunderstood what they meant. You understood it as running sfdc code on Heroku which is not happening—but was proposed as part of Shinrai (a failed project). What has happened is many