frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Trap Street

https://en.wikipedia.org/wiki/Trap_street
1•ivanjermakov•1m ago•0 comments

Why are some people mosquito magnets? Clues are emerging

https://phys.org/news/2026-05-people-mosquito-magnets-clues-emerging.html
1•jnord•2m ago•0 comments

Show HN: I made a screen recording app to make demos like an Apple commercial

https://shotglass.app
4•jakemanger•5m ago•0 comments

Satteri – High-Performance Markdown and MDX Processing for the JavaScript

https://github.com/bruits/satteri
2•todotask2•5m ago•0 comments

GitHub Launchpad Proposal

https://github.com/liamromanis101/Github_Strategic_Proposal-2026
2•lromanis•7m ago•0 comments

FaceTime Without the Internet [video]

https://www.youtube.com/watch?v=0b1XL91-q48
2•marklit•8m ago•0 comments

OpenAI, Microsoft and Friends Build a Better, More Scalable Ethernet

https://www.nextplatform.com/connect/2026/05/12/openai-microsoft-and-friends-build-a-better-more-...
3•rbanffy•10m ago•0 comments

Cuckooland – Tom Burgis on the abuse of power and influence (2024)

https://www.ft.com/content/b82c15dd-0c63-4657-a2e7-488ce30b8afc
3•robtherobber•13m ago•0 comments

Google's Android-powered laptops are called Googlebooks, and coming this year

https://arstechnica.com/gadgets/2026/05/googles-android-powered-laptops-are-called-googlebooks-an...
3•rbanffy•14m ago•0 comments

Hysteria: A QUIC-Based Proxy Designed to Resist Censorship

https://github.com/apernet/hysteria
4•steveharing1•16m ago•0 comments

Bun is being ported to Rust using Claude. Here's a code review using GPT

https://github.com/Swival/security-audits/blob/main/bun-rust/README.md
2•jedisct1•17m ago•0 comments

Alien

https://typesetinthefuture.com/2014/12/01/alien/
3•tosh•18m ago•0 comments

AllSkyKamera: A Citizen-Science Network for Global Night Sky Monitoring

https://allskykamera.space/index.php?lang=en
3•ptrsrtp•19m ago•0 comments

Show HN: Recursant, a mesh-based control plane for AI agents

https://github.com/ajensenwaud/recursant
2•hestefisk•22m ago•0 comments

OpenCL 3.1

https://www.khronos.org/blog/opencl-3.1-is-here
3•tosh•24m ago•0 comments

Valve snuck a Wilhelm scream Easter egg into the new Steam Controller [video]

https://www.youtube.com/watch?v=tw5Luf_7F8c
2•HelloUsername•26m ago•0 comments

Terence Tao: New mathematical workflows [video]

https://www.youtube.com/watch?v=Uc2zt198U_U
1•energy123•29m ago•0 comments

Codex Computer Use

https://developers.openai.com/codex/app/computer-use
1•tr33house•30m ago•1 comments

AluminiumOS, by Google: Android Reimagined for the Desktop

https://aluminium-os.com/
9•brysonreece•34m ago•14 comments

Urlsify.com Made This Free to Use URL Shortener with Indepth Analytics

https://old.reddit.com/r/sideprojects/comments/1tabelm/finished_making_this_url_shortener_complet...
1•godlymod•34m ago•0 comments

Hantavirus Map

https://hantavirusmap.net/
1•leonvonblut•38m ago•0 comments

Wrote this for humans, now I use it as a prompt

https://x-x.codes/posts/supplementary-guide-to-code-reviews
1•alex_x•39m ago•1 comments

Sick of Ads on Free QR Generator

https://miqr.mx/
1•rubiocanino•41m ago•2 comments

Genera OS

https://wiki.c2.com/?GeneraOs
2•tosh•42m ago•0 comments

Leak reveals Google's Aluminium OS with a 16-minute video

https://www.androidauthority.com/google-aluminium-os-leak-3665979/
4•thunderbong•43m ago•0 comments

The Role of HubSpot in Driving Successful CRM Adoption in Africa

https://amdan.pro/the-role-of-hubspot-in-driving-successful-crm-adoption-in-africa/
1•amdanmerit•44m ago•0 comments

Tep: A Sinatra-flavoured framework that compiles to a native binary via Spinel

https://github.com/oripekelman/tep
1•futurecat•48m ago•0 comments

Show HN: Design posters showcasing your country's electrical grid

https://github.com/open-energy-transition/grid2poster
1•lyoncy•53m ago•0 comments

European governments: 3.000 tracking sites, 1.000 phpMyAdmins, and 99% poorly

https://internetcleanup.foundation/2026/05/european-governments-3000-tracking-sites-1000-phpmyadm...
42•aequitas•56m ago•6 comments

A Brazilian Space Launch System for the Small Satellite Market

https://www.mdpi.com/2226-4310/6/11/123
1•rbanffy•58m ago•0 comments
Open in hackernews

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

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