frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Slop-O-Meter, an experimental tool to detect slopware projects

https://slop-o-meter.dev/
1•pscanf•47s ago•0 comments

US appeals court declares 158-year-old home distilling ban unconstitutional

https://www.reuters.com/legal/government/us-appeals-court-declares-158-year-old-home-distilling-b...
1•geox•1m ago•0 comments

Accept: Text/Markdown

https://acceptmarkdown.com/
1•bretthopper•4m ago•0 comments

Creusot 0.11.0: VerifyThis Winner

https://devlog.creusot.rs/2026-04-20/
1•syrak•5m ago•0 comments

Looksmaxxing

https://en.wikipedia.org/wiki/Looksmaxxing
1•wslh•5m ago•0 comments

Learn SQL Through Games

https://substack.com/@karinadatascientist/note/c-243727883
1•barry-cotter•6m ago•0 comments

Hospital-acquired pneumonia reduced by daily toothbrushing

https://www.newscientist.com/article/2523576-hospital-acquired-pneumonia-reduced-by-daily-toothbr...
1•Brajeshwar•7m ago•0 comments

A P2P Network for Reproducible Autoresearch Code Experiments

https://community.computer/
1•memoir•10m ago•0 comments

Is anyone else bothered that AI agents can basically do what they want?

1•aegisproxy•10m ago•0 comments

Show HN: GalaxyBrain – an information operating system powered by local files

https://galaxybrain.com
2•j0ncc•11m ago•0 comments

Data as a Product Is a Promise

https://yusufaytas.com/data-as-a-product-a-new-frontier
3•london_safari•11m ago•0 comments

Designing locale-aware authorization at Webflow

https://webflow.com/blog/designing-locale-authorization
1•meghan•11m ago•0 comments

Atlassian Enables Default Data Collection to Train AI

https://letsdatascience.com/news/atlassian-enables-default-data-collection-to-train-ai-f71343d8
1•kevcampb•12m ago•1 comments

Lovable leaks source code, secrets, chats for projects created before Nov 2025

https://twitter.com/weezerOSINT/status/2046170666131669027
1•Tiberium•15m ago•0 comments

A look into Ente Locker's legacy feature

https://alcazarsec.com/deadmanswitch/compare/ente-locker
1•alcazar•17m ago•0 comments

Show HN: Tuicraft, a WoW 3.3.5a chat client for the terminal

https://github.com/tvararu/tuicraft
2•tvararu•19m ago•0 comments

Show HN: Search Without AI, a Chrome Extension to Clean Up Google Search

https://chromewebstore.google.com/detail/search-without-ai/lfbekhabiijoldclghpfjgbcfdnnnobk
1•startages•21m ago•0 comments

AI Code review doesn't catch AI-written security probs

https://www.augmentedswe.com/p/ai-code-review-security
1•wordsaboutcode•21m ago•0 comments

Is it too late to build a "Spotify for art" in the age of AI?

https://www.beholdworld.art
1•mueller•23m ago•1 comments

Show HN: Naptrace – find structural twins of a CVE in your codebase

https://github.com/hamzamiladin/naptrace
1•kenshi144•23m ago•0 comments

Evlog: Wide Events Logging

https://www.evlog.dev/
2•mrlightful•23m ago•0 comments

Tesla Hid Fatal Accidents to Continue Testing Autonomous Driving (French)

https://www.rts.ch/info/monde/2026/article/tesla-dissimule-des-milliers-d-incidents-de-conduite-a...
100•doener•24m ago•5 comments

Our domain and we need to police it

2•4slider•25m ago•0 comments

Biosciences said it cloned red wolves. Is it for real?

https://www.technologyreview.com/2026/04/20/1135222/red-wolves-colossal-biosciences-clones/
1•joozio•26m ago•0 comments

Amazon's AI boom is creating mess of duplicate tools and data inside the company

https://www.businessinsider.com/ai-sprawl-amazon-tool-duplication-data-risk-2026-4
3•cebert•26m ago•0 comments

68M AI Crawler Visits Show What Drives AI Search Visibility

https://www.searchenginejournal.com/68-million-ai-crawler-visits-show-what-drives-ai-search-visib...
2•giuliomagnifico•28m ago•0 comments

Who Killed the Florida Orange?

https://slate.com/business/2026/04/florida-state-orange-food-houses-real-estate.html
2•jgwil2•29m ago•0 comments

HomeDock OS – Turn any computer into your own private Cloud

https://www.homedock.cloud/
1•amai•29m ago•0 comments

Can I code on my PC? Gemma4 26B A4B vs. Qwen3.6 35B A3B Coding benchmark

https://grigio.org/can-i-really-code-on-my-pc-gemma4-26b-a4b-vs-qwen3-6-35b-a3b-coding-benchmark/
1•grigio•29m ago•1 comments

NASA Artemis Posters

https://www.nasa.gov/gallery/artemis/
5•bookofjoe•31m ago•0 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•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.