We do have a pricing page however it's geared towards giving an estimation on how much additional we can generate for a merchant with our average improvement against industry average failure and recovery rates.
We tailor pricing to provide a double digit ROI since there's a huge range between each businesses metrics. For example, take two businesses with $4M MRR and one has a payment failure rate of 25% ($1m/mo) and the other has 5% ($200k/mo). We've found that Merchants are happiest with this approach as we also provide a free payment audit upfront to benchmark historical performance, estimate our impact, and set price. This way the benchmark, targets, and ROI are completely transparent.
Very cool! As someone pointed out, your github repo says it was archived: https://github.com/porter-dev/porter-archive Naively, I would think Porter cloud would just be a managed version of your porter-dev/porter-archive. Could you talk about how it's a different product than before? Did the code base change significantly?
Our archived repo functioned as more of a Kubernetes-centered dashboard - Porter Cloud is intended to offer a more complete PaaS experience including spinning up non-application resources like databases
Thanks! Followup question: After you "eject" the app and start paying AWS directly but continue using porter, is the experience more like the archived repo? Or, is it still Porter Cloud just with different billing underneath?
The experience after ejecting to your own AWS account is the same as Porter Cloud. If you're using something like Postgres on Porter Cloud that also gets switched to wrap RDS under the hood in the AWS case
FWIW, I've been using Elixir in production since 2016 and haven't found I've needed to learn any erlang. For context, we use Elixir for our backend and serve around ~100/rps over websockets. We've integrated Elixir into Stripe, Segment, Google, and Xero and haven't found we've needed Erlang libraries for any of those integrations or any of the other parts of our code base.
> Elixir when they invariably stumble across the things in erlang — libraries and the like. I'd hoped I could avoid it myself, but it's too interdependent.
This hasn't been true in my experience. I'd be curious to hear which Erlang libraries the OP has been using.
If nothing else you're likely to run into ETS, it's really nice and easy to use. But even still, the calls are pretty easy to make, and the docs are good. You don't really even need to understand any Erlang syntax, it's just built into OTP.
We had looked into Quill but decided to use Threads.com. Considering how inconsiderate Quill's shut down was, it was a good decision for that reason alone.
For anyone looking at alternative for threaded messages and find Slack's threads insufficient, our team loves Threads. We looked at a few others (Zulip, Twist) and landed on Threads about 2 years ago. Since then, the product has gotten better and better.
Also, haven't posted to HN much -- is this an appropriate thing to post on a thread like this?
As for training people, I taught my non-technical co-founder Elixir for some backend scripts he needed to write. He found it much simpler to pick up then Javascript or Ruby and his code was idiomatic rather quickly.
As for the IDE support in VSCode, I've found ElixirLS[1] great. I do have to restart it sometimes (delete the .elixir_ls folder), but that's a small cost to pay for a pretty great experience.
After spending years in RoR in multiple code bases, I find Elixir code bases to be easier to debug and libraries easier to grok. Without the mutable state of OOP, I don't find myself asking, "Where is this state coming from and when/how was it set?" Of course, macros can be hard to follow, but I still find an Elixir library more straight forward than a Ruby one.
We've also experience the great performance and reliability shared by others on this
We haven't had difficulty finding the right libraries even though the ecosystem isn't as mature as Ruby or Javascript.
I still have to occasionally grab my laptop to keep its fans from taking it airborne, it still crashes occasionally, requiring nuking .elixir_ls (and holding onto the laptop again), and while it hasn't happened recently, I've had situations where I'd get weird errors for code that should be fine, also requiring me to delete .elixir_ls to get rid of the warnings.
That said, I don't really mind, but then I perhaps don't care as much about IDE-ish features. I've also been doing more and more work inside LiveBooks, and those don't even have vim keybinding!
I'm glad to hear this! Using Remirror worries me because it injects an abstraction between our code and PM.
However, when I look at your docs, it's not clear it's a different in approach from Remirror. The imports are all from bangle.dev which makes it seem like the same approach.
I would love to see a doc explaining the "API overhead" and how to use PM directly. I want to feel confident I can easily drop back down to PM if Bangle doesn't have a feature I need or implements it in a way that won't work for our use case.
Really excited to see this approach! Shared PM plugins are a great idea!
I had a similar experience with Atlas. At least 1.5 years ago, Atlas felt like a enterprise company trying to do a SaaS. They used the same sales person driven approach I associate with enterprise sales. mLab just felt far more developer focused.
We also left compose but left to move to mLab. When Compose was still MongoHQ, we were really impressed by their support. In the last few years, we became incredibly unsatisfied. mLab has been awesome and responsive. I hope the move to Atlas doesn't cause their support to change.
In the comments, you mention how Quill is extensible. Does Quill's extensibility enable the creation of a hierarchical level that resembles an HTML <section> element? From what I can tell, Quill/Parchment divides documents into block blots, inline blots, and embedded blots[1]. If I wanted to create a group of block blots, could that be done with Quill? In HTML, this would look something like:
Is the pricing transparent and, if so, what is it?