frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Keeping FairScan simple isn't simple

https://fairscan.org/blog/keeping-fairscan-simple/
1•Matumio•2m ago•0 comments

Reducing protein intake could support healthy aging by reshaping metabolism

https://medicalxpress.com/news/2026-07-protein-intake-healthy-aging-reshaping.html
1•pseudolus•4m ago•0 comments

Rust – What .boxed() costs you (and a tiny crate to avoid it)

https://ae2.rs/post/boxed-vs-box-pin
1•ae2•4m ago•0 comments

How the smartest people use AI

https://www.youtube.com/watch?v=PcEWx_001aU
1•mattm•5m ago•0 comments

Deployments are now up to 7 seconds faster

https://vercel.com/changelog/deployments-are-now-up-to-7-seconds-faster
1•flyaway123•6m ago•0 comments

Toasts pose significant accessibility concerns and are not recommended for use

https://primer.style/accessibility/patterns/accessible-notifications-and-messages/#toasts
1•plucafs•6m ago•0 comments

How to Spot AI Writing

https://www.economist.com/culture/2026/07/30/how-to-spot-ai-writing
1•ijidak•7m ago•0 comments

Christopher Nolan's Collapsing Worlds

https://www.patreon.com/PastLivesMedia/posts/christopher-165426703
2•softwaredoug•8m ago•0 comments

DeepSeek's Plan for AGI Is the Costco Hot Dog

https://kuber.studio/blog/AI/DeepSeeks-Plan-for-AGI-is-the-Costco-Hot-Dog
1•kuberwastaken•9m ago•0 comments

Show HN: Reimagine place photos with Nano Banana

https://aigoogleearth.app/
1•Evanmo666•9m ago•0 comments

Wyro – Draw a backend on a canvas, export TypeScript with no lock-in

1•Paaul01•10m ago•0 comments

$350 for a single slice of pie?

https://www.adafruit.com/product/6125?gad_source=4&gad_campaignid=23986111167&gbraid=0AAAAADx9JvQ...
1•replatformradar•12m ago•0 comments

Two 500-year-old mummies confirm Europeans brought smallpox to the Americas

https://english.elpais.com/science-tech/2026-07-31/two-500-year-old-mummies-confirm-europeans-bro...
1•geox•14m ago•1 comments

Show HN: Job board and MCP server for AI developers

https://frontierroles.com/
1•alastairr•17m ago•0 comments

Building a fitness brain for hybrid athletes

https://www.heykipp.io/
1•mlabouardy•17m ago•0 comments

From boiling lead and black art: The history of mathematical typography (2017)

http://www.practicallyefficient.com/2017/10/13/from-boiling-lead-and-black-art.html
1•EndXA•17m ago•0 comments

Trump's Fixation on Arctic Ships Led to Billions in No-Bid Contracts

https://www.nytimes.com/2026/08/01/climate/trump-arctic-ships.html
2•duxup•21m ago•1 comments

Plug-In Solar Panels Are Starting to Sprout in U.S. Backyards

https://www.nytimes.com/2026/07/31/business/energy-environment/plug-in-balcony-solar.html
2•simonpure•21m ago•0 comments

Neuvra

https://www.neuvraai.com/
1•kiraratakaoka•22m ago•1 comments

Show HN: Warpgate 0.27 (FOSS Teleport alternative) adds RDP/VNC support

https://warpgate.null.page/
1•hardex•22m ago•0 comments

Apple Raises iCloud+ Prices in 8 Countries

https://www.macrumors.com/2026/07/17/apple-icloud-plus-price-increase/
1•meysamazad•26m ago•0 comments

Astronomers Have Detected an Exomoon for the First Time

https://www.wired.com/story/astronomer-detect-exomoon-for-first-time/
1•wglb•27m ago•0 comments

NPM bypass-2FA tokens can no longer manage accounts or packages

https://github.blog/changelog/2026-07-31-restricting-npm-bypass-2fa-granular-access-tokens/
1•nyku•29m ago•0 comments

How to plant a nuclear plant in Iran

https://www.digitaldigging.org/p/how-to-plant-a-nuclear-plant-in-iran
1•georgecmu•31m ago•0 comments

Neuroscience of Enduring Change: Erasing Problematic Emotional Learnings [pdf]

https://coherencetherapy.org/files/Ecker-2020-Erasing_Problematic_Emotional_Learnings-Psychothera...
1•plucafs•32m ago•0 comments

Decidim is a digital platform for citizen participation

https://decidim.org/
1•riffraff•32m ago•0 comments

Replicating the physics of the Gameboy screen for realistic emulation

https://note.com/kathoc/n/n5ceb773a3dbc
3•iamwil•33m ago•0 comments

Tglist – Telegram reach drops as post rate grows – except for Ukrainian channels

https://tglist.io/rnd/posting-frequency-reach-decay
1•coubri•35m ago•0 comments

Scalzi – Another Reason Not to Use "AI" for Your Writing

https://whatever.scalzi.com/2026/07/31/another-reason-not-to-use-ai-for-your-writing/
2•roomey•36m ago•0 comments

Google kills Earth AI generator after one day

https://twitter.com/newsfromgoogle/status/2083249962150760610
32•BlueBerry2001•40m ago•23 comments
Open in hackernews

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

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