frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Kavka's Toxin Puzzle

https://en.wikipedia.org/wiki/Kavka%27s_toxin_puzzle
1•rzk•1m ago•0 comments

Harry Potter by Balenciaga (2026) [video]

https://www.youtube.com/watch?v=gtnt84CDP-s
1•GeoAtreides•2m ago•0 comments

I'm struggling and I don't have anyone else to share this with except you

3•owlcompliance•3m ago•0 comments

Queen's Wish: A Portmortem of Mixed Success

https://bottomfeeder.substack.com/p/queens-wish-a-portmortem-of-mixed
1•Tomte•3m ago•0 comments

The Agency: Meticulously crafted AI agent personalities

https://github.com/msitarzewski/agency-agents
1•danebalia•4m ago•1 comments

Practical Type Inference: High‑Throughput Recovery of Real‑World Types

https://arxiv.org/abs/2603.08225
1•matt_d•4m ago•0 comments

New 'negative light' technology hides data transfers in plain sight

https://www.unsw.edu.au/newsroom/news/2026/03/New-negative-light-technology-hides-data-transfers-...
1•wjSgoWPm5bWAhXB•6m ago•0 comments

'a window into the past': The homes revealing how Tudor people lived

https://www.bbc.com/culture/article/20260309-the-homes-revealing-how-tudor-people-really-lived
1•makaimc•6m ago•0 comments

Rabbit r1 with whatever model you want

https://github.com/ShayneP/rabbit-r1-livekit-skill
1•ShayneP•8m ago•1 comments

Request Copilot code review from GitHub CLI

https://github.blog/changelog/2026-03-11-request-copilot-code-review-from-github-cli/
2•danebalia•9m ago•1 comments

Microsoft brings new "Xbox mode" to Windows 11 PCs next month

https://www.windowscentral.com/microsoft/windows-11/windows-11-xbox-mode-announcement-gdc-2026-pr...
1•nikodunk•9m ago•0 comments

WordPress/PHP-AI-client: provider agnostic PHP client SDK to communicate with AI

https://github.com/WordPress/php-ai-client
1•ulrischa•9m ago•0 comments

Show HN: CAS – I reverse-engineered Claude Code to build a better orchestrator

https://github.com/codingagentsystem/cas
1•aceelric•10m ago•1 comments

Me preocupa más ver a un rumano con cara de "yo esto ya lo vi hace añOS"

https://borjamoskv.substack.com/p/el-tema-no-es-cuando-la-va-a-superar
1•borjamoskv•11m ago•0 comments

Stop rebuilding Word documents with PDF libraries

https://tmplvision.io/
1•benny00100•11m ago•1 comments

ThoughtWorks Retreat: Where does engineering go? [pdf]

https://www.thoughtworks.com/content/dam/thoughtworks/documents/report/tw_future%20_of_software_d...
1•danebalia•11m ago•1 comments

Someone forked and submitted my open-source project to a contest, and won $1000

https://cyao.dev/blog/contest.html
2•Cyao•11m ago•0 comments

Pro-Iran hackers claim cyberattack on major US medical device maker

https://www.cnn.com/2026/03/11/politics/pro-iran-hackers-cyberattack-medical-device-maker
7•zomg•13m ago•1 comments

PeerTube v8.1 Released

https://joinpeertube.org/news/release-8.1
3•toomuchtodo•14m ago•1 comments

Constellation Draw

https://neal.fun/constellation-draw
3•xia•16m ago•0 comments

Browserbase Fetch: Simple API for extracting web page content for AI agents

https://www.browserbase.com/blog/fetch-api
1•Kylejeong21•17m ago•0 comments

A Definition-Based Wordle Game

https://www.jlauf.com/dictle/
2•jlauf•17m ago•0 comments

Show HN: AutosArena – The most complete automotive data platform, available free

https://autos-arena.com
1•seeyam14•18m ago•0 comments

SetupClaw – White-Glove OpenClaw Deployment for Founders and Exec Teams

https://setupclaw.com
2•personjerry•18m ago•1 comments

Made my own programming language, kinda advanced

https://github.com/entrenchedosx/spl
1•redempt1on•19m ago•1 comments

Show HN: Pointify – Retro analog gauges for system stats and Claude usage

https://github.com/luftaquila/pointify
2•luftaquila•19m ago•0 comments

Charging Strategies for Battery Electric Trucks in Germany

https://www.mdpi.com/2032-6653/17/2/106
1•PaulHoule•19m ago•0 comments

Most Watched Software Engineering Talks of 2025

https://www.techtalksweekly.io/p/100-most-watched-software-engineering-talks-of-2025
2•m4lloc•20m ago•0 comments

Homebrew 5.1.0

https://brew.sh/2026/03/10/homebrew-5.1.0/
5•mikemcquaid•20m ago•1 comments

Show HN: Sandbox Flow – A Playground for Sandboxes

https://github.com/BandarLabs/sandboxflow
1•mkagenius•22m 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.