rjhacks

3 ms·

1. 1.▲
   by rjhacks 2y ago

   Thanks for sharing, such an interesting approach! At my startup we're currently discussing licenses, this is very inspiring. I have a follow-up question! The reasons for OSS you list include "Bus-Factor", "Longevity&quot
2. 2.▲
   by rjhacks 6y ago

   For the CoScreen team, I'm curious how the existing competition ( https://tuple.app/ , https://screen.so/ ) factors in to your decision to build/position this - do you believe you have a different vi
3. 3.▲
   Loon’s Final Flight(blog.x.company)

   2 points by rjhacks 6y ago|0 comments
4. 4.▲
   by rjhacks 6y ago

   I understand it's exciting to see introductions of new machine types and new GPUs, but for it to mean anything Google should instead get its house in order on the GPUs they already offer. Getting an n1 instance with a Tesla T4 GPU in a
5. 5.▲
   by rjhacks 8y ago

   How much CPU is allocated to a Cloud Run (not-on-GKE) instance while a request is active? I see that memory is configurable (up to 2G), but no word about CPU... I have a compute-heavy and bursty workload that I'd _love_ to put on Cloud
6. 6.▲
   by rjhacks 9y ago

   This article, linked from the one discussed here, seems solid: https://www.bmj.com/content/347/bmj.f6698
7. 7.▲
   by rjhacks 9y ago

   I think the use case where the per-config-request pricing model could break is with serverless (like Lambda or Cloud Functions or ...). Secret management there is super important, and your solution looks great, except that what makes these