explodingcamera
explodingcamera on Hacker News
Location: Stuttgart, Germany
Remote: Open to remote or hybrid, anywhere in the EU
Willing to relocate: Yes
Technologies: Rust, WebAssembly, TypeScript, React, PostgreSQL, Redis, Docker
Résumé/CV: https://henrygressmann.de/static/cv-henry-gressmann.pdf
Email: [email protected]
Portfolio: https://henrygressmann.de/work
GitHub: https://github.com/explodingcamera/
Availability: Starting October 2026
I'm a Software Engineer focused on backend systems, Rust, WebAssembly, and open-source software. Recently, I’ve been working on large-scale Rust backend infrastructure handling 80k+ req/s at AnyDesk, and building projects such as TinyWasm, a WebAssembly runtime (
https://github.com/explodingcamera/tinywasm), and Liwan, an open-source, privacy-friendly, self-hosted web analytics tool (
https://liwan.dev).
I'm especially interested in technically challenging backend/platform roles, developer tooling, infrastructure, WebAssembly, and open-source products - ideally with strong ownership over technical decisions and product impact.
Posted by
explodingcamera on Wednesday May 20, 2026 @02:24AM
from the luciofranco.com dept.
I guess that sounds like the normal web/progressive web apps/web archives (especially with the push to more platform APIs in browsers)? Also, Tauri uses the system's WebView2/Webkit runtime, so it essentially works like this already.
Location: Berlin / Germany
Remote: Yes, Hybrid preferred
Willing to relocate: No
Technologies: Rust / Typescript / Web / React / React Native / WebAssembly / Containers
Résumé/CV: https://henrygressmann.de/me
Github: https://github.com/explodingcamera/
Email: [email protected]
I just graduated from university (did my thesis on WebAssembly and Edge Computing), been coding my entire life, and I am looking for the next thing.
Some of my recent work:
- https://liwan.dev/ - Open source web analytics platform
- https://github.com/explodingcamera/tinywasm - Lightweight WebAssembly Interpreter
Location: Berlin/Germany (Remote/Hybrid)
Willing to relocate: Yes
Technologies: Rust, TypeScript, WebAssembly, Networking, Containers, Web (Astro, React, ...), React Native, ...
Résumé/CV/Contact: https://github.com/explodingcamera / [email protected] / https://henrygressmann.de / https://www.linkedin.com/in/henrygressmann/
As far as I can see from looking at their repo, Drizzle isn't a wrapper for Kysely though? You can use Kysely or other query builders with drizzle, but it has its own query builder too.
It seems to be wrapping drizzle, with astrodb just being a way to deeper integrate it into the framework and adding some ease of use features. Also seems like a nice way to support the development of astro by using their hosting service.
Yeah, the only unsafe code right now is using this trait to prevent some duplicate bounds checking when reading/writing to memories that wasn't being optimized by the rust compiler. Shouldn't be too much of a performance difference for code that's not too heavy on memory access, made about a 5-10% difference for the selfhosted benchmark if I remember correctly though.
Hi! I have a short reflection essay, which should be mostly covered by the documentation in the repo. But I could share it if you shoot me an email.
WASI is one of the next things I want to explore. Right now, there sadly doesn't seem to be any self-contained implementations for the recently released WASI preview 2 out there, and TinyWasm also doesn't have support for the WebAssembly Component Model yet.
For performance, I have some very preliminary benchmarks, but this is something I want to go into more as part of my upcoming bachelor's thesis.
Posted by
explodingcamera on Thursday March 07, 2024 @05:44AM
from the show-hn dept.
https://github.com/explodingcamera/tinywasm
Show HN: TinyWasm - A tiny WebAssembly Runtime written in RustHi HN! I'm excited to share TinyWasm (https://github.com/explodingcamera/tinywasm), a WebAssembly Interpreter I developed for my final university project.The main goal of this project was to deepen my understanding of WebAssembly and interpreter design. TinyWasm successfully passes all the official WebAssembly 1.0 tests and also...
Posted by
explodingcamera on Wednesday March 06, 2024 @02:59PM
from the support.google.com dept.
zero-clause BSD is essentially a modified MIT that doesn't even require attribution, so essentially a "public domain" like license.
It is absolutely done, mostly by the media player/library used, e.g exoplayer on Android has automatic lag compensation for that purpose.
From the documentation, it seems like there is 0 mercurial support. It's its own separate version control system that diverged years ago. You can either use the sapling scm client or git.
The latest reply in this GitHub issue links to documentation and a example repo showing that tailwind is supported though
The visualization looks cool, but it's not fun to use, not having an overview of all the project names really messes with my head, especially always having to scroll back up and not seeing what I'm clicking on.
Esperanto is supported in their larger model
How is it with high bandwidth application? E.g would it be okay to put my media server behind it? Currently tunneling it through a VPS so cloudflare doesn't get mad.
Looks really nice! Also, super happy that the interactive examples are not super sluggish code sandbox iframes, they're actually usable! A more typescript-first approach would have been nice, or at least typescript/JavaScript toggles, but the React team seems to be aware that that's an area they need to work on.
I think the Python 2 requirement is just a mistake in the README, I'm pretty sure the node-gyp version they're using only supports python 3.
what does this have to do with the eu? The bad proposals I've seen have all been shut down, and instead good laws like gdpr and net neutrality have been enacted eu-wide.
Posted by
explodingcamera on Monday February 20, 2023 @10:49AM
from the arxiv.org dept.
Check out their kimsufi offering
Looks really nice! one thing I instantly noticed though is the import order, would be nice if they could consider switching the path and module name around, like `from "x" import y`, not sure why modern languages would still do it like this.
Might be only available in Firefox Developer Edition
That doesn't mean there nothing to be learned from mistakes previous languages made and striving to create iteratively better languages
The biggest breaking change I see is just dropping compatibility for older browsers, you can however still enable it with a plugin.
There's an easy fix, say you moved to the eu and request that they delete all data about you (you could also try to do a data correction request to change your age).