|
| 1 | +--- |
| 2 | +title: "Silly Project Ideas" |
| 3 | +date: 2025-01-10T21:28:12-08:00 |
| 4 | +tags: |
| 5 | +- dev |
| 6 | +- go |
| 7 | +- beam |
| 8 | +- prism |
| 9 | +- hobby SDK |
| 10 | +categories: |
| 11 | +- Dev |
| 12 | +- Hobby SDK |
| 13 | +--- |
| 14 | + |
| 15 | +Here are some weird project Ideas I'd love to try if I ever find the time. |
| 16 | + |
| 17 | +<!--more--> |
| 18 | + |
| 19 | +* Make [Prism](https://beam.apache.org/documentation/runners/prism/) "self distributed and scaling" using [Cloud Run](https://cloud.google.com/run). |
| 20 | + * Basically the idea would be to host an instance on Cloud Run, serving it's JobManagement service. |
| 21 | + * But replace the local docker execution with Cloud Run launches for worker container launches, connecting back to the parent prism instance for work orchestration. |
| 22 | + * The main prism instance can't scale, but the UI should be hostable without too much problem. |
| 23 | + * Could add Tailscale for more fun. |
| 24 | + * Entirely a fun hack without also adding a cloud persistence layer too. |
| 25 | +* Make [Prism] integrate with Kubernetes. Distributes work in the cluster. |
| 26 | + * Basically the same idea, but with Kubernetes operations instead. |
| 27 | + * Same problems. |
| 28 | +* Find the branch of the Go compiler that has the work for Memory/GC Regions, and have it store things into Cuda Unified Memory Instead to simplify GPU integration. |
| 29 | + * Totally wild endgame idea. Would need to actaully learn some Cuda and it's CGo bindings first. |
| 30 | + * In principle could be used to more naturally toggle GPU based work. |
| 31 | +* Heck, even just do my normal distributed ray tracer, but batch the rendering stage onto a GPU. |
| 32 | +* Try using opencv with BeamGo generally. |
| 33 | +* Actually finish the Hobby SDK. |
| 34 | + * Stateful Transforms - State and Timers |
| 35 | + * On Window Expiration |
| 36 | + * Real Windowing |
| 37 | + * Streaming Splittable-DoFns |
| 38 | + * Leverage Go 1.24 Generic Aliases to make the API more convenient. |
| 39 | +* And of course |
| 40 | + * Submit talk proposals to conferences. |
| 41 | + |
| 42 | +So might to potentially do. |
| 43 | + |
| 44 | +Never enough time. |
| 45 | + |
| 46 | +---- |
| 47 | + |
| 48 | +I think I'm not going to try too hard to post on Thursdays. |
| 49 | +Between the Frelard Run Club, and Pub Night, it's quite a packed day. |
0 commit comments