5 ms·

We’ve been using this in production for the last three months and I can report it has been fairly smooth overall. Only very minor downtime, and we’ve received a

by jb1991 2y ago

We’ve been using this in production for the last three months and I can report it has been fairly smooth overall. Only very minor downtime, and we’ve received a lot of communication from our customers about it, they like it quite a bit. So that’s been nice.

talkinghead 2y ago
what have you been using it for?
- Waterluvian 2y ago
  Can’t speak for parent but we’ve been using it for our standard red ball use cases. The physics can seem a bit floaty, particularly with space or moonscape wallpapers, but overall it’s good.
  - Bluestein 2y ago
    Totally mission critical.-
mb2100 2y ago
when ours was down, we found clicking the ball helped... it immediately bounced up again.
- Bluestein 2y ago
  We find a soft re-bounce helps.-
toddmorey 2y ago
This has been a complete show stopper for my organization: https://github.com/nate-parrott/ball/issues/10 https://github.com/nate-parrott/ball/issues/10 We've submitted numerous GH issues and even tried to chase the developer down on LinkedIn. But he treats the project like a fun, novelty "gift" to the community and doesn't respect the SLAs that any repo maintainer needs to adhere to for my org to put their free code in production.
- adamors 2y ago
  Can’t tell if this is satire. Have you tried submitting a patch?
  - cevn 2y ago
    I can't tell if THIS is satire...
    - MonkeyClub 2y ago
      Everything is satire, if you're not the one on call.
  - toddmorey 2y ago
    100% fun satire + a loving shoutout to all the folks who maintain GH projects that start as a labor of love and a desire to share with the community. Please don't let the triage of silly demands like this fictional one destroy your spirit. More devs need to be good to OSS maintainers. Breaks my heart when I see folks treat public repos and GH issues as a service desk and not a collaboration! (Not saying anyone is doing that for this fun project, but a message I'll use any excuse to promote. Btw... that issue filed was I think someone genuinely helping the project.)
    - Bluestein 2y ago
      > More devs need to be good to OSS maintainers. Good point. (They are two and different things ...) > Breaks my heart when I see folks treat public repos and GH issues as a service desk and not a collaboration! This is also well said, and on point.-
- concurrentsquar 2y ago
  My team can't even evaluate Ball (as a tool for physical simulation of spherical cow-like objects): https://github.com/nate-parrott/ball/issues/9 https://github.com/nate-parrott/ball/issues/9 Currently, we are using Unreal Engine 5 to do our hundreds of architectural physics simulations - the major issue is that UE5 is very slow on *the EC2 instance* (we only have one 2048 core EC2 instance shared between the entire office; we used to use Vercel and Cloudflare but we had to sell our homes to suddenly subscribe to Cloudflare Enterprise (the CF sales guy told us that we would not be allowed to run a CF Worker for more than 30 days without it, even though we had a CF worker run for 37 years, and many of our CF workers have been running before the creation of CF (nobody knows why)) and a giant spike in our Vercel Cuda Function Invocations (for GPGPU compute on the Edge, allowing architects to view the collapse of their buildings with only ~53 ms of latency (compared to ~53 ms without Next.js))). Ball seems much faster (it can run on a Macbook Air), potentially allowing us to save at least several tens of millions of dollars per year on AWS costs.
barryrandall 2y ago
It needs write-ahead logging and better transaction isolation before it can be taken seriously for high transaction volume environments. Neat concept, though.
- indoordin0saur 2y ago
  We initially had this issue as well. So we put a small team of developers to work on the problem and were able to implement our own version of the metastore that supported optimistic concurrency and hidden partitioning. It has significantly improved reliability in stress tests (variable velocity ball bouncing in a hyper-dimensional click-cube environment). however, the larger size of our object store is increasing our monthly S3 costs.
  - Bluestein 2y ago
    > however, the larger size of our object store is increasing our monthly S3 costs. Classic, am affraid.- Tried R2? :)

by jb1991 2y ago

talkinghead 2y ago

what have you been using it for?

Waterluvian 2y ago
Can’t speak for parent but we’ve been using it for our standard red ball use cases. The physics can seem a bit floaty, particularly with space or moonscape wallpapers, but overall it’s good.
- Bluestein 2y ago
  Totally mission critical.-

mb2100 2y ago

when ours was down, we found clicking the ball helped... it immediately bounced up again.

Bluestein 2y ago
We find a soft re-bounce helps.-

toddmorey 2y ago

This has been a complete show stopper for my organization: https://github.com/nate-parrott/ball/issues/10 https://github.com/nate-parrott/ball/issues/10 We've submitted numerous GH issues and even tried to chase the developer down on LinkedIn. But he treats the project like a fun, novelty "gift" to the community and doesn't respect the SLAs that any repo maintainer needs to adhere to for my org to put their free code in production.

adamors 2y ago
Can’t tell if this is satire. Have you tried submitting a patch?
- cevn 2y ago
  I can't tell if THIS is satire...
  - MonkeyClub 2y ago
    Everything is satire, if you're not the one on call.
- toddmorey 2y ago
  100% fun satire + a loving shoutout to all the folks who maintain GH projects that start as a labor of love and a desire to share with the community. Please don't let the triage of silly demands like this fictional one destroy your spirit. More devs need to be good to OSS maintainers. Breaks my heart when I see folks treat public repos and GH issues as a service desk and not a collaboration! (Not saying anyone is doing that for this fun project, but a message I'll use any excuse to promote. Btw... that issue filed was I think someone genuinely helping the project.)
  - Bluestein 2y ago
    > More devs need to be good to OSS maintainers. Good point. (They are two and different things ...) > Breaks my heart when I see folks treat public repos and GH issues as a service desk and not a collaboration! This is also well said, and on point.-
concurrentsquar 2y ago
My team can't even evaluate Ball (as a tool for physical simulation of spherical cow-like objects): https://github.com/nate-parrott/ball/issues/9 https://github.com/nate-parrott/ball/issues/9 Currently, we are using Unreal Engine 5 to do our hundreds of architectural physics simulations - the major issue is that UE5 is very slow on *the EC2 instance* (we only have one 2048 core EC2 instance shared between the entire office; we used to use Vercel and Cloudflare but we had to sell our homes to suddenly subscribe to Cloudflare Enterprise (the CF sales guy told us that we would not be allowed to run a CF Worker for more than 30 days without it, even though we had a CF worker run for 37 years, and many of our CF workers have been running before the creation of CF (nobody knows why)) and a giant spike in our Vercel Cuda Function Invocations (for GPGPU compute on the Edge, allowing architects to view the collapse of their buildings with only ~53 ms of latency (compared to ~53 ms without Next.js))). Ball seems much faster (it can run on a Macbook Air), potentially allowing us to save at least several tens of millions of dollars per year on AWS costs.

barryrandall 2y ago

It needs write-ahead logging and better transaction isolation before it can be taken seriously for high transaction volume environments. Neat concept, though.

indoordin0saur 2y ago
We initially had this issue as well. So we put a small team of developers to work on the problem and were able to implement our own version of the metastore that supported optimistic concurrency and hidden partitioning. It has significantly improved reliability in stress tests (variable velocity ball bouncing in a hyper-dimensional click-cube environment). however, the larger size of our object store is increasing our monthly S3 costs.
- Bluestein 2y ago
  > however, the larger size of our object store is increasing our monthly S3 costs. Classic, am affraid.- Tried R2? :)