frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Lapser Studio – Beautiful timelapse screen recordings effortlessly

https://www.lapser.studio/
1•Osbro•56s ago•0 comments

Ask HN: Can HN ban new accounts? or charge money?

1•randyrand•2m ago•1 comments

Show HN: Benchmarking Tangible Interface Understanding in Long-Horizon Tasks

https://huggingface.co/papers/2511.17649
1•tellarin•2m ago•1 comments

Dangers of Homogeneity: 48% of European Telcos use Nginx, report finds

https://ethiack.com/news/blog/digital-exposure-to-cybercrime-european-telecoms
1•gpaiva21•4m ago•0 comments

A terminal feed reader for HN and Reddit and lobste.rs using Claude Code

https://github.com/emarkou/grokfeed
1•elemar•7m ago•0 comments

Dallas ISD book checkouts soar amid state's cellphone ban for public schools

https://www.cbsnews.com/texas/news/dallas-isd-calendar-school-library-book-checkout-report-texas-...
1•taubek•7m ago•0 comments

Single-file PHP media host with crypto subscriptions

https://github.com/vekuz/durcoin
1•durcoin•7m ago•0 comments

ASML Bibliography

https://neilhacker.com/2026/04/28/asml-article-bibliography/
1•vinhnx•7m ago•0 comments

The unwritten laws of software engineering

https://newsletter.manager.dev/p/the-unwritten-laws-of-software-engineering
2•vinhnx•8m ago•0 comments

Agentic Engineering Management

https://peterszasz.com/agentic-engineering-management/
1•vinhnx•8m ago•0 comments

Show HN: Repid v2 – open-source async Python task queue with AsyncAPI docs

1•aleksul•9m ago•0 comments

Anthropic's Little Brother

https://www.theatlantic.com/technology/2026/04/openai-imitating-anthropic/686975/
2•JumpCrisscross•10m ago•0 comments

DKSplit – Fast word segmentation for domain names (BiLSTM-CRF and ONNX)

https://github.com/ABTdomain/dksplit
1•ABTdomain•12m ago•0 comments

The scientists turning recycled ocean plastic waste into roads

https://www.bbc.co.uk/newsround/articles/clyd05555g6o
1•wjSgoWPm5bWAhXB•13m ago•0 comments

Stop Winning Arguments. Start Using "Claude Mode" Instead

https://basila.medium.com/when-youre-fed-up-arguing-try-switching-to-claude-mode-3249f36c01fb
1•pavovap•15m ago•1 comments

How Did REST Come to Mean the Opposite of REST?

https://htmx.org/essays/how-did-rest-come-to-mean-the-opposite-of-rest/
1•vladde•16m ago•0 comments

Trump admin pays wind developers to quit, back fossil fuel projects

https://www.theregister.com/2026/04/28/trump_admin_pay_off_wind_farm/
1•FpUser•19m ago•0 comments

White House Captions Photo of Trump and King Charles as 'Two Kings'

https://www.forbes.com/sites/antoniopequenoiv/2026/04/28/white-house-captions-photo-of-trump-and-...
1•geox•21m ago•0 comments

Show HN: Vibee.sh – SSH-only VM rental. Instant trial, no signup

https://vibee.sh/
1•lfaoro•23m ago•1 comments

Automatic Enum Stringification in C via Build-Time Code Generation

https://medium.com/@yair.lenga/automatic-enum-stringification-in-c-via-build-time-code-generation...
1•yairlenga•25m ago•1 comments

How will AI crypto trading bots shape automated trading in 2026?

https://www.bitdeal.net/crypto-trading-bot-development
2•harrisonrichrd•27m ago•0 comments

The EU to demand collection of Facebook and Instagram user identities

https://ec.europa.eu/commission/presscorner/home/en
2•miohtama•31m ago•0 comments

Taste Games

https://dynomight.net/taste-games/
1•pdrobnjak•32m ago•0 comments

War panic: if you prepare for war to achieve peace, you get war (2024)

https://blogs.lse.ac.uk/medialse/2024/12/19/war-panic-if-you-prepare-for-war-to-achieve-peace-you...
2•robtherobber•36m ago•0 comments

Pbgopy v0.4.0: Simple cross-device clipboard with history

https://github.com/nakabonne/pbgopy
1•nakabonne•37m ago•0 comments

Wipeout Clone Runs Native on ESP32-S3

https://hackaday.com/2026/04/29/wipeout-clone-runs-native-on-esp32-s3/
2•sohkamyung•37m ago•0 comments

Lectronz

https://lectronz.com/
1•irdc•38m ago•1 comments

Curious: How do you manage contract signature? Any winning process?

https://www.getprobo.com/blog/2026-04-24-how-we-automated-our-client-contract-process
1•arthurmyx•39m ago•1 comments

TimeCapsuleSMB: Hacking the Apple Time Capsule to Run Modern Samba

https://github.com/jamesyc/TimeCapsuleSMB
1•lproven•42m ago•0 comments

More Americans See Driverless Car Future; Few Show Interest

https://news.gallup.com/poll/708683/americans-driverless-car-future-few-show-interest.aspx
2•giuliomagnifico•42m 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•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.