frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Markdown editor with live preview built in C++

https://github.com/MinottiAlessandro/Emerald
1•BBones_•1m ago•1 comments

Show HN: OxiSH, a modern, memory-safe SSH server

https://dirkjan.ochtman.nl/writing/2026/08/13/announcing-oxish.html
1•dochtman•1m ago•0 comments

A History of the Sentence "Buffalo buffalo buffalo buffalo buffalo."

https://cse.buffalo.edu/~rapaport/BuffaloBuffalo/buffalobuffalo.html
1•KomoD•2m ago•0 comments

Show HN: A Rosetta Stone for UI component libraries

https://www.frontfamily.com/
2•ch-bas•2m ago•0 comments

Show HN: Binaural beats CLI with server/IPC mode and custom presets

https://github.com/axyz/binaural
1•axyz•2m ago•0 comments

Unsloth/DeepSeek-V4-Pro-0813-GGUF

https://huggingface.co/unsloth/DeepSeek-V4-Pro-0813-GGUF
2•asoberbeck•2m ago•0 comments

Who Vets AI's Code? The Scale Challenge Facing Open Source Ingestion

https://www.bleepingcomputer.com/news/security/who-vets-ais-code-the-scale-challenge-facing-open-...
1•DemiGuru•2m ago•0 comments

Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo

https://en.wikipedia.org/wiki/Buffalo_buffalo_Buffalo_buffalo_buffalo_buffalo_Buffalo_buffalo
1•KomoD•2m ago•0 comments

Dasharo Compatible with MSI Pro Z690-A/Z790-P Release v1.1.7/v0.9.5

https://blog.3mdeb.com/2026/2026-08-13-msi_z690-a_z790-p_v1.1.7_v0.9.5_release/
1•pietrushnic•3m ago•1 comments

Cards Against Humanity: Who Wants to Fuck with Elon Musk?

https://www.cardsagainsthumanity.com/elonhasnofriends
2•cdrnsf•4m ago•0 comments

Why did I build a product no one needs?

https://metedata.substack.com/p/017-why-did-i-build-a-product-no
1•young_mete•4m ago•0 comments

Prospects of TrenchBoot (TCG DRTM) on ARM

https://blog.3mdeb.com/2026/2026-08-12-trenchboot-on-arm/
1•pietrushnic•5m ago•1 comments

MIT neuroscientists discover the brain can reason without words

https://www.sciencedaily.com/releases/2026/08/260811011140.htm
1•sundarurfriend•6m ago•0 comments

My experience buying ads in ChatGPT: the good, the bad and the ugly

https://successfulsoftware.net/2026/08/13/my-experience-buying-ads-in-chatgpt-the-good-the-bad-an...
1•nozzlegear•6m ago•1 comments

Could geothermal roads help prevent potholes before they form?

https://www.surrey.ac.uk/news/could-geothermal-roads-help-prevent-potholes-they-form-surrey-trial...
1•geox•7m ago•0 comments

Show HN: How to use Mu – tools for agents – with x402 payments

https://micro.mu/blog/post?id=1786633600633959421
1•asim•8m ago•0 comments

Claudish-to-English makes Claude output comprehensible

https://github.com/gvzdv/claudish-to-english
1•rickcarlino•8m ago•0 comments

The Improbable, Inevitable Return of the Suit

https://www.bloomberg.com/news/articles/2026-08-13/the-suit-makes-a-fashion-comeback
2•tmoertel•8m ago•0 comments

Incremental Learning

https://www.super-memory.com/help/il.htm
1•Tomte•9m ago•0 comments

2,500-year-old sculpture discovered at UNESCO site in Turkey

https://www.theartnewspaper.com/2026/08/07/colossal-2500-year-old-sculpture-discovered-turkey-une...
1•speckx•10m ago•0 comments

Zoom Zero-Click Vulnerabilities

https://a.security/blog/asecurity-zoomsday
3•vsgherzi•10m ago•0 comments

Design with a Soul: How to make your Vibe-coded site not look like AI Slop

1•Ozzie-D•12m ago•0 comments

Show HN: Kanea – Container orchestration in one binary

https://github.com/m18h/kanea
1•messandoh•12m ago•0 comments

Toddler's tragic death from brain-destroying amoeba offers lessons for doctors

https://arstechnica.com/health/2026/08/an-ultra-rare-amoeba-was-destroying-a-toddlers-brain-docto...
2•Brajeshwar•12m ago•0 comments

In praise of designer-ish babies

https://www.economist.com/leaders/2026/08/13/in-praise-of-designer-ish-babies
2•shadow28•13m ago•1 comments

Build a Software Factory on Vercel

https://github.com/vercel-labs/eve-software-factory-template
1•flashbrew•13m ago•0 comments

Eve Software Factory

https://ask-foreman.dev/
2•flashbrew•14m ago•0 comments

Show HN: Lark, OSS realtime database, drop-in compatible with Firebase SDKs

https://github.com/lark-sh/lark
1•silverlight•14m ago•0 comments

Forward Deployed Executives – The Next Billion-Dollar AI Unblock

https://www.rickmanelius.com/p/forward-deployed-executives-the-next
2•hank2000•15m ago•0 comments

LoongLeak: A Vulnerability Affecting Chinese Loongson 3A5000 and 3A6000 CPUs

https://loongleakattack.com/
3•csmantle•15m ago•0 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.