We used `pgdog` as a proxy during a recent database backend migration (Heroku -> EC2 -> RDS) and it was much smoother than PgBouncer. Really nice seeing more things in this space, and having the team's work recognized.
> In this case I have first hand knowledge since he pitched me on the idea: would Sidekiq, being a big sponsor of Ruby Central in the past, be interested if rubygems could somehow use the remote IP to identify the companies downloading the sidekiq gem so I could use that to upsell those companies
TBH the whole thing is pretty opaque. There are a lot of accusations floating around. It's pretty easily to capitalize on "Big evil shopify is making a takeover", but I suspect there's a lot more happening behind the scenes.
I remember this differently. SVN had great _branching_ but horrific merge support. They resisted improvements to merging, because they wanted something theoretically perfect.
Git came along with great merge support and the entire world loved it.
For calculator languages, I think there are several choices. Depends a bit on what you know, and what you need...
Frink (https://frinklang.org/) has been around for ages, and is rooted in physical unit conversions
Calca (http://calca.io/) has come up a handful of times. It looks pretty reasonable
R, if that's your flavor
Anything with a REPL. Though the OP suggests these are cumbersome, I'd counter argue that anything you know well is usually more efficient than learning something new.
A very long list of commercial tools: Matlab, Mathematica, WolframAlpha, STS, SAS, etc
We're a small startup building device management tools. We believe strongly in https://honest.security and are trying to bring these principles to how companies think of security and their employee computers.
We're looking for software engineers to work on our endpoint agent. It is entirely open source and written in go.
For AWS and GCP you can setup cross-project permissions. I've run a single project of secrets, which grants specific access to various service accounts
This feels like a somewhat narrow and biased comparison. It is focused around getting startup credits, and while that's important, I think it's a very limited view of onboarding.
Better would be to think about what the general initial usability of these services are. How easy is it to spin up the compute load? Create reasonable IAM policies? Debug problems?
My own experience (and bias) is that while AWS has vastly more features, GCP is much more usable. The latter feels like a coherent setup with projects and IAM. AWS always has a surprisingly amount of work around org accounts and IAM setups.
So maybe it's faster to get AWS credits, but it's much harder to make use of them.
Implements two dialects. An original one compatible with the inspiration, and used in some of our earlier product. And the replacement (syllables above) which is alphabetically sortable.