frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ensemble Listening Model

https://www.ensemblelisteningmodel.com/
1•durron•48s ago•0 comments

A daily practice for writing better taglines

https://www.instagram.com/accounts/login/?next=https%3A%2F%2Fwww.instagram.com%2Ftaglinesandcopy&...
1•leeclowtaughtme•2m ago•1 comments

Show HN: A Lightweight Event Sourcing Starter for Next.js and GenesisDB

https://github.com/genesisdb-io/genesisdb-io-nextjs-es-starter
3•patriceckhart•3m ago•0 comments

Build Broad, Refine Later

https://opuslabs.substack.com/p/build-broad-refine-later
1•opuslabs•4m ago•0 comments

Training Your Own LLM on a MacBook Pro

https://opuslabs.substack.com/p/training-your-own-llm-on-a-macbook
2•opuslabs•4m ago•0 comments

Llms.txt didn't boost AI traffic for 10 sites; growth was coincidental

https://searchengineland.com/does-llms-txt-matter-467740
2•speckx•5m ago•0 comments

Show HN: Afelyon – AI agent that turns Jira tickets into GitHub PRs

https://afelyon.com/
1•AbduNebu•7m ago•0 comments

Turbopack: Building Faster by Building Less

https://nextjs.org/blog/turbopack-incremental-computation
2•feross•8m ago•0 comments

Show HN: OpsCompanion – Live production context for teams and agents

https://opscompanion.ai/
1•kennethops•8m ago•0 comments

EU-Inc: An API-first corporate structure as alternative to Delaware C-Corps

https://www.eu-inc.org/
1•matesz•9m ago•1 comments

The fix for a segfault that never shipped

https://www.recall.ai/blog/the-fix-for-a-segfault-that-never-shipped
3•davidgu•9m ago•0 comments

Check this futuristic Architecture for ecommerce: composable commerce

https://bagisto.com/en/composable-commerce/
1•anikeshkumar•11m ago•0 comments

Krazam: Rare Data Hunters [video]

https://www.youtube.com/watch?v=IU4ByUbDKNc
3•Topfi•13m ago•0 comments

Cow Tools

https://en.wikipedia.org/wiki/Cow_tools
2•pleurotus•13m ago•0 comments

Show HN: Quadrastack – All-in-one CLI for mocking and testing APIs

https://quadrastack.com
2•yuegui•14m ago•0 comments

Show HN: Kiplomatie – A framework for ethical AI governance

1•Kiplomat-SouCmp•15m ago•0 comments

Show HN: AIChatLens – Save AI chats and snippets locally in the browser

https://chromewebstore.google.com/detail/aichatlens-ai-memory-and/edefkcahpidomhojmdacbdagmccggclb
1•chaimaaM•16m ago•0 comments

Immigration Agencies Are Openly Defying Federal Courts

https://lpeproject.org/blog/immigration-agencies-are-openly-defying-federal-courts/
2•abrownbear•16m ago•0 comments

When "Likers'' Go Private: Engagement with Reputationally Risky Content on X

https://arxiv.org/abs/2601.11140
4•linolevan•17m ago•0 comments

Queuert – Node.js background jobs that live in your database transaction

https://github.com/kvet/queuert
1•dr_kvet•18m ago•1 comments

Naked Power: Apple and Google's Duopoly

https://infrequently.org/2026/01/naked-power/
2•cdrnsf•18m ago•0 comments

RAM shortage chaos expands to GPUs, high-capacity SSDs, and even hard drives

https://arstechnica.com/gadgets/2026/01/ram-shortage-chaos-expands-to-gpus-high-capacity-ssds-and...
3•akyuu•19m ago•0 comments

Trump shares altered map of U.S. flag covering Canada, Greenland and Venezuela

https://www.ctvnews.ca/canada/article/trump-shares-altered-map-of-us-flag-covering-canada-greenla...
6•Infiniti20•21m ago•0 comments

The Path to Real-Time Worlds and Why It Matters

https://over.world/blog/the-path-to-real-time-worlds-and-why-it-matters
2•Philpax•23m ago•0 comments

Ask HN: Will humans still vote after AI takes over?

3•nothrowaways•23m ago•3 comments

Web-based video editor powered by WebGPU

https://subformer.com/en-US/editor
5•mohebifar•24m ago•3 comments

How Hightouch built their long-running agent harness

https://www.amplifypartners.com/blog-posts/how-hightouch-built-their-long-running-agent-harness
30•thecr0w•25m ago•1 comments

Show HN: CanIUse for WebCodecs – Hardware support from 71M tests

https://webcodecsfundamentals.org/datasets/codec-support-table/
2•sb2702•26m ago•1 comments

Leading through uncertainty in the age of AI

https://www.pwc.com/gx/en/issues/c-suite-insights/ceo-survey.html
2•shscs911•27m ago•0 comments

OpenAI aims to debut first device in 2026

https://www.axios.com/2026/01/19/openai-device-2026-lehane-jony-ive
4•Vasniktel•27m ago•0 comments
Open in hackernews

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

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