frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Ireland Is Becoming a French Military Protectorate

https://foreignpolicy.com/2026/06/18/ireland-france-military-protectorate-outsourcing-defense-pro...
1•ilamont•19s ago•0 comments

Show HN: LoomStack – Helping engineering orgs scale AI-driven development

https://loomstack.co/
1•vermaabhishek39•5m ago•0 comments

No AI data centres in my backyard, please

https://hey.paris/posts/ai-data-centres-tasmania/
2•parisidau•11m ago•0 comments

Iran war triggers global race to build oil reserves

https://www.reuters.com/commentary/reuters-open-interest/iran-war-triggers-global-race-build-oil-...
1•kaycebasques•11m ago•0 comments

The systemic decay of tech hiring

https://thoughtspile.github.io/2026/06/22/systemic-decay-of-hiring/
1•theanonymousone•12m ago•0 comments

What If the Work We're Busy Automating Is Needless?

https://www.oftwominds.com/blogjune26/needless-work6-26.html
1•spking•14m ago•0 comments

UK considers forcing social media firms to prioritise trusted news

https://www.reuters.com/legal/litigation/uk-considers-forcing-social-media-firms-prioritise-trust...
1•frm88•14m ago•0 comments

Gaussian splats on visionOS Beta

https://developer.apple.com/documentation/visionos/gaussian-splats-on-visionos
1•LoganDark•15m ago•0 comments

That I'm Using .NET

https://medium.com/c-sharp-programming/7-ways-that-im-using-net-93c669143cc8
1•sukhpinder0804•18m ago•0 comments

Seedance 2.5, generating a complete 30-second video in one go

https://twitter.com/xiaohu/status/2069236441964818508
3•vantareed•19m ago•1 comments

Vim Adventures – learning Vim by playing a game

https://www.youtube.com/watch?v=GVjtUK5JEw0
1•coolwulf•20m ago•1 comments

GLM-5.2 is the step change for open agents

https://www.interconnects.ai/p/glm-52-is-the-step-change-for-open
4•vantareed•26m ago•0 comments

Spartan Programming

https://spartan.wiki
1•skogstokig•30m ago•0 comments

Open-source security auditors for Supabase, Strapi, Hasura and Ollama

https://github.com/Perufitlife/awesome-backend-security
2•renzomad•35m ago•0 comments

Nonstop Trading, Lots of Leverage. How 'Perp Futures' Are Changing Wall Street

https://www.wsj.com/finance/commodities-futures/nonstop-trading-loads-of-leverage-how-perp-future...
4•JumpCrisscross•39m ago•0 comments

Reddit account history viewer, even for deleted posts

https://deletedby.com
2•Mobile-Spread•42m ago•2 comments

The System Moved On, but It Didn't Forget

https://webmnem.here.now/system-moved-on-but-it-didnt-forget/
1•InfraStack•45m ago•0 comments

The AI Tarpit: Why You Can't Stop Reading Your Code

https://www.williamangel.net/blog/2026/06/22/The-AI-Tarpit-Why-You-Cant-Stop-Reading-Your-Code.html
1•datadrivenangel•47m ago•0 comments

I Bought the Trump Phone [video]

https://www.youtube.com/watch?v=b1ytw85Npt8
3•billfor•48m ago•0 comments

Show HN: A 3D world you grow from your phone's camera flash

https://phronesis.world/similar
3•degibug•52m ago•0 comments

King's study finds AI chose nuclear signalling in 95% of simulated crises

https://www.kcl.ac.uk/news/artificial-intelligence-under-nuclear-pressure-first-large-scale-kings...
1•totetsu•52m ago•1 comments

Man used massage gun on his tired eyeballs. It went as well as you'd expect

https://arstechnica.com/health/2026/06/man-used-massage-gun-on-his-tired-eyeballs-it-went-as-well...
6•canucker2016•55m ago•5 comments

Ask HN: Has Codex gotten slower recently?

4•aurenvale•56m ago•0 comments

Show HN: ExtensionBooster – Get real human reviews for your apps

https://extensionbooster.net/
3•quangpl•56m ago•1 comments

How I made the firewood splitting simulator

https://old.reddit.com/r/vibecoding/comments/1uckug1/heres_how_i_made_the_firewood_splitting_simu...
4•thunderbong•58m ago•0 comments

Show HN: Loft gives thumb-keys and split-layout on a standard laptop or keyboard

https://loftkeyboard.com
4•RuleOfBirds•1h ago•0 comments

Prompt Preflight – catch vague AI-agent prompts before they burn tokens

https://github.com/akg268/prompt-preflight/
2•akg268•1h ago•0 comments

Chain-of-Trust with AI

https://marirs.net.in/cot/
2•sriramster•1h ago•1 comments

Show HN: I scanned every YC Spring 2026 startup for what AI crawlers see

https://potatometer.com/blog/yc-spring-2026-ai-reach-vs-readability
2•apswin•1h ago•0 comments

AWS Lambda MicroVMs for isolated execution of user and AI-generated code

https://aws.amazon.com/about-aws/whats-new/2026/06/aws-lambda-microvms/
16•leemoore•1h ago•3 comments
Open in hackernews

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

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