frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Removing macOS 26 Tahoe's unwanted menu icons

https://weblog.rogueamoeba.com/2026/01/10/removing-tahoes-unwanted-menu-icons/
1•chmaynard•31s ago•0 comments

MySQL users be warned: Git commits in MySQL-server significantly declined 2025

https://optimizedbyotto.com/post/reasons-to-stop-using-mysql/
1•ottoke•1m ago•0 comments

Are We ... Yet?

https://wiki.mozilla.org/Areweyet
1•mooreds•2m ago•0 comments

The Software Cambrian Explosion

https://johncodes.com/archive/2026/01-11-explosion/
1•jpmcb•4m ago•0 comments

The death of code won't matter

https://jaimefjorge.com/posts/the-death-of-code-wont-matter/
2•jaimefjorge•5m ago•0 comments

Google automatically emails 13 year olds to allow them to opt out of parental s

https://support.google.com/families/answer/7106787?hl=en
1•todsacerdoti•6m ago•0 comments

Blogs Are Back – Discover and Follow Independent Blogs

https://www.blogsareback.com
1•ArmageddonIt•8m ago•0 comments

Show HN: I wrote an embeddable Unicode algorithms library in C

https://github.com/railgunlabs/unicorn
1•hgs3•9m ago•0 comments

LLVM: The Bad Parts

https://www.npopov.com/2026/01/11/LLVM-The-bad-parts.html
1•nikic•9m ago•0 comments

Show HN: AI Code Guard – Security scanner for AI-generated code

https://github.com/ThorneShadowbane/ai-code-guard
1•ajujaans•11m ago•0 comments

Monero ATM Project: A do-it-yourself automated Teller machine

https://atm.monero.is/builds.html
1•debesyla•12m ago•0 comments

Onager: Graph in DuckDB

https://cogitatortech.github.io/onager/
2•marklit•14m ago•0 comments

Using a tiny GPT model to beat Brotli/ZSTD, 600x faster than Fabrice Bellard's

https://github.com/carsonpo/compress-zip
1•carsonpoole•14m ago•0 comments

Digital Travel App TripBFF Exposed Location Data Way Too Accurately

https://medium.com/bugbountywriteup/digital-travel-app-tripbff-exposed-location-data-way-too-accu...
1•Jlleitschuh•17m ago•0 comments

Vibe Engineering: What I've Learned Working with AI Coding Agents

https://twitter.com/mrexodia/status/2010157660885176767
2•nekitamo•18m ago•1 comments

Ralph Experiment – SQLite UI

https://lochie.dev/posts/ralph-sqlite-ui/
1•mpweiher•18m ago•0 comments

Universal Commerce Protocol (UCP)

https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/
1•shooker435•19m ago•0 comments

Infest: Special Edition

https://archive.org/details/infest.special-edition
1•rendx•23m ago•0 comments

Impressed by Synology Support

https://blog.notmyhostna.me/posts/impressed-by-synology-support
1•dewey•23m ago•0 comments

The 400-year software patch to a 10-day memory leak

https://ischemist.com/writings/note/calendar-memory-leak
1•hiddenseal•25m ago•0 comments

Microsoft Windows Media Player stops serving up CD album info

https://www.theregister.com/2026/01/09/microsoft_windows_media_player_forgets/
4•A4ET8a8uTh0_v2•26m ago•1 comments

Sergey Brin is joining Larry Page, in reducing ties to CA

https://www.nytimes.com/2026/01/09/technology/google-founders-california-wealth-tax.html
2•vlod•26m ago•1 comments

Cambridge college to target elite private schools for student recruitment

https://uk.news.yahoo.com/cambridge-college-target-elite-private-185806826.html
1•nephihaha•27m ago•0 comments

Claude Code Orchestrator – Parallel AI Development with Multiple Claude Sessions

https://github.com/reshashi/claude-orchestrator
1•shashimudunuri•27m ago•1 comments

Learning to work (very) remotely (2023)

https://borischerny.com/tech/2023/12/10/Working-Remotely.html
1•mooreds•29m ago•0 comments

A16Z: The Power Brokers

https://www.notboring.co/p/a16z-the-power-brokers
1•paulpauper•30m ago•0 comments

A Closer Look at the 2026 U.S. Food Guidelines

https://www.exfatloss.com/p/a-closer-look-at-the-2026-us-food
1•paulpauper•31m ago•0 comments

Social-MCP: new kind of social network

https://social-mcp.org/
2•gwainrib•31m ago•1 comments

Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production

https://skoredin.pro/blog/golang/goroutine-leak-debugging
3•ibobev•32m ago•0 comments

Hexagonal Architecture in Go: Why Your "Clean" Code Is a Mess

https://skoredin.pro/blog/golang/hexagonal-architecture-go
3•ibobev•33m ago•0 comments
Open in hackernews

Show HN: Brainfuck to RISC-V JIT compiler written in Zig

https://github.com/evelance/brainiac
5•0x000xca0xfe•7mo ago
Hi everybody,

