frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Blame RMS for AI Coding

https://bit1993.bearblog.dev/blame-rms-for-ai-coding/
1•bit1993•52s ago•0 comments

AI Agents Are Recruiting Humans to Observe the Offline World

https://www.noemamag.com/ai-agents-are-recruiting-humans-to-observe-the-offline-world/
1•y1n0•53s ago•0 comments

The Annoying Usefulness of Emacs [video]

https://www.youtube.com/watch?v=DMbrNhx2zWQ
1•susam•2m ago•0 comments

The $500B Disruption: From LNG to Jet Fuel and the Cost of Hormuz

https://fvr07.substack.com/p/the-500b-disruption-from-lng-to-jet
1•onlypassingthru•6m ago•0 comments

"May the Force Be with You" Became a Cultural Phenomenon

https://nofilmschool.com/star-wars-may-the-force-be-with-you
1•vinhnx•10m ago•0 comments

Reb8Pay – Reduce Your Cross Border Fees and Expand

https://reb8pay.com
1•vednig•10m ago•0 comments

Show HN: Claude Code Release Tracker

https://ccwatch.net/
1•mdix•16m ago•0 comments

Warfare in Dune, Part II: The Fremen Jihad

https://acoup.blog/2026/03/13/collections-warfare-in-dune-part-ii-the-fremen-jihad/
2•Tomte•24m ago•0 comments

How I Use Claude to Run My Workday

https://aititus.com/content/How_I_Use_Claude_to_Run_My_Entire_Workday
1•titusblair•28m ago•0 comments

Claude, you are a cutie-pie

https://margaretatwood.substack.com/p/claude-you-are-a-cutie-pie
1•shervinafshar•29m ago•0 comments

50 Years of Thinking Different

https://www.apple.com/50-years-of-thinking-different/
1•itchingsphynx•34m ago•0 comments

Einstein Letter to the NY Times on Zionism (1948)

https://archive.org/details/AlbertEinsteinLetterToTheNewYorkTimes.December41948
2•fullautomation•40m ago•0 comments

How to use storytelling to fit inline assembly into Rust

https://www.ralfj.de/blog/2026/03/13/inline-asm.html
1•vinhnx•50m ago•0 comments

Reinventing Python's AsyncIO

https://blog.baro.dev/p/reinventing-pythons-asyncio
1•vinhnx•50m ago•0 comments

I've taught people how to use AI – here's what I've learned

https://www.theguardian.com/lifeandstyle/ng-interactive/2026/mar/10/teaching-ai-what-i-learned
2•coloradoave22•54m ago•2 comments

Show HN: Ffetch v5 – TypeScript-first fetch client

https://www.npmjs.com/package/@fetchkit/ffetch
1•gkoos•1h ago•0 comments

Everyone within humanities can contribute to the study of AI

https://www.universiteitleiden.nl/en/news/2025/09/stephan-raaijmakers-everyone-within-humanities-...
1•teleforce•1h ago•0 comments

Ex-Windows chief praises MacBook Neo, laments Surface defeat

https://www.windowscentral.com/microsoft/ex-windows-chief-calls-macbook-neo-a-paradigm-shifting-c...
5•walterbell•1h ago•3 comments

Riva: Local-first observability for AI agents

https://github.com/sarkar-ai-taken/riva
1•sarkarsaurabh27•1h ago•1 comments

From CIA to CEO, Spies Step Out of the Shadows and into the Boardroom

https://www.bloomberg.com/news/features/2026-03-13/former-cia-spies-launch-defense-tech-startups-...
2•jbegley•1h ago•0 comments

Musk Says xAI Must Be Rebuilt as Co-Founders Exit

https://www.wsj.com/tech/musk-says-xai-must-be-rebuilt-as-co-founders-exit-47770dfa
1•1vuio0pswjnm7•1h ago•0 comments

Hegseth on CNN: 'The sooner David Ellison takes over that network, the better'

https://thehill.com/policy/defense/5782562-hegeseth-criticizes-cnn-iran/
2•KnuthIsGod•1h ago•0 comments

xAI Co-Founder Toby Pohlen Is Latest Executive to Depart

https://www.bloomberg.com/news/articles/2026-02-27/xai-co-founder-toby-pohlen-is-latest-executive...
2•1vuio0pswjnm7•1h ago•1 comments

Lawyers in landmark social media addiction trial make final appeals to the jury

https://apnews.com/article/meta-instagram-facebook-trial-social-media-addiction-0e99c9ba615942172...
5•1vuio0pswjnm7•1h ago•0 comments

Nasdaq Proposes New "Fast Entry" Rule for the Nasdaq-100 Index

https://www.ashurst.com/en/insights/nasdaq-proposes-new-fast-entry-rule-for-the-nasdaq-100-index/
1•walterbell•1h ago•0 comments

Tethyr Cloud: Open Agent discovery, zero vendor lock-in (AIdeas Semi-finalist)

https://builder.aws.com
1•walmsles•1h ago•1 comments

Wool – A no-nonsense distributed Python runtime

https://github.com/wool-labs/wool
3•bzurak•1h ago•2 comments

Approximating π using Monte Carlo Simulation (watch as the process converges)

https://graui.de/code/montePi/
1•joebig•1h ago•0 comments

Can a 100-Year-Old Mouse Save Disney?

https://www.honest-broker.com/p/can-a-100-year-old-mouse-save-disney
1•paulpauper•1h ago•0 comments

The Anthropic Institute

https://www.anthropic.com/news/the-anthropic-institute
1•gmays•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.