frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Raiden Warned About AI Censorship [video]

https://www.youtube.com/watch?v=-gGLvg0n-uY
1•DeathArrow•37s ago•0 comments

Show HN: Thalo – A "programming" language for structured knowledge

https://github.com/rejot-dev/thalo
1•WilcoKruijer•4m ago•0 comments

From Tomorrow Back to Yesterday: A Tale of Two Web Architectures – Yang [video]

https://www.youtube.com/watch?v=8W6Lr1hRgXo
1•adityaathalye•5m ago•0 comments

The State of Modern AI Text to Speech Systems for Screen Reader Users

https://stuff.interfree.ca/2026/01/05/ai-tts-for-screenreaders.html
1•tuukkao•10m ago•0 comments

Apple is burying the Time Capsule, but how to replace it?

https://sixcolors.com/post/2026/01/apple-is-burying-the-time-capsule-but-how-to-replace-it/
2•tosh•11m ago•0 comments

What time you should arrive at cinema to avoid adverts

https://news.sky.com/story/what-time-you-should-actually-arrive-at-cinema-to-avoid-adverts-13149863
1•austinallegro•11m ago•0 comments

Subject of Unique Interest: Mary Freeman Heuston Lewis and William Dean Howells

https://commonplace.online/article/a-subject-of-unique-interest/
1•bryanrasmussen•13m ago•1 comments

DeepSeek's mHC: Stabilizing Training Divergence from 3,000x to 1.6x

2•Research_Brief•13m ago•0 comments

How to Think About Self-Attention Intuitively

https://www.henrydashwood.com/posts/attention-intuition
1•HenryDashwood•16m ago•0 comments

Nvidia PersonaPlex: natural conversation AI

https://research.nvidia.com/labs/adlr/personaplex/
1•ricardobeat•18m ago•0 comments

Doing Gigabit Ethernet over My British Phone Wires

https://thehftguy.com/2026/01/22/doing-gigabit-ethernet-over-my-british-phone-wires/
2•user5994461•20m ago•0 comments

Microservices Architecture Fails Due to Poor Product Topology

https://www.hyperact.co.uk/blog/product-topology
1•birdculture•21m ago•0 comments

Tried Qwen3-TTS Open source to clone my voice and created a video

https://www.youtube.com/watch?v=0LU9nmnR0cs
1•naveen-zerocool•27m ago•0 comments

Why are there so many CPU bugs nowadays

https://mas.to/@gabrielesvelto/115939583202357863
6•riffraff•28m ago•0 comments

Ask HN: Do You Prefer Cursor over Codex or Claude Code? Why?

3•halamadrid•28m ago•0 comments

Show HN: SpiraCSS – CSS architecture where tooling and AI handle the rules

https://spiracss.jp/
1•zetsubo•29m ago•0 comments

Can You Run Recursion on Ideas?

1•codenighter•29m ago•0 comments

Picking up the missing pieces of Apple's Creator Studio

https://sixcolors.com/post/2026/01/whats-the-real-value-in-creator-studio/
1•tosh•30m ago•0 comments

Replacing Protobuf with Rust to go 5 times faster

https://pgdog.dev/blog/replace-protobuf-with-rust
2•whiteros_e•31m ago•0 comments

Section 230 Didn't Fail Rand Paul. He Just Doesn't Like the Remedy That Worked

https://www.techdirt.com/2026/01/22/section-230-didnt-fail-rand-paul-he-just-doesnt-like-the-reme...
1•beardyw•32m ago•0 comments

Adep

https://adep-france.fr/
1•compado•33m ago•0 comments

Howard Lutnick heckled at Davos dinner as Christine Lagarde walks out

https://www.ft.com/content/e2ae0417-6146-4428-96db-0484a6b024d1
1•saubeidl•35m ago•1 comments

AI-exposed jobs deteriorated before ChatGPT

https://arxiv.org/abs/2601.02554
1•dandelionv1bes•37m ago•0 comments

Tell HN: Alibaba Sucks

1•burnt-resistor•37m ago•1 comments

A Microsoft engineer reveals how Windows 95's 'secret' fast restart worked

https://www.xda-developers.com/microsoft-engineer-reveals-how-windows-95s-secret-fast-restart-wor...
1•daniel_iversen•39m ago•0 comments

Ask HN: How can a new back end dev start contributing to real-world open source?

1•hejhdiss•41m ago•0 comments

Ask HN: How can a new back end dev start contributing to real-world open source?

1•hejhdiss•41m ago•0 comments

Towards Execution-Grounded Automated AI Research

https://arxiv.org/abs/2601.14525
2•abracos•48m ago•0 comments

We’re all VCs now:The skills developers need in the AI era

https://lerner.co.il/2026/01/21/were-all-vcs-now-the-skills-developers-need-in-the-ai-era/
1•reuven•49m ago•0 comments

Tanker og perspektiver I fokus

1•Aksel-Louis•50m ago•0 comments
Open in hackernews

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

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