frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Apple and Google pledge not to discriminate against third-party apps in UK deal

https://www.theguardian.com/technology/2026/feb/10/apple-google-third-party-apps-app-store
1•chrisjj•34s ago•0 comments

Tell me about an OpenClaw skill

2•l-fy•2m ago•0 comments

The Danger of Shipping Fast

https://newsletter.posthog.com/p/the-hidden-danger-of-shipping-fast
1•vinhnx•2m ago•0 comments

Jury told that Meta, Google 'engineered addiction' at landmark US trial

https://techxplore.com/news/2026-02-jury-told-meta-google-addiction.html
1•geox•4m ago•0 comments

Struggling Towards an Algebraic Theory of Music

https://reasonablypolymorphic.com/blog/algebraic-music/
1•surprisetalk•5m ago•0 comments

To be well-calibrated is to be punctual

https://www.lesswrong.com/posts/9Qj6v2tjZfDH9kfam/to-be-well-calibrated-is-to-be-punctual
1•surprisetalk•5m ago•0 comments

Making Money on OnlyFans Is a Lot Harder Than You Think (2020)

https://www.vice.com/en/article/making-money-on-onlyfans-is-a-lot-harder-than-you-think/
1•surprisetalk•5m ago•0 comments

Vi turns 50 this year

https://en.wikipedia.org/wiki/Vi_(text_editor)
1•kurren•5m ago•1 comments

Show HN: Snagg – Clip memes from anywhere, post them instantly

https://snagg.meme
1•airowe•5m ago•0 comments

My helicopter went into freefall – inside an active volcano

https://www.theguardian.com/lifeandstyle/2026/feb/10/my-helicopter-went-into-freefall-inside-an-a...
1•Symbiote•6m ago•0 comments

Show HN: I wrote a prompt to stop Gemini from hallucinating

1•Ginsabo•6m ago•0 comments

Ask HN: Local community first approach to building an age verification system

1•throwaway_2898•6m ago•0 comments

PicoClaw ultra-lightweight personal AI Assistant run on just 10MB of RAM

https://www.cnx-software.com/2026/02/10/picoclaw-ultra-lightweight-personal-ai-assistant-run-on-j...
2•pyprism•7m ago•0 comments

"Stan Veit's History of the Personal Computer" Audiobook, YouTube Introduction [video]

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

Show HN: Samma Suit – Open-source 8-layer security framework for AI agents

https://sammasuit.com
1•jbwagoner•7m ago•0 comments

Star – Your Digital Songbook

https://starapp.io
1•mianala•9m ago•0 comments

74% of European firms would fail without access to U.S. technology

https://europeancorrespondent.com/en/r/trumps-power-switch
2•speckx•10m ago•0 comments

Freeimageai.org is your go-to hub for free AI image generation and editing

https://freeimageai.org
1•zhouhua•10m ago•1 comments

Cecli AI Coding Assistant

https://cecli.dev
1•tomjuggler•10m ago•1 comments

Epsteinomatic: Turn Your Memories into Crimes

https://epsteinomatic.com/
4•dezmou•11m ago•1 comments

Show HN: Mouse-tracker – A tiny physics-based mouse tracker (Web Component)

https://gimli.app/mouse-tracker
1•gimliapp•11m ago•0 comments

Show HN: Radiant – Radial Menu Launcher for macOS Inspired by Blender's Pie Menu

1•sagawafumiya•12m ago•0 comments

The Left has a Hyperpolitics problem

https://newrepublic.com/article/205820/left-protests-hyperpolitics-building-political-power
1•RickJWagner•13m ago•0 comments

How to Migrate Your Custom GPTs to Claude

https://aiforcontentmarketing.ai/what-to-do-with-your-custom-gpts-when-you-switch-to-claude/
1•pakostina•13m ago•0 comments

The Screening Machine

https://www.tabletmag.com/sections/science/articles/screening-machine
1•RickJWagner•13m ago•0 comments

LingBot – open weights world model

https://huggingface.co/robbyant/lingbot-world-base-cam
1•nikhizzle•14m ago•0 comments

Show HN: AppControl – A Modern Windows Task Manager with History

https://www.appcontrol.com/
1•suprnurd•15m ago•1 comments

Show HN: Shuffled - Daily word puzzle game

https://shuffled.app
1•wmora•15m ago•0 comments

Show HN: The Control and Memory Layer for AI Agents

1•dan_lupashku•15m ago•0 comments

Show HN: Vela – Modern programming language compiling to native code via LLVM

https://github.com/MigMarGil/Vela_lang
1•MMG_dev•16m ago•0 comments
Open in hackernews

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

https://github.com/evelance/brainiac
5•0x000xca0xfe•8mo 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•8mo 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•8mo 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•8mo 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.