takko_the_boss

Going to the bathroom.

Like, I gotta get up, walk a few steps, sit down, read Facebook, and then i gotta clean my own rear end. Why aren't we in Wall-E world yet?

I want to just wake up, eat, sleep, repeat without ever having to move out of my floating platform apparatus. Instead of deciding what to eat, goop is dispensed to you from the comfort of my own floating chair/bed thing. Pottying should be the same. A large blocker in this lifestyle is the necessity to get up and do the business yourself. I want a platform that directly handles bodily waste material without you ever having to get up.

I'm working on the Hachi programming language (https://hdev.run).

It started a few years back. I wanted to modernize some C/C++ stuff (specific use cases, long story) and do some easy interop. And I didn't find exactly what I wanted, so I just built it. Additionally, creating a language means I get to express things the way *I* want to, and not be bounded to someone else's way of doing it, no matter how good. And over time, I started to consume features I like from other languages.

Initially, this was 100% *only* for me, and me alone. But I released it publicly later that year since I realized that maybe someone could get some use out of it. And most (if not all) of the things I work on aren't public, so figured it'd be an interesting experience to let it see some sunlight.

Hachi is in fact used for actual work, and is currently at v0.5. Not only do I use it for making tools, but I've also replaced just about all of the bash and python scripting I'd otherwise normally do with Hachi instead.

I make quite regular edits to the compiler and core lib modules, however the documents do lag behind slightly (I'm just one dude).

Anyways, this is my favorite passion project and I do plan to be at it for a long time, and now I want to share it with the HN community here!

This is awesome! As a fellow language maker, this is no small feat!!!!

I'm super interested in what resulted in the motivation to create tin.

I usually get grief from folks who ask "Why do it?! Is there not enough out there for you? How special is this 'work' you're even doing?!", or my favorite being "just write in (X language) instead".

I have a huge amount of respect for other folks who determine that what they want to express is unique enough that they'd fare better with their own language instead of whatever industry standard or Soup De Jour is ubiquitous.

Rest In Peace Dan Simmons.

R.I.P.

Felix proposes a simple constraint: never update state directly. Instead, append canonicalized temporal facts and derive current state from the latest observation. Includes canonicalization rules, identity hashing, snapshot semantics, and ingestion behavior. Designed for telemetry, configuration tracking, audit logging, and out-of-order ingestion scenarios.

I’ve been building a programming language called Hachi for the past couple of years. It’s a lightweight systems language that transpiles to C++, giving you native performance with a modern, simple syntax.

One of Hachi’s most unique feature is its memory management model: it uses static lifetime analysis to automatically insert free calls when values go out of scope. There’s no garbage collector, no runtime overhead, and you still get memory safety similar to RAII, but without the boilerplate.

Hachi also makes it easy to embed C or C++ code directly into your source files, so you can leverage existing libraries without fighting the toolchain. It’s been especially fun to use for security tooling and networking-related projects.

The language is still evolving, but it already works well for real-world code (I use it for work at my company). If you’re curious, check it out, try a small project, or even just skim the tutorials in the docs site. I’d love feedback, ideas, or just to know what folks think.