frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Lobfo – AI terminal for sports prediction markets (Kalshi × Polymarket)

https://v0-pmt-ai.vercel.app/
1•Nortca•2m ago•1 comments

Show HN: Chrobox – plan, execute, and reflect with AI insights

https://www.chrobox.net/
1•ggprgrkjh•2m ago•0 comments

How to make a macOS screen saver

https://wadetregaskis.com/how-to-make-a-macos-screen-saver/
1•chmaynard•4m ago•0 comments

Getting AI object removal to run in under 2 seconds in a Figma plugin

https://www.figma.com/community/plugin/1576512610054427811/photo-object-remover-imgour
1•Bikashhh•5m ago•1 comments

Advent Hunt 2025

https://2025.adventhunt.com/
1•thatoneengineer•5m ago•0 comments

Chinese fighters target SDF jets with radar lock-on, Japan says

https://www.japantimes.co.jp/news/2025/12/07/japan/china-japan-radar-lock-on/
1•DustinEchoes•10m ago•0 comments

Show HN: MCP Hosting with Persistent Storage

https://glama.ai/blog/2025-12-06-mcp-hosting-with-persistent-storage
1•statements•12m ago•0 comments

Space Invaders – The Legacy

https://spaceinvaders.square-enix-games.com/legacy
1•andsoitis•13m ago•0 comments

Invader

https://www.space-invaders.com/home/
1•andsoitis•15m ago•0 comments

Saving Japan's exceptionally rare 'snow monsters'

https://www.bbc.com/future/article/20251203-japans-disappearing-snow-monsters
1•1659447091•15m ago•0 comments

Mathematics Without Numbers

https://www.jstor.org/stable/20026529?seq=1
1•andsoitis•16m ago•0 comments

Cloudflare outage, December 6th 2025

1•AlOwain•20m ago•0 comments

2025 Desmos Art Contest

https://www.desmos.com/art
1•downboots•21m ago•0 comments

Ask HN: Is Opus 4.5 scaring the crap out of you as well?

4•consumer451•24m ago•0 comments

Computer-Science Reinforcement Learning Got Rewards Wrong

https://gist.github.com/yoavg/3eb3e722d38e887a0a8ac151c62d9617
1•Anon84•26m ago•0 comments

Mechanical Habits

https://matklad.github.io/2025/12/06/mechanical-habits.html
1•emschwartz•31m ago•0 comments

Neuralink Overview, Fall 2025

https://www.youtube.com/watch?v=QJdgHXyJh7M
2•oars•31m ago•0 comments

RSF massacres left Sudanese city 'a slaughterhouse', satellite images show

https://www.theguardian.com/global-development/2025/dec/05/rsf-massacres-sudanese-city-el-fasher-...
1•reducesuffering•32m ago•0 comments

Hackers Impersonate Brands to Steal YouTube Channels

https://utkusen.substack.com/p/how-hackers-impersonate-brands-to
1•utku1337•34m ago•0 comments

Poetiq: SOTA Reasoning on ARC-AGI

https://github.com/poetiq-ai/poetiq-arc-agi-solver
1•rahimnathwani•39m ago•0 comments

Apple's exec shake-up continues with departures of general counsel, policy head

https://techcrunch.com/2025/12/04/apples-executive-shakeup-continues-with-departures-of-general-c...
7•randycupertino•40m ago•2 comments

Resources for Protecting Against 'React2Shell'

https://vercel.com/blog/resources-for-protecting-against-react2shell
1•lortex•43m ago•0 comments

Wave of (Open Street Map) Vandalism in South Korea

https://www.openstreetmap.org/user/KennyDap/diary/407844
25•shortrounddev2•47m ago•2 comments

Pipetap: A Windows Named Pipe Multi-Tool / Proxy

https://github.com/sensepost/pipetap
1•leonjza•49m ago•0 comments

ReVSeg: Incentivizing the Reasoning Chain for Video Segmentation with RL

https://arxiv.org/abs/2512.02835
1•SweetSoftPillow•49m ago•0 comments

Quick takes on the Dec 5 Cloudflare outage

https://surfingcomplexity.blog/2025/12/06/quick-takes-on-the-dec-5-cloudflare-outage/
2•gpi•50m ago•0 comments

Photographer Built a Medium-Format Rangefinder, and So Can You

https://petapixel.com/2025/12/06/this-photographer-built-an-awesome-medium-format-rangefinder-and...
1•shinryuu•52m ago•0 comments

Beauty and the feast: Effect of beauty on earnings using restaurant tipping data

https://ideas.repec.org/a/eee/joepsy/v49y2015icp34-46.html
2•mhb•54m ago•0 comments

United States Antarctic Program Field Manual (2024) [pdf]

https://www.usap.gov/usapgov/travelAndDeployment/documents/Continental-Field-Manual-2024.pdf
3•SheinhardtWigCo•55m ago•0 comments

Automating Organic Synthesis

https://www.rowansci.com/blog/automating-organic-synthesis-onepot
2•sethbannon•56m ago•0 comments
Open in hackernews

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

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