frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Rankiwiki – voting-based rankings for small groups

https://rankiwiki.com
1•rankiwiki•54s ago•0 comments

Fop – Filter Orderer and Preener (Rust Edition) for Adblock

https://github.com/ryanbr/fop-rs
1•mp3geek•2m ago•1 comments

Read Something Wonderful

https://readsomethingwonderful.com/
1•snorbleck•4m ago•0 comments

The Hardest Part of Starting a Startup Isn't Code, It Is This

1•suhaspatil101•5m ago•0 comments

Why Self-Driving Cars Still Don't Exist

https://dan.bulwinkle.net/blog/full-self-driving-cars/
1•pilingual•5m ago•0 comments

The Whole App Is a Blob

https://drobinin.com/posts/the-whole-app-is-a-blob/
3•valzevul•9m ago•0 comments

Vibe Coding as 2025 word of the year in Collins dictionary

https://en.wikipedia.org/wiki/Word_of_the_year
1•py4•11m ago•0 comments

Why Florida Crocs Are Thriving Outside a Nuclear Power Plant

https://www.smithsonianmag.com/smart-news/florida-crocs-are-thriving-outside-nuclear-power-plant-...
1•thunderbong•12m ago•0 comments

Broadcom reveals its mystery $10B customer is Anthropic

https://www.cnbc.com/2025/12/11/broadcom-reveals-its-mystery-10-billion-customer-is-anthropic.html
2•indigodaddy•13m ago•0 comments

Show HN: PicPick – AI-powered photo curator using CLIP and face recognition

https://github.com/hardiksondagar/picpick
1•hardiksondagar•16m ago•0 comments

Arborium: Tree-sitter code highlighting with Native and WASM targets

https://arborium.bearcove.eu/
2•zdw•22m ago•0 comments

Show HN: A systems language with runtime reflection and no GC

https://xxml-language.com
1•thatsoulyguy•22m ago•0 comments

Unscii

http://viznut.fi/unscii/
2•Levitating•24m ago•0 comments

Electric vehicle owners face new pay-per-mile tax. What about the environmental?

https://phys.org/news/2025-11-electric-vehicle-owners-pay-mile.html
1•PaulHoule•25m ago•0 comments

Director Rob Reiner dead at 78

https://www.hollywoodreporter.com/movies/movie-news/rob-reiner-dead-harry-met-sally-princess-brid...
3•RickJWagner•25m ago•1 comments

The Generative AI Industry Is Fraudulent, Immoral and Dangerous

https://dianne.skoll.ca/writings/ai-is-bad/
4•pabs3•26m ago•0 comments

The Synchronization Tax

https://www.symmetrybroken.com/the-synchronization-tax/
1•riemannzeta•27m ago•0 comments

Niantic Spatial, Inc

https://www.nianticspatial.com/
1•salkahfi•27m ago•0 comments

How the lives of India's poorest improved in the last 10 years

https://timesofindia.indiatimes.com/toi-plus/business-economy/how-the-lives-of-indias-poorest-imp...
1•ridiculous_leke•28m ago•1 comments

Dark mode is essential, not a design preference

https://seemeplease.com/blog/dark-mode
5•SeeMePlease•32m ago•1 comments

Analog Calendar with LEDs and Switches

https://www.friendlywire.com/projects/analog-calendar/
1•zdw•33m ago•0 comments

Memories of Burger Becky

https://blitter.net/blog/2025/12/14/memories-of-burger-becky/
1•zdw•35m ago•0 comments

Habits That Make a Great Programmer

https://arpitbhayani.me/blogs/better-programmer/
1•daviddada•36m ago•0 comments

Show HN: GPT Prompt from Searchbar – ChatGPT directly from the browser omnibox

https://github.com/ParasKoundal/GPTSearch
1•alohaTool•41m ago•0 comments

How Kalshi Was Built

https://theuncredentialed.substack.com/p/kalshi-building-a-truth-machine
2•uncred•44m ago•0 comments

Singapore should move with urgency on robotaxis

https://speculativedecoding.substack.com/p/is-singapore-being-too-careful-with
1•pradyuprasad•46m ago•0 comments

Ukraine willing to drop ambitions to join NATO, Zelenskyy says

https://www.theguardian.com/world/2025/dec/14/ukraine-willing-to-drop-ambitions-to-join-nato-zele...
3•geox•46m ago•0 comments

What happens when the coding becomes the least interesting part of the work

https://obie.medium.com/what-happens-when-the-coding-becomes-the-least-interesting-part-of-the-wo...
1•doppp•1h ago•0 comments

Real-time volcanic forecasting using seismic ambient noise analysis (AGU 2025)

https://agu.confex.com/agu/agu25/meetingapp.cgi/Paper/1891387
1•oldfuture•1h ago•0 comments

Single-shot light-speed computing might replace GPUs

https://newatlas.com/computers/single-shot-tensor-optical-computing/
1•ashishgupta2209•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•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.