211–216 of 216 posts
Earlier quoted context omitted.
That phrasing doesn't rule out an issue on your email server's end, like the email could have bounced. (Though I'm guessing that's unlikely.)
Would be surprised if that was this case - vanilla GSuite setup.
Earlier quoted context omitted.
So you're in favor of companies breaking their terms and conditions at will? I think that would cause quite a lot more outrage and problems.
Contracts can be amended when all parties agree on a change.
Earlier quoted context omitted.
> or a hobby or a one-off project I don't want to pay $5 / month indefinitely to host a weekend project. I don't want to deal with the complexities of hosting a weekend project myself. I've done plenty of that. I just don't want to end up spending $100-200 / month to host a lifetime of weekend projects and experiments.
Then you can get a raspberry Pi and host it in your closet.
That involves port forwarding, figuring out something like dyndns, and whatever I need to share domains on a single IP.
Earlier quoted context omitted.
> I've never had them wipe a database on me, Give it time, apparently ;) If you're like me and are really into ease of use, I really endorse Digital Ocean. People don't seem to use it in Big Important Companies, but I never had a problem with anything I hosted there when I was my last, medium-sized company, and everything was so easy to manage in the GUI without having to learn proprietary APIs and whole stacks of in…
DO is also good and less restrictive for a new user than aws (I.e. getting more resources). I remember having to beg to get more than 1(or 2) servers at aws as a new user. I haven't looked recently but does DO have the heroku click to add resources and git push to deploy offerings?
Earlier quoted context omitted.
I assumed the value prop of being on Heroku in 2023 was purely "not having to do the pain in the butt to migrate your legacy app that you made on Heroku in the pre-2010 era" - in other words, I would be really shocked if Heroku got significant new business or any growth at all, now that it's just expensive AWS with some basic CI integration points. I also assume Salesforce only bought them as a cash generator and has…
"Pre-2010"? Heroku only launched in April 2009. So I would assume the vast majority of current customers are not actually from a "pre-2010 era". Heroku didn't even have a postgres add-on until November 2010 -- the salesforce purchase went through in Dec 2010. In fact, the heroku "golden years" were mostly during the early salesforce period. (Heroku put matz, creator of ruby, on staff in July 2011; there was no Heroku…
> it requires a lot lot lot less in-house expertise and management hours than AWS
Yeah, you're not wrong there. I do worry though that it's still too complex to really trust someone with no devops bg to be fully responsible for, and at the same time, it's so outmoded (just meaning, it's not that popular now besides for legacy projects) that you aren't going to find a lot of good candidates who are expert with Heroku compared to expert with AWS.
So to me, Heroku is a gamble that you can get by indefinitely with only what you(r existing eng staff) know how to do in Heroku. Which for some projects, maybe that's a decent gamble for the payoff of easier admin in the short term.
> if you do consider them just "AWS with some CI integration" then I guess they would have been from the start? What would have made that true now if it wasn't then?
Yeah good point -- Let's see if I can try to explain my claim better. I think in 2009 using AWS was completely inelegant in every way, it was pretty barebones and basically just "Rent an EC2 server and do whatever you want, good luck." Heroku had a unique (at that time) approach which made cloud hosting much simpler and more abstract. AWS today at least offers a few ways you can host an application on AWS while doing less server maintenance than you'd have needed in '09. Infrastructure As Code is also something I think has a lot of popularity today that wasn't really a thing in 2009, and Heroku if I remember correctly, isn't really about that. So there isn't as much repeatability on that platform, it's more "click around and build your stuff out in the GUI." Which again, is cool in the short term to bootstrap, but can be painful at a bigger scale.
Earlier quoted context omitted.
I assumed the value prop of being on Heroku in 2023 was purely "not having to do the pain in the butt to migrate your legacy app that you made on Heroku in the pre-2010 era" - in other words, I would be really shocked if Heroku got significant new business or any growth at all, now that it's just expensive AWS with some basic CI integration points. I also assume Salesforce only bought them as a cash generator and has…
> Salesforce on bought them as a cash generator As an early Heroku employee, this gave me quite the chuckle.
I just imagined Benioff going "Cool, we can buy this and continue to collect the checks every month, while not developing the UI or integrating it in any way into our business." Basically the same thing they did with Exact Target.