frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The Complete Guide to Deploying Rails 8 with Kamal on Hetzner

https://mooktakim.com/blog/deploying-rails-with-kamal/
1•mooktakim•22s ago•0 comments

I built a tiny CLI that writes my commit messages from Git diff

https://github.com/saccofrancesco/gitsloth
1•s4ccofr4ncesco•2m ago•0 comments

Speaking of Voxtral

https://mistral.ai/news/voxtral-tts
1•claudiug•2m ago•0 comments

Show HN: Drift – Linter for Documentation Rot

https://fiberplane.com/blog/drift-documentation-linter/
1•keturakis•6m ago•0 comments

Every Venue and Every Concert in San Diego 2026

https://www.sdconcerts.app
1•goldkey•7m ago•0 comments

A cross-shell framework for managing aliases, plugins, completions, and themes

https://github.com/g-udi/gaudi-shell
1•ahmadassaf•9m ago•1 comments

Chicago artist creates tourism posters for city's neighborhoods

https://www.chicagotribune.com/2026/03/25/chicago-neighborhood-posters/
2•NaOH•11m ago•0 comments

DataSwift – A client-side toolkit for mock data, JSON parsing, and CSV to SQL

https://data-swift-kappa.vercel.app
1•dearmmv•12m ago•0 comments

AI will test governments on jobs, training, and public trust, Hoover panels warn

https://www.hoover.org/news/ai-will-test-governments-jobs-training-and-public-trust-hoover-panels...
1•hhs•15m ago•0 comments

The Hard Problem of Consciousness: Triveritas and the Third Impossibility

https://zenodo.org/records/18930279
1•amelius•17m ago•0 comments

Apple Discontinues Mac Pro

1•alifeinbinary•17m ago•0 comments

Order Granting Preliminary Injunction – Anthropic vs. U.S. Department of War [pdf]

https://storage.courtlistener.com/recap/gov.uscourts.cand.465515/gov.uscourts.cand.465515.134.0.pdf
3•theindieman•17m ago•2 comments

Drift – a terminal screensaver that activates when you're idle

https://github.com/phlx0/drift
1•phlx0•20m ago•0 comments

A 100% serverless RAG that extracts complex tables better than NotebookLM

1•saurav-dev•21m ago•0 comments

Why a company is investigating rapes at an ICE detention center, not the sheriff

https://apnews.com/article/otay-mesa-immigration-center-rape-investigations-f14e4687075f84ddb52d4...
2•petethomas•22m ago•0 comments

Islamic Astronomy and Copernicus [pdf]

https://www.tuba.gov.tr/files/yayinlar/bilim-ve-dusun/TUBA-978-625-8352-02-3.pdf
1•teleforce•23m ago•0 comments

Uber and Lyft users overpay when they don’t price check: study

https://hub.jhu.edu/2026/01/02/uber-lyft-study-carey-business-school/
1•hhs•24m ago•0 comments

RunKoda – Real-time collaborative IDE where AI agents don't conflict

https://runkoda.com
1•SNAFI•24m ago•0 comments

New York's Cannabis Business

https://www.bbc.com/worklife/article/20260325-is-new-yorks-weed-business-really-flying-high
1•1659447091•26m ago•0 comments

What is economics these days?

https://marginalrevolution.com/marginalrevolution/2026/03/what-is-economics-these-days.html
1•hhs•27m ago•0 comments

Simulated microgravity alters fertilization and embryo development in mammals

https://www.nature.com/articles/s42003-026-09734-4
1•geox•28m ago•0 comments

Fedora Moving from Pagure to Forgejo

https://communityblog.fedoraproject.org/the-forge-is-our-new-home/
1•birdculture•28m ago•0 comments

Trump Administration Plans to Require Higher Wages for H-1B Visa Holders

https://www.wsj.com/politics/policy/trump-administration-plans-to-require-higher-wages-for-h-1b-v...
3•petethomas•30m ago•0 comments

2023

https://www.hyperdimensional.co/p/2023
1•jger15•31m ago•0 comments

Arctic Winter Sea Ice Ties Record Low, NASA, NSIDC Scientists Find

https://science.nasa.gov/earth/arctic-winter-sea-ice-2026/
1•martinpw•33m ago•0 comments

Show HN: 96.2% on LongMemEval – world record, built solo in 16 days for $1k

https://github.com/JordanMcCann/agentmemory
1•JordanMcCann•36m ago•0 comments

Husband "cheating" on wife with AI chatbot

https://old.reddit.com/r/BestofRedditorUpdates/comments/1s16oqw/cheating_with_ai/
2•cercatrova•36m ago•0 comments

Uptime of GitHub Pages Alternatives

https://alexsci.com/blog/static-hosting-uptime/
3•QuadmasterXLII•37m ago•0 comments

The Apple Charging Situation

https://randsinrepose.com/guides/apple-charging-guide.html
3•colinprince•40m ago•0 comments

Upgrading K8s to 1.35? cgroup v1 is now rejected by default

https://randomwrites.com/operations/23-Cluster-Upgrade-1-34-to-1-35
2•mutahirs•41m ago•0 comments
Open in hackernews

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

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