21–30 of 67 posts
Earlier quoted context omitted.
Have you considered a community Discord?
We considered Discord, but went with Slack (mainly because we have dedicated support channels for customers). If we provided a Discord, would that be more appealing to join?
B2C for developers is really something. Some junior in some huge org, is he going to put his AWS security credentials into a box and expense the $100 a month? Maybe.
It seems really against trend. You're making something for ultra-junior developers who are going to be asking ChatGPT (or whatever soon-to-be vendor LLM) for a solution, which can't interact with UIs. And how is your thing going to have more representation in a dataset than a docker compose file or whatever hackneyed idea is simple enough for this user to adopt?
> We offer many features that are hard to build in-house
I am just saying you should try asking ChatGPT with GPT4 for examples before you make this the premise. What was once super arcane is now just another blob of opaque bullshit Berkeley CS '23 is going to be copying and pasting into somewhere.
These look all the same. I honestly don't know how people choose one over the other. It's like roulette, gotta pick a random one.
Which ones deploy to your own cloud accounts?
I consider the "best-in-breed" tools with this shape to break into the following categories:
"Infra Abstractions": DuploCloud, Massdriver, Stacktape "PaaS in your own cloud": Nullstone, Zeet, Quovery, Porter, Architect.io, FlightControl "SDLC Platform for Teams": Coherence (withcoherence.com) - the key difference here is in how CI/CD (incl integration tests) are handled, how development environments are configured alongside other environments, and how production is segregated from other environments.
This a somehow both a crowded space and an emerging one. But we believe that even with the diversity of choice that there are clear reasons that most teams will by (vs. build) their internal dev platform in the future: namely the cost to buy vs. to build/maintain, and the productivity from better tools.
Is there ever going to be another Dropbox? B2C for developers is really something. Some junior in some huge org, is he going to put his AWS security credentials into a box and expense the $100 a month? Maybe. It seems really against trend. You're making something for ultra-junior developers who are going to be asking ChatGPT (or whatever soon-to-be vendor LLM) for a solution, which can't interact with UIs. And how is…
I do think that AI is going to have a massive impact on development including cloud infrastructure; however, we rarely see junior developers setting up cloud infrastructure because it is dangerous.
Our motivation is to make the cloud easier for all skill levels. In many organizations, this usually requires platform engineers or lead engineers that determine what works best with their technical strategy.
Our goal is to (yes, remove the arcaneness), but also remove the tedium and distraction from development.
Earlier quoted context omitted.
Which ones deploy to your own cloud accounts?
Kubernetes is kind of the intellectually honest, logical end point of this stuff.
However, Kubernetes is more a primitive for infrastructure rather than a tool to build automation workflows for software teams. Our focus is to complement teams that may or may not choose Kubernetes.
tbh, I have tried so many alternatives to this issue (as a Rails dev) and 'til today, I still find the oddest one of the all to be the only one straightforward enough to match the Heroku paradigm, that would be Hatchbox (which only dwells with Rails deployments).
I will give this a shot, but I'm skeptical. Also, I want to thank the Dokku team, since recently I tried a few deployments and while there was hiccups along the way, the platform has improved quite a lot since the last time I tried it.
Is there ever going to be another Dropbox? B2C for developers is really something. Some junior in some huge org, is he going to put his AWS security credentials into a box and expense the $100 a month? Maybe. It seems really against trend. You're making something for ultra-junior developers who are going to be asking ChatGPT (or whatever soon-to-be vendor LLM) for a solution, which can't interact with UIs. And how is…
Thanks for the feedback! I do think that AI is going to have a massive impact on development including cloud infrastructure; however, we rarely see junior developers setting up cloud infrastructure because it is dangerous. Our motivation is to make the cloud easier for all skill levels. In many organizations, this usually requires platform engineers or lead engineers that determine what works best with their technica…
So whom is this for?
Doesn’t this set up cloud infrastructure? Dangerous how exactly?
It’s not a tautology. Someone who can’t handle like, using AWS directly, is a junior developer.
Another perspective is the founderese is not very reassuring.
From a quick glance at your docs, it seems that you are mainly focussing on web facing applications.