Posted by david927 10 hours ago
Ask HN: What Are You Working On? (Nov 2025)
It looks inside each file to see what it’s about, then moves it to the right folder with a single click. Everything happens on your Mac, so nothing leaves your computer. No clouds, no servers.
It already works with images, Office (Word, Excel, PowerPoint) PDFs, ePubs, text, Markdown, and many other file types (30+) in English. Next I’m adding multi-language support.
If you have messy folders anywhere on your Mac, Floxtop can help.
Try it for free - requires macOS 14+ with Apple Silicon: https://github.com/taranntell/fallinorg/releases/download/1....
https://github.com/scallyw4g/bonsai
I recently ported the terrain generators to the GPU, and increased the visible volume to 1 billion voxels cubed. I did a short YouTube video about it.
https://www.youtube.com/watch?v=bLfgjWsM1PI
I also wrote a metaprogramming language which generates a lot of the editor UI for the engine. It's a bespoke C parser that supports a small subset of C++, which is exposed to the user through a 'scripting-like' language you embed directly in your source files. I wrote it as a replacement for C++ templates and in my completely unbiased opinion it is WAY better.
Users can create their own sub-communities, and within them, set up different categories and boards. Posts can be voted on, and board types can include regular posts, Q&A, or live chat. It's like a hybrid of Reddit and Discord but leans more towards a traditional web community. It also supports server-side rendering, making it SEO-friendly. This project is an extension of my previous Hacker News clone, dizkaz (https://news.ycombinator.com/item?id=43885998).
I got all the components, tested it on a breadboard, learned to solder and now I'm working on the 3d Print to enclose everything.
I actually just did a test run to see if my current 3d design would fit my PICO board, and it fit, but not that secure yet.
Im a developer but never worked this close to metal, so I've been so happy with how it's been going so far, making me real proud of myself.
The iron rule is no direct interaction with the world. These are things that players can in theory always start on their own as long as they can communicate.
* Disk images
* Liveboot isos
* Container images (docker/podman)
Many build products are supported, with more on the way:
https://chrivers.github.io/raptor/builders/index.html#compat...
It uses a syntax that is inspired by Docker, but significantly enhanced.
Take a look at:
* The project: https://github.com/chrivers/raptor/
* The book: https://chrivers.github.io/raptor/
It's very interesting because the Ruby codebase uses a `typedef uintptr_t VALUE` type to mean any of the following:
- A pointer to the heap
- A Ruby tagged value (which may be a pointer to the heap)
- Any integer value that fits in `uintptr_t`
Fil-C doesn't allow you to carry around pointers using integers, in the sense that when you do that, the pointers lose their capabilities.
But in Ruby's case, it's not as simple as changing the typedef to a pointer type, since `VALUE` variables often end up being used for integer math (including bit math, shifts, etc).
So, it's going to take a nontrivial patch to Ruby to get it to work in Fil-C. I think I'm about 70% of the way through (I started Friday afternoon).
Hope to document 100 ideas. Wish me luck.
It's a custom assembler built on top of the LLVM assembler (llvm-mc) that emits instrumentation code to catch ABI violations at runtime. Stuff like clobbering nonvolatile registers, misaligning the stack pointer, misusing the redzone, assuming volatile registers don't change across a function call, etc.
Hoping to finish up basic x86_64 support within the next few days. I can now reliably assemble and run unoptimized gcc output without hitting false positives, but I still have to iron out some false positives triggered by OpenSSL's handwritten assembly routines.
TODO items for the near future include porting the runtime support library into a kernel module so I can instrument Linux, and beginning ports other architectures (ideally something semi-obscure like POWER or RISC-V). I also need to figure out how to support dynamic linking, because the tool currently needs static linking to access its thread-local variables.
https://github.com/kenballus/llvm-project/tree/abisan/llvm/t...
Not related to the thread, but if anyone is looking to hire a developer or knows of opportunities, I was recently let go and am actively searching. Any leads or feedback would be greatly appreciated.
Sample PDF: https://drive.google.com/file/d/1n7M1TKOptSsYiibrbvV_Yojx53T...