bonsai VS wundergraph

The engine's completely bespoke; I wrote everything from the memory allocators and the font rasterizer to the renderer and level editor.

Source code is available online, and there's a discord for those interested.

Github : https://github.com/scallyw4g/bonsai

Discord : https://discord.gg/hv8NWrGU

Project Repo : https://github.com/scallyw4g/bonsai

| Bonsai | Realtime 3D Voxel Engine | Seeking Volunteers/Contributors | Remote, Global

Last month I posted a 'real' hiring ad (with an actual salary). I got such an overwhelming response from Intern level candidates that I though I'd put the word out; I'm looking for contributors for an OSS project I work on. If this is an inappropriate venue for this ad, I'm happy to take this down.

Bonsai is a long-running passion project of mine that's recently reached a level of stability with which I'm comfortable including an additional contributor or two. The project is largely inspired by Handmade Hero, and the rules are the same. With very few exceptions, every line of code included in the project has been written by me. This includes everything from the standard library to the font rasterizer, the collision detection, and even a C metaprogramming language.

https://github.com/scallyw4g/bonsai

As you can imagine, there's a great number of things that could be worked on, and I'm very open to suggestions. That said, a few tasks relatively high on the to-do list are as follows:

* Make some games!

* Implement transparency in the renderer based on this paper : https://www.jcgt.org/published/0002/02/09/paper.pdf

* Implement an MP3 decoder

* Using the metaprogramming language I wrote, implement a GUI tool to introspect the engine data at runtime.

A few more .. ;)

I'm looking for anyone who is passionate about (or passionately learning about) low-level programming, graphics and/or compilers. If you're just starting out with these topics, I'm happy to be a mentor and help you stumble blindly down the path of becoming an excellent engineer. Working on Bonsai has been an absolutely amazing experience for me; it's literally changed my entire life, and I'd love to share it with other folks. If you're looking for a cool new project to work on, and don't need income from it, let's connect.

[email protected]

Obligatory buzzwords : C, C++, OpenGL, WebGL, WASM, 3D graphics, multi-threading

Anyhow, if it sounds like what you're after you can take a look: https://github.com/scallyw4g/bonsai

Code available : https://github.com/scallyw4g/bonsai/blob/master/src/engine/voxel_synthesis.cpp

I never really got graphql until I stumbled upon Wundergraph. (https://github.com/wundergraph/wundergraph). I have no affiliation with them except that I have been building an app with it. I'm honestly puzzled how it's not more popular. Maybe people are solving these problems in other ways? But I tried out a bunch of stuff: Vapor, Supabase, Hasura, etc. None of it simplifies building complex systems the way WG does.

I think their takes on graphql make sense: https://wundergraph.com/blog/graphql_is_not_meant_to_be_expo...

To demonstrate field usage metrics in Federation, I’ll be using WunderGraph Cosmo — a fully open source, fully self-hostable platform for Federation V1/V2 that is a drop in replacement for Apollo GraphOS.

The inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder match and what can I say, it's going great. We're focusing on enterprise GraphQL/API solutions (https://wundergraph.com) and I benefit from the networking and communication abilities of Stefan, while I answer all technical questions. Tldr, I highly recommend to team up with people who complement your skills.

GraphQL Gateway is primarily responsible for serving GraphQL queries to consumers. It takes a query from a client, breaks it into smaller sub-queries, and executes that plan by proxying calls to the appropriate downstream subgraphs. When we started our journey, there was only Apollo Federation in the arena, and we used it. Still, now you can look at other options (e.g. Mercurius, Conductor, Hot Chocolate, Wundergraph, Hasura Remote Schemas), compare benchmarks and decide what's important and preferable for your needs. The Gateway provides a unified API for consumers while giving backend engineers flexibility and service isolation.

I'm a big fan of tRPC. It's amazing how it pushed TypeScript only stacks to the limit in terms of DX. Additionally, it made the GraphQL community aware of the limitations and tradeoffs of the Query language. At the same time, I think tRPC went through a really fast hype cycle and it doesn't look like we're seeing a massive move away from REST and GraphQL to RPC. That said, we see a lot of interest in RPC these days as we've adopted some ideas from tRPC and the old NextJS. In our BFF framework (https://wundergraph.com/) we've combined file based routing with RPC. In addition to tRPC, we're automatically generating a JSON Schema for each operation and an OpenAPI spec for the whole set of operations. People quite like this approach because you can easily share a set of RPC endpoints as an OpenAPI spec or postman collection. In addition, there are no discussions around HTTP verbs and such, there's only really queries, mutations and subscriptions. I'm curious what other people's experiences are with GraphQL, REST and RPC style APIs? What are you using these days and how many people/teams are involved/using your apis?

You can check out the source code on GitHub and leave a star if you like it. Follow me on Twitter, or join the discussion on our Discord server.

If you like the work we're doing and want to support us, give us a star on GitHub.