frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

How Elon Musk Left OpenAI, According to Greg Brockman

https://techcrunch.com/2026/05/06/how-elon-musk-left-openai-according-to-greg-brockman/
2•evo_9•3m ago•1 comments

Umka: A statically typed embeddable scripting language

https://github.com/vtereshkov/umka-lang
2•modinfo•5m ago•0 comments

Riju: Fast online playground for every programming language

https://riju.codes/
2•gurjeet•10m ago•0 comments

How AI Works Under the Hood – LLMs Explained with Code

https://nitayneeman.com/blog/how-ai-works-under-the-hood-llms-explained-with-code/
1•thunderbong•11m ago•0 comments

Arithmeum Museum

https://www.arithmeum.uni-bonn.de/en/arithmeum.html
1•soupspaces•11m ago•0 comments

Show HN: I Replaced React in GraphiQL with Svelte

https://code.webb.page/eol/graphiql.git/about/
4•NetOpWibby•15m ago•0 comments

0xBitNet

https://github.com/m96-chan/0xBitNet
2•oldfuture•16m ago•0 comments

Muscles by Electricity: The Latest Fitness Craze?

https://www.wsj.com/lifestyle/fitness/electrical-muscle-stimulation-ems-workout-03dce7e3
2•lxm•17m ago•0 comments

Character.ai Faces Unlawful Practice of Medicine Claim in Pennsylvania Suit

https://www.law.com/therecorder/2026/05/06/characterai-maker-faces-unlawful-practice-of-medicine-...
3•1vuio0pswjnm7•23m ago•2 comments

Compaction in `Sid`: A Novel Algorithm?

https://rescrv.net/w/2026/05/06/compaction-in-sid
2•rescrv•26m ago•1 comments

Spec CPU 2026

https://www.spec.org/cpu2026/
2•sanxiyn•31m ago•0 comments

School Cellphone Ban Study Finds Mixed Results

https://www.nytimes.com/2026/05/04/us/did-school-cellphone-bans-study.html
3•lxm•36m ago•0 comments

We had people come just to see it: Amazon delivers its first UK parcels by drone

https://www.bbc.co.uk/news/articles/cx21k21vnmgo
2•nmstoker•38m ago•0 comments

Three-Em Dash

https://www.compart.com/en/unicode/U+2E3B
4•gregsadetsky•40m ago•0 comments

Nvidia Enterprise Reference Architectures for AI Data Centers

https://www.nvidia.com/en-us/technologies/enterprise-reference-architecture/
2•nalinidash•43m ago•1 comments

SpaceX is starting to move on from the most successful rocket

https://arstechnica.com/space/2026/05/spacex-is-starting-to-move-on-from-the-worlds-most-successf...
2•LorenDB•43m ago•0 comments

Permacomputing Principles

https://permacomputing.net/principles/
6•andsoitis•49m ago•0 comments

Hantavirus explained: Symptoms, transmission and treatment

https://epi.ufl.edu/2026/05/06/hantavirus-explained-symptoms-transmission-and-treatment/
3•rolph•50m ago•0 comments

Quilt Poems

https://leetusman.com/projects/quilt-poems/
4•andsoitis•51m ago•0 comments

Orthohantavirus

https://viralzone.expasy.org/213.html?outline=all_by_species
3•rolph•53m ago•0 comments

Encountering Artificial Intelligence: Ethical and Anthropological Investigations

https://jmt.scholasticahq.com/article/91230-encountering-artificial-intelligence-ethical-and-anth...
5•andsoitis•55m ago•0 comments

An SDK to accept payments from Agents

https://github.com/GTG-Labs/sangria
3•simantakDabhade•56m ago•0 comments

If AI cuts jobs, it would also threaten Social Security and Medicare

https://minnesotareformer.com/2026/04/17/if-ai-cuts-jobs-it-would-also-threaten-social-security-a...
8•littlexsparkee•58m ago•2 comments

Marco Rubio discovers he needs to take over Spirit Airlines

https://www.youtube.com/watch?v=whF9C5j7X8k
4•keepamovin•1h ago•0 comments

Show HN: Dreamwork – a job search site I made after Indeed fired my pregnant wif

https://www.dreamworkhq.com/
4•cojj25•1h ago•2 comments

Ridiculous Things I Utterly Love About Vampire Crawlers

https://kotaku.com/vampire-crawlers-survivors-garlic-poe-decks-chests-sponge-2000689719
4•PaulHoule•1h ago•0 comments

SpaceX IPO gives Musk unchecked power and forbids investor lawsuits

https://arstechnica.com/tech-policy/2026/05/report-spacex-ipo-gives-musk-unchecked-power-and-forb...
10•pzxc•1h ago•1 comments

Geography Is Four-Dimensional

https://sive.rs/4d
5•inatreecrown2•1h ago•1 comments

Nobody understands the point of hybrid cars

https://www.youtube.com/watch?v=KnUFH5GX_fI
4•incomplete•1h ago•0 comments

Cognitive Surrender

https://twitter.com/addyosmani/status/2052124873208799378
4•ayoisaiah•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•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.