frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: No-Typing – A free, local-first Whisper dictation app for macOS

1•giddynaya•17s ago•0 comments

The Secret to Success Is 'Monotasking'

https://www.theatlantic.com/health/2026/05/monotasking-inside-the-box-excerpt-david-epstein/687015/
1•fortran77•1m ago•1 comments

NanoBrain – A Markdown+Git "second brain" for Claude Code

https://github.com/siddsdixit/nanobrain
1•siddixit•1m ago•0 comments

Where the sun is overhead, and the monuments built to mark it

https://pilgrimapp.org/sunpath/
1•momentmaker•3m ago•0 comments

Social Media is now Parasocial Media

https://journals.sagepub.com/doi/10.1177/20563051261437487
1•bookofjoe•4m ago•0 comments

Top AI Companies Agree to Pentagon Deals for Classified Work

https://www.wsj.com/tech/ai/top-ai-companies-agree-to-pentagon-deals-for-classified-work-9c621e78
1•ChartMaster22•5m ago•1 comments

Gh-relay:share a readonly browser view of your private repo via a temporary URL

https://github.com/soub4i/gh-relay
1•soubai•7m ago•0 comments

Show HN: Secure-by-default Ollama Docker image with built-in auth, only 70MB

https://github.com/hwdsl2/docker-ollama
1•hwdsl2•8m ago•0 comments

Microtonal Sid Music? Angine de Poitrine Bassline in C64 Basic [video]

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

Bye Spotify, Hello MP3s

https://minimal.bearblog.dev/bye-spotify-hello-mp3s/
1•pastel5•8m ago•0 comments

Pentagon Makes Deals with A.I. Companies to Expand Classified Work

https://www.nytimes.com/2026/05/01/us/politics/pentagon-ai-companies-deals.html
1•doener•8m ago•1 comments

Claude hacked my ("rotary") phone

https://ktoya.me/claude-for-hardware/
1•ktoyame•12m ago•0 comments

If Claude writes the code, what makes me still a developer?

https://betweentheprompts.com/if-claude-writes-the-code/
2•scastiel•13m ago•0 comments

The Great Lightbulb Conspiracy (2014)

https://spectrum.ieee.org/the-great-lightbulb-conspiracy
1•downbad_•14m ago•1 comments

What Strings Will Trump Attach to Dollar Lifelines?

https://www.bloomberg.com/opinion/articles/2026-05-01/us-dollar-backstop-is-weakened-by-politiciz...
1•petethomas•14m ago•0 comments

Wkdomains scan of Y Combinator.com – no llms.txt

https://wkdomains.com/bot/ycombinator.com
1•fcpguru•14m ago•1 comments

Apple accidentally left Claude.md files in today's Apple Support app update

https://twitter.com/CodeByNZ/status/2050123209698066789
1•lr0•15m ago•0 comments

Embedded Rust or C Firmware? Lessons from an Industrial Microcontroller Use Case

https://arxiv.org/abs/2604.25679
1•mrtz•20m ago•0 comments

US ransomware negotiators get 4 years in prison over BlackCat attacks

https://www.bleepingcomputer.com/news/security/us-ransomware-negotiators-get-4-years-in-prison-ov...
1•Brajeshwar•23m ago•0 comments

Ask HN: How do you feel about AI assisted blogging?

1•throwarayes•26m ago•2 comments

Show HN: Glyph – byte-exact substring retrieval (~1.5ms, FM-index)

https://github.com/yasha1971-coder/glyph-engine
1•EMPTYCONTOUR•26m ago•0 comments

Berkshire Has a Website from the '90s and Buffett Fans Say Don't Mess with It

https://www.wsj.com/tech/personal-tech/berkshire-hathaway-shareholder-meeting-warren-buffett-greg...
1•meyum33•26m ago•0 comments

Only One Side Will Be the True Successor to MS-DOS – OS/2 1.x

https://blisscast.wordpress.com/2026/04/21/os2-gui-wonderland-12b/
1•Aloha•27m ago•0 comments

The Attention Your Phone Stole Was Gone

https://thinkingrock.substack.com/p/the-attention-your-phone-stole-was
1•7777777phil•27m ago•0 comments

Show HN: Stanzio, AI presentation tool that designs each slide as real HTML

https://stanzio.fly.dev/
1•mrconter11•28m ago•0 comments

Bolt Graphics Targets FP64 HPC Workloads with Zeus GPU

https://www.hpcwire.com/2026/04/22/bolt-graphics-targets-fp64-hpc-workloads-with-zeus-gpu/
1•rbanffy•28m ago•0 comments

Microsoft rolls out Xbox Mode, bringing a console-like experience to any PC

https://www.xda-developers.com/microsoft-rolls-out-xbox-mode-bringing-a-console-like-experience-t...
2•rbanffy•29m ago•0 comments

An AI reasoning system just discovered a candidate universal law in astrophysics

https://blankline.org/research/universal-bimodal-drift-rate
1•DarenWatson•30m ago•1 comments

Keep your coding agent on track

https://github.com/algorismo-au/lanekeep
1•mightymo1•34m ago•0 comments

Workflow Engine for Async Microservice Flows

https://littlehorse.io/blog/callbacks
2•coltmcnealy•36m ago•1 comments
Open in hackernews

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

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