Viewing profile — hthrowaway5
hthrowaway5
HN member- Joined
- Sat, May 14, 2022, 12:20 AM UTC
- HN karma
- 181
- Public activity
- 25 items
- HN profile
- View on Hacker News ↗
About hthrowaway5
No profile information was provided.
Recent public activity
-
comment
Comment #31423307
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 produ…
-
comment
Comment #31421868
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 inco…
- comment
-
comment
Comment #31421278
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 ye…
-
comment
Comment #31418637
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…
-
comment
Comment #31418575
that and dreamforce (over and over again)
-
comment
Comment #31418528
> 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 mont…
-
comment
Comment #31418253
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 …
-
comment
Comment #31418231
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 secr…
-
comment
Comment #31418159
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 …
- comment
-
comment
Comment #31391849
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. Troubl…
- comment
-
comment
Comment #31391717
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…
-
comment
Comment #31378785
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?…
-
comment
Comment #31378703
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 bac…
-
comment
Comment #31378658
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 i…
-
comment
Comment #31378610
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 …
-
comment
Comment #31378440
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." Sell…
-
comment
Comment #31378361
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 wo…
-
comment
Comment #31374260
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 …
-
comment
Comment #31374247
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.
-
comment
Comment #31374048
* 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 passwo…
-
comment
Comment #31373955
(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'…
-
comment
Comment #31373909
(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 …