frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Phlogiston Forty Four: An Interview with Roger Zelazny

https://web.archive.org/web/20080216071439/http://zelazny.corrupt.net/phlog44rzint.txt
1•debo_•8m ago•0 comments

Trump, Lost in the Failure of His War, Blinks

https://www.forever-wars.com/trump-lost-in-the-failure-of-his-war-blinks/
1•KnuthIsGod•9m ago•0 comments

Anthropic: A Technical and Business Model Analysis

https://blog.sd.idv.tw/en/posts/2026-03-25_anthropic-business-analysis/
2•steve_luo•11m ago•1 comments

Show HN: Looking for feedback on a Git-native message board

https://zenmemes.com/compose/thread
1•forgotmypw17•17m ago•2 comments

AMD-optimized Rocky Linux distribution to focus on AI and HPC workloads

https://www.phoronix.com/news/AMD-Rocky-Linux-Optimized
1•teleforce•18m ago•0 comments

Freddy – AI educator that lives in your Slack and teaches your team about AI

https://braingem.ai
1•sstart•22m ago•0 comments

Welcome to IBM Bob: Your AI-Powered Development Partner

https://bob.ibm.com
1•noiv•22m ago•0 comments

The U.S. attacked Iran to show its power but the war is already lost

https://fortune.com/2026/03/18/us-iran-war-lost-strategic-miscalculation-trump/
2•KnuthIsGod•25m ago•0 comments

I Spoke to the Dev Behind the Systemd Birth Date Change [video]

https://www.youtube.com/watch?v=8bAN4Jam974
2•stop50•32m ago•0 comments

Is lighter sleep a normal part of ageing – or a sign of something more serious?

https://theconversation.com/is-lighter-sleep-a-normal-part-of-ageing-or-a-sign-of-something-more-...
2•lentoutcry•34m ago•0 comments

Some Meta employees were told to work remotely for the day as layoffs loom

https://www.businessinsider.com/meta-employees-work-remotely-email-layoffs-hr-wfh-2026-3
1•kpw94•36m ago•0 comments

Flowing with Agents with Beyang Liu, CTO of Sourcegraph

https://changelog.com/podcast/658
1•fagnerbrack•39m ago•0 comments

I prepare for high-stakes technical AI demos

https://katecatlin.substack.com/p/how-i-prepare-for-high-stakes-technical
1•mooreds•39m ago•0 comments

Software Engineers Make Productive Decisions (without slowing the team down)

https://strategizeyourcareer.com/p/how-software-engineers-make-productive-decisions
1•fagnerbrack•40m ago•0 comments

The Trials of Satya Nadella

https://www.newcomer.co/p/the-trials-of-satya-nadella
1•imartin2k•40m ago•0 comments

How Reading books regulates your nervous system

https://bigthink.com/mind-behavior/how-reading-books-regulates-your-nervous-system/
3•the-mitr•42m ago•0 comments

Brewdog founder admits 'many mistakes' as hundreds lose jobs in sale

https://www.bbc.com/news/articles/cze00ddyw27o
1•mooreds•44m ago•1 comments

Typing Speed Might Matter Now

https://jarbus.net/blog/typing-speed-might-matter-now/
1•jarbus•49m ago•3 comments

ToolTrust Scanner – detect backdoored MCP packages (litellm 1.82.8)

https://github.com/AgentSafe-AI/tooltrust-scanner
1•brian93512•51m ago•0 comments

AI automation is quietly de-skilling white-collar workers

https://www.inc.com/andrea-olson/how-ai-automation-is-quietly-deskilling-white-collar-workers/913...
2•ryan_j_naughton•55m ago•0 comments

Show HN: Pixelbeat – A pixel-art terminal music player daemon written in Rust

https://github.com/Dylanwooo/pixelbeat
2•Dylanwoo•56m ago•0 comments

Implementing automatic eSIM installation on Android

https://medium.com/proandroiddev/integration-of-automatic-esim-installation-on-android-6c5f6d7124cb
13•nesterenkopavel•59m ago•0 comments

MirageOS – Build Unikernels in OCaml

https://mirage.io/
3•h4ch1•1h ago•1 comments

iStat Menus < 7.20.5 local privilege escalation

https://markuta.com/istat-menus-local-privilege-escalation/
1•jandeboevrie•1h ago•0 comments

D B Smith says "Einstein dead" and releases full stack of revolutionary papers

https://zenodo.org/records/19212785
2•tintweezl•1h ago•1 comments

Saving money by switching from PHP to D (2019)

https://dlang.org/blog/2019/09/30/saving-money-by-switching-from-php-to-d/
1•teleforce•1h ago•0 comments

Self-Parking Car Evolution

https://trekhleb.dev/self-parking-car-evolution/
2•trekhleb•1h ago•1 comments

Remove curl and wget aliases from PowerShell

https://github.com/PowerShell/PowerShell/pull/1901
1•tuananh•1h ago•0 comments

Pseudo-3D Photo Maker – iOS App

https://apps.apple.com/us/app/ioutbox-pseudo-3d-photo-maker/id6760662310
1•dares2573•1h ago•0 comments

Show HN: Travelwithsira: Find Cheapest Flights

https://travelwithsira.com/
1•malwaregeeeek•1h ago•0 comments
Open in hackernews

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

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