this was my project to learn Zig and RISC-V+x86_64 assembly.

Not sure if anybody is actually interested in yet another Brainfuck compiler, so I'll just write up some random things I learned while building it!

- A primitive assembly stitching compiler is 10x faster than the interpreter. Did not expect that.

- The generated x86 code is really bad (e.g. it always uses 6 or 7 byte sized instructions with 32-bit immediates when there are much smaller ones) but it doesn't really matter. Good code generated by GCC and clang for transpiled Brainfuck->C is not much faster as it's bottlenecked by memory accesses anyways.

- Zig is pretty far along actually. You can make serious projects with it!

- But the community seems to like self-punishment. Unused parameters and variables are hard errors and there is no way to disable that even for debug builds. Makes quickly commenting out part of the code a real PITA.

- I've had a miscompilation due to std.mem.span being broken and two source code breaks going from Zig 0.13 to 0.15 (std.mem.page_size got removed and ArrayList.popOrNull as well).

- But arbitrary size integers are fantastic! And well-defined two's complement behaviour!

Here is for example the code that encodes the c.beqz instruction:

  /// Branch if Equal to Zero (compressed): c.beqz rs1', offset -> beq rs1, x0, offset
  pub fn c_beqz(text: *std.ArrayList(u8), rs1: RV_X, offset: i9) !void {
      std.debug.assert(is3BitReg(rs1));
      std.debug.assert(@mod(offset, 2) == 0);
      const imm: u9 = @bitCast(offset);
      const RV_CB = packed struct(u16) {
          op: u2,
          offset5: u1,
          offset1_2: u2,
          offset6_7: u2,
          rsd_rs1_: u3,
          offset3_4: u2,
          offset8: u1,
          funct3: u3,
      };
      const ins = RV_CB {
          .op = 0x1,
          .offset5 = @truncate(imm >> 5),
          .offset1_2 = @truncate(imm >> 1),
          .offset6_7 = @truncate(imm >> 6),
          .rsd_rs1_ = @truncate(@intFromEnum(rs1) - 8),
          .offset3_4 = @truncate(imm >> 3),
          .offset8 = @truncate(imm >> 8),
          .funct3 = 0x6,
      };
      try appendInstruction(text, u16, @bitCast(ins));
  }
This is really nice as all the exotic integer sizes are actually checked, too.

- Zig support for Windows is good. Porting the project to Windows was very easy.

- When the RISC-V registers are carefully chosen, almost all instructions could be compressed in this projects.

- Compressed instructions and good branching code (using the branch instructions directly when the jump range is small enough instead of branching over a larger jump instruction) did not noticeably change performance on real hardware (OrangePi RV2).

- But somehow QEMU got a massive boost from that. Not sure why exactly.

So, that's about it!

I hope at least something was interesting...

Comments

sylware•7mo ago
thumbs up for this project (everything RISC-V is usually).

I write rv64 assembly (nearly core only, without memory reservation instructions) and run it on x86_64 with a very small (x86_64 assembly written) interpreter.

And your are right, I have had thoughts about a "RISC-V" x86_64 compiler (but it will probably require some runtime unfortunately).

Hopefully, rv22+ hardware with ultra-performant µ-architecture and with the latest silicon process will happen sooner than we expect. One less PI toxic lock and cleaner, _really standard_ assembly (the end game of much software).

0x000xca0xfe•7mo ago
Yeah I can't wait for a performant RISC-V core. Runtime code generation is so easy for RISC-V. I have many ideas or projects where I'd like to use it but it feels kinda pointless when JITed RISC-V machine code on current hardware gets destroyed by any half-decent x86 PC or Mac running naive C code.
sylware•7mo ago
Well, here are the tricks: interpreted rv64 assembly will be "slow"... actually "slower" than x86_64 native code... but in many execution contexts, for many pieces of software, here the first trick: the "slow" interpreted rv64 assembly machine code will be... "fast" enough... The 2nd trick: I have control on my rv64 machine interpreter, and I can write native x86_64 acceleration assembly along side of a rv64 reference implementation (I planned to do just that for my CPU renderer in my wayland compositor... actually I have already AVX2 code for some of that, even though the sweet spot is AVX512, but don't have the hardware for this, yet).

And once we have this rv64 shiny hardware, certainly won't be a drop-in, but the distance to code will be minimal.

One important SDK thing: I am careful at using the smallest number of rv64 machine instructions (we tend to forget 'R' in "RISC-V" means 'R'educed...), and I use basic, really basic, C preprocessors instead of the assembler preprocessor in order to decouple the assembly code from a specific assembler preprocessor. I don't even use assembler pseudo-instructions, or ABI register names, neither compressed machine instructions.

On top of that: I don't use ELF, I use a super minimal executable/system interface dynamic shared library format of my own, omega idiotically simple, which I wrap in ELF binaries for transparent support. People have to come to realize, ELF complexity, for a executable/system interface dynamic shared library is utterly and completely obsolete, even a liability once you are looking for binary stability in time (cf games), proven over more than the last decade.