frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

I built a game where you guess the AI prompt behind images

https://www.indiehackers.com/post/i-built-a-game-where-you-guess-the-ai-prompt-behind-images-RakW...
1•irtizahammad•53s ago•0 comments

macOS for Developers: 5 Essential Skills to Master Terminal, Homebrew and Docker

https://rakiabensassi.substack.com/p/macos-for-developers-5-essential
1•rakiabensassi•58s ago•0 comments

The Moments That Made 2025

https://rakiabensassi.substack.com/p/the-moments-that-made-2025
1•rakiabensassi•2m ago•0 comments

The Great Transition or the Great Integration?

https://horkan.com/2026/03/12/the-great-transition-or-the-great-integration
1•wayne_horkan•3m ago•0 comments

Support Celestrak

https://giving.classy.org/campaign/750670/donate
1•d_silin•8m ago•0 comments

Adjustments to the China Storefront of the App Store on iOS and iPadOS

https://developer.apple.com/news/?id=dadukodv
1•surprisetalk•11m ago•0 comments

Elon Musk: xAI was not built right first time round; is being rebuilt

https://twitter.com/elonmusk/status/2032201568335044978
3•mellosouls•14m ago•1 comments

Enhanced Atkinson Hyperlegible Font (2025)

https://www.brailleinstitute.org/about-us/news/braille-institute-launches-enhanced-atkinson-hyper...
1•droidjj•15m ago•0 comments

OSS Anti Surveillance: project to track, oppose, and remove surveillance in FOSS

https://github.com/AntiSurv/oss-anti-surveillance
1•iamnothere•16m ago•1 comments

Explainer: What is Basel and why has it been so contentious?

https://www.reuters.com/legal/legalindustry/what-is-basel-why-has-it-been-so-contentious-2026-03-12/
1•petethomas•19m ago•0 comments

Show HN: The Common Infrastructure for Agentic Communication

https://cyrisai.dev/
1•krishnamzg•24m ago•0 comments

Adapting to the New AI Landscape in Software Engineering

https://docs.google.com/document/d/1-vxazqwALKGivwedpGET4j1ipgab09C6RbLMTZ5ve5U/edit?tab=t.wi7nr0...
1•alexjray•24m ago•0 comments

Fed to loosen capital requirements for big US banks

https://www.ft.com/content/a1c81f17-201f-4e3f-8e02-e0b304f1b6a1
2•petethomas•25m ago•2 comments

How HN: PDF Table Extractor – AI-powered tool to extract tables from PDFs to CSV

https://pdf-table-extractor-5wak.vercel.app
1•atdl•26m ago•1 comments

What's My ΔEOK JND?

https://www.keithcirkel.co.uk/whats-my-jnd/
1•donohoe•30m ago•1 comments

Agent Skills for Interview Preparation

https://github.com/jiito/interview-prep-skills
1•jiito•32m ago•0 comments

Probabilistic Execution Beyond Classical Systems

https://www.authorea.com/users/903147/articles/1391658-probabilistic-execution-beyond-classical-s...
1•huiwenhan•32m ago•1 comments

Judgment and creativity are all you need

https://lethain.com/judgment-is-all-you-need/
2•donutshop•33m ago•0 comments

Hackers reportedly stole nearly 1,000TB of data from Telus Digital

https://mobilesyrup.com/2026/03/12/hackers-steal-nearly-1000tb-of-data-from-telus-digital/
2•whynotmaybe•35m ago•1 comments

Management in the Age of AI

https://blog.staysaasy.com/p/management-in-the-age-of-ai
1•donutshop•35m ago•0 comments

To Sparsify or to Quantize: A Hardware Architecture View

https://www.sigarch.org/to-sparsify-or-to-quantize-a-hardware-architecture-view/
2•matt_d•51m ago•1 comments

Tennessee grandmother jailed after AI face recognition error links her to fraud

https://www.theguardian.com/us-news/2026/mar/12/tennessee-grandmother-ai-fraud
31•danso•53m ago•6 comments

Don't Vibe – Prove

https://ngrislain.github.io/projects/2026-3-12-dont-vibe--prove/
4•ngrislain•58m ago•0 comments

I built the Vy replacement that launches March 26th, the day Vy shuts down

https://inceptive-ai.com
2•alymaknojiya•58m ago•3 comments

Meta delays rollout of new AI model after performance concerns

https://www.nytimes.com/2026/03/12/technology/meta-avocado-ai-model-delayed.html
5•wibbily•1h ago•2 comments

Adobe's longtime CEO to exit role amid AI disruption, shares fall

https://www.reuters.com/sustainability/boards-policy-regulation/adobe-announces-ceo-transition-sh...
5•tartoran•1h ago•0 comments

One plan/spec to rule them all (at least replace lots of docs)

3•wek•1h ago•0 comments

In space, no one can hear you kernel panic

https://increment.com/software-architecture/in-space-no-one-can-hear-you-kernel-panic/
2•p0u4a•1h ago•1 comments

Rivian Introduces R2 Lineup, Sharing Full Trims and Pricing

https://rivian.com/newsroom/article/rivian-introduces-r2-lineup
3•freetime2•1h ago•1 comments

Show HN: Nix on Windows –- proof-of-concept demo

https://github.com/nix-windows/nix-windows-demo
7•Ericson2314•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•9mo 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•9mo 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•9mo 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•9mo 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.