frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

I made Aplix, but need honest reviews about it

1•itsmsr•35s ago•0 comments

Model-based linguistic space for transmitting our thoughts from brain to brain

https://pubmed.ncbi.nlm.nih.gov/39096896/
1•Anon84•1m ago•0 comments

Microsoft blocks trick to unlock native NVMe driver, but workarounds still exist

https://www.tomshardware.com/software/windows/microsoft-blocks-the-registry-hack-trick-that-unloc...
2•josephcsible•13m ago•0 comments

Ask HN: AI companies' bots are making my server slow, what do you do?

1•aabbcc1241•15m ago•1 comments

Alibaba Unveils New Chip Design to Meet Surging Demand for AI

https://www.bloomberg.com/news/articles/2026-03-24/alibaba-unveils-new-chip-design-to-meet-surgin...
1•voxadam•18m ago•1 comments

Show HN: ArXiv metadata as Parquet files (2.99M papers, 1.44GB, 417 files)

https://huggingface.co/datasets/open-index/open-arxiv
1•tamnd•20m ago•0 comments

FCC Clearing the Air on Wi-Fi Software Updates (2015)

https://www.fcc.gov/news-events/blog/2015/11/12/clearing-air-wi-fi-software-updates
1•walterbell•25m ago•0 comments

Sovereign AI OS and SAMN Introduction

1•twocats7701•27m ago•0 comments

How Do US Men and Women Spend Their Time?

https://www.pewresearch.org/social-trends/feature/how-do-u-s-men-and-women-spend-their-time/
1•gmays•27m ago•0 comments

Firefox ext: Bkmker · Your bookmarks, encrypted and private

https://addons.mozilla.org/en-US/firefox/addon/bkmker/
2•fullstacking•33m ago•0 comments

OpenTarget Core: Laser Shooting Platform for Raspberry Pi Using OpenCV

https://github.com/JSK-Project/OpenTarget-Core
1•laurieg•36m ago•0 comments

Aspect Ratios with Sinners Director Ryan Coogler (2025)

https://www.youtube.com/watch?v=78Ru62uFM0s
1•hbcondo714•38m ago•0 comments

Halo-Gravity Traction

https://www.childrenshospital.org/conditions-treatments/halo-gravity-traction
1•walterbell•41m ago•0 comments

California bill aims to help vibe coders

https://www.semafor.com/article/03/20/2026/california-bill-aims-to-help-vibe-coders
2•gnabgib•42m ago•1 comments

A city that wasted nothing [video]

https://aeon.co/videos/the-extraordinary-efficiency-of-japans-edo-economy
4•billybuckwheat•43m ago•1 comments

Show HN: Locro – Fast and accurate local OCR through Chrome's screen_ai

https://github.com/sergiocorreia/clv-locro
1•zzleeper•43m ago•0 comments

'Microshifting' puts a new spin on 9-to-5 schedules

https://apnews.com/article/microshifting-work-time-flexible-schedule-balance-97a98519916b447cd60c...
1•donutshop•44m ago•0 comments

California bill to stop 'dominant platforms' from blocking competition

https://yro.slashdot.org/story/26/03/22/2025249/tech-leaders-support-california-bill-to-stop-domi...
4•MilnerRoute•45m ago•0 comments

Mars to Wars: New Space pivots to weaponize space

https://www.defensenews.com/space/2026/02/19/spacex-and-blue-origin-abruptly-shift-priorities-ami...
3•infinitewars•46m ago•1 comments

The Un-Slop Fiction Prize

https://www.hyperstitionai.com/unslop
1•Curiositry•49m ago•0 comments

Blackburn AI Bill Repeals Section 230, Expands AI Liability, Age Verification

https://reclaimthenet.org/trump-america-ai-act-section-230-repeal-ai-liability-age-verification
5•walterbell•51m ago•0 comments

Nashville library launches Memory Lab for digitizing home movies

https://www.axios.com/local/nashville/2026/03/16/nashville-library-digitize-home-movies
3•toomuchtodo•51m ago•0 comments

Show HN: Generate, preview, and export 3D models without complex software

https://www.ai3dgen.com
2•stewardyunn•57m ago•0 comments

My Prodigal Brainchild

https://nealstephenson.substack.com/p/my-prodigal-brainchild
2•martinlaz•57m ago•0 comments

Show HN: A form builder that feels like chatting

https://www.typerson.com
1•briandev•1h ago•0 comments

Box of Secrets: Discreetly modding an apartment intercom with Matter

https://www.jackhogan.me/blog/box-of-secrets/
16•swq115•1h ago•1 comments

PwC will say goodbye to staff who aren't convinced about AI

https://www.theregister.com/2026/03/19/pwc_ai/
4•gnabgib•1h ago•1 comments

StackOverflow's questions per day have fallen 99%

https://meta.stackoverflow.com/questions/433864/do-you-agree-with-gergely-that-stack-overflow-is-...
13•stevage•1h ago•3 comments

Music manuscripts from Cologne now linked to digitized copies

https://rism.info/library_collections/2026/03/19/Music-manuscripts-from-Cologne.html
1•gnabgib•1h ago•0 comments

Where did 400 MiB go?

https://frn.sh/pmem/
3•thunderbong•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•10mo 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•10mo 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•10mo 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•10mo 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.