frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Data Model Dependency Is a Trap

https://medium.com/@HobokenDays/the-fate-of-shared-data-model-cf8a3dc88ac9
1•HideInNews•1m ago•0 comments

Ship comms: how do they work?–lightning talk by Matt Kulukundis [video]

https://www.youtube.com/watch?v=RFvnXCHS57M
1•leoc•7m ago•0 comments

Show HN: Beauty Arena – An Elo-based experiment to measure aesthetics

https://beautyarena.vercel.app
1•railing1024•7m ago•0 comments

"For You" Feed for Science

https://www.researchhub.com/
1•Tardigrade10•8m ago•0 comments

Outside, Dungeon, Town: Integrating the Three Places in Videogames (2024)

https://keithburgun.net/outside-dungeon-town-integrating-the-three-places-in-videogames/
1•vector_spaces•10m ago•0 comments

39C3 – Breaking architecture barriers: Running x86 games and apps on ARM

https://www.youtube.com/watch?v=3yDXyW1WERg
1•doener•10m ago•0 comments

Stranger Things Creator: Turn Off TV's Garbage Settings

https://www.instagram.com/reel/DRiaP2zEow4/
1•next_xibalba•11m ago•1 comments

Why A.I. Didn't Transform Our Lives in 2025

https://www.newyorker.com/culture/2025-in-review/why-ai-didnt-transform-our-lives-in-2025
1•petethomas•12m ago•0 comments

Show HN: McNeal – Encrypted messaging over acoustic channels

https://github.com/AntonioLambertTech/McnealV2
1•netIsNewWrldOrd•13m ago•0 comments

Show HN: SAFi, a Governance Engine for LLMs

https://safi.selfalignmentframework.com
1•jnamaya•15m ago•0 comments

'Capital of capital': how Abu Dhabi rose as a sovereign wealth powe

https://www.ft.com/content/711e670c-4832-49cb-8b10-5018103ec785
1•petethomas•19m ago•0 comments

The Magic of Merlin

https://www.birds.cornell.edu/home/the-magic-of-merlin/
1•Group_B•23m ago•1 comments

Why most software startups don't need VCs anymore (most)

https://sderosiaux.substack.com/p/why-most-software-startups-dont-need
1•chtefi•25m ago•0 comments

Episteme: A New System for Science

https://episteme.com/
1•momeara•26m ago•0 comments

Comparative Overview of EU-US Vehicle Standards

https://etsc.eu/comparative-overview-eu-us-vehicle-standards/
4•throw0101c•32m ago•0 comments

Show HN: Giselle – open-source visual editor for building AI workflows

https://github.com/giselles-ai/giselle
1•codenote•34m ago•0 comments

Don't call yourself a programmer, and other career advice (2011)

https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/
1•teleforce•35m ago•1 comments

Five myths about learning a new language – busted

https://theconversation.com/five-myths-about-learning-a-new-language-busted-266946
2•zeristor•36m ago•0 comments

Miniray – A WGSL Minifier

https://hugodaniel.com/posts/miniray/
1•todsacerdoti•37m ago•0 comments

MongoDB Server Security Update, December 2025

https://www.mongodb.com/company/blog/news/mongodb-server-security-update-december-2025
12•plorkyeran•40m ago•2 comments

The Manus Debate and Why Some Bubbly AI Moonshots Aren't Bubbles

https://substack.com/inbox/post/182749582
1•theno0b•44m ago•1 comments

Show HN: DynamicHorizon – Dynamic Island for macOS

https://www.dynamichorizon.app
2•DHDEV•58m ago•0 comments

The Second Great Error Model Convergence

https://matklad.github.io/2025/12/29/second-error-model-convergence.html
1•kartikarti•1h ago•0 comments

Hyaluronic Acid in Topical Applications: Hero Molecule in the Cosmetics Industry

https://www.mdpi.com/2218-273X/15/12/1656
2•PaulHoule•1h ago•0 comments

Robots Are Hard – Revisiting the original Roomba and its simple architecture

https://robotsinplainenglish.com/e/2025-12-27-roomba.html
3•ArmageddonIt•1h ago•0 comments

Capital in the 22nd Century

https://philiptrammell.substack.com/p/capital-in-the-22nd-century
2•jger15•1h ago•0 comments

Will Skyrocketing Silver Prices Make Photo Film More Expensive?

https://petapixel.com/2025/12/29/will-skyrocketing-silver-prices-make-photo-film-even-more-expens...
1•geox•1h ago•0 comments

Show HN: J_PyDB – tiny encrypted file-based Python DB

https://github.com/NovaDev404/J_PyDB
1•SuperGamer474•1h ago•1 comments

Stranger Things Creator Says Turn Off "Garbage" Settings

https://screenrant.com/stranger-things-creator-turn-off-settings-premiere/
31•1970-01-01•1h ago•19 comments

Bye Bye Big Tech: How I Migrated to an Almost All-EU Stack (and Saved 500€/Year)

https://www.zeitgeistofbytes.com/p/bye-bye-big-tech-how-i-migrated-to
6•alexcos•1h 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.