SummerOfCode2021 VS sandbox

https://summerofcode.withgoogle.com/ - sign up as an org, you have until the 21st.

I'm interested in Google summer of code event but missed it last year. I want to attend the event this year and notice that Haskell.org was one of the organizations. It sounds really exciting, I hope Haskell.org will participate in GSoC this year as well. But I have little experience with Haskell, I'm worried about how to write an expressive proposal when I don't even know which projects they will focus on. Can anyone give me so resources or suggestions about the following question?

I also encourage you to look into Google Summer of Code (GSoC).

OSS have benefited from Google Summer of Code, Google has released many fundamental libraries as OSS such as Guava for Java, Abseil for C++, etc. Many have criticized that Google never made money of a lot of its innovations, and instead had others build their own based on Google's shared information (Hadoop, and later all nosql databases, for a quick example; Docker came to be from open source innovations that Google put into Linux for their own container system). Even as Google has begun monetizing, they still open source core parts of their products (such as Kubernetes) for their benefit.

They actually do something like that. It's called Summer of Code.

Apply on their official page: Google Summer of Code

Read: https://summerofcode.withgoogle.com/

More at 👉 GSoC 2. The Linux Foundation Mentorship Program

if you don't land anything, maybe consider Google Summer of Code.

I maintain a project called Meshery and one of the new contributors (who came in to get a GSoC internship) literally asked if I could explain what Meshery is.

I've made a similar game: https://github.com/JMS55/sandbox, and it looks like we've had a lot of the same ideas :)

If you're interested in game development, you may enjoy playing around with Sandbox. It's a game I created where you place sand, water, acid, fire, etc and watch them interact.

> WebGPU is years away to become usable

As a counterpoint, I've been using WebGPU (through wgpu-rs) for the past 1.5 years. It's been a pleasure to use. For instance, here's the CPU-side code for a glow post-process shader using 4 render passes https://github.com/JMS55/sandbox/blob/master/src/glow_post_p....

I've considered implementing Sandbox using wgpu compute sharers (all the rendering is already done with wgpu). The reason I didn't is because I couldn't figure out how to make particles update in parallel - how to handle conflicts between two particles wanting to move into the same position, updating a particle that's supposed to be destroyed, etc. I'd love to get this working however. My last attempt was a the "multithread" branch where I tried to use rayon as a means of prototyping the game using parallel update logic.

Unrelated to a club, but you might enjoy looking at a game I built with Rust + WebGPU https://github.com/JMS55/sandbox.

Counterpoint: https://flathub.org/apps/details/com.github.jms55.Sandbox

Not a GSOC project, but my game Sandbox is open to contributions! https://github.com/JMS55/sandbox

Overflowing the stack: Use a Vec, or Box<[T; N]> (boxed array). A boxed array is a heap allocated array, where the box part just points to some data on the heap, so it's cheap to move around. Both are pretty much equivalent, boxed array is maybe slightly more faster/correct. Note that if you use a boxed array, due to some missing compiler optimizations, you'll probably just get a stack overflow anyways, as the compiler will first store the array on the stack, and then copy it to the heap. This can be solved with some unsafe code, such as in https://github.com/JMS55/sandbox/blob/master/src/heap_array.rs.