bonsai VS sourcegraph

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

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

Despite their shitty rug-pull <https://github.com/sourcegraph/sourcegraph/pull/53345>, I do really like Sourcegraph and one doesn't (currently?!) need to be logged in to use it: https://sourcegraph.com/search and they have a handy rewrite pattern such that one can just plug the repo path into the URL for quick searching e.g. https://sourcegraph.com/github.com/JetBrains/intellij-commun...

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...