frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Sherry Turkle on "Artificial Intimacy: Who We Become When We Talk to Machines"

https://news.harvard.edu/gazette/story/2026/10/my-chatbot-is-my-boyfriend-whats-the-harm/
1•7402•3m ago•0 comments

Are these the worlds best shithouses?

https://www.visitnorway.com/plan-your-trip/travel-tips-a-z/norwegian-scenic-routes/worlds-best-to...
1•28304283409234•6m ago•0 comments

Show HN: Proxenos – a local-first agent for getting through the health system

https://github.com/mindemory/proxenos
1•mindemory•7m ago•0 comments

Two Talk

https://www.twotalk.org
1•Qaphqa•17m ago•1 comments

Map Shows Nations Urging People to Stockpile Food as France Issues Warning

https://www.newsweek.com/map-shows-countries-urging-residents-to-stockpile-food-12629524
1•measurablefunc•20m ago•0 comments

SenseNova-6.8-Code2Video

https://huggingface.co/sensenova/SenseNova-6.8-Code2Video
1•everygen_studio•26m ago•0 comments

Tiny Computers

https://indieappcatalog.com/app/4940
1•andsoitis•26m ago•1 comments

Leaking Secrets from Air-Gap Computers by Spelling Radio Signals from RAM

https://arxiv.org/abs/2409.02292
1•hapax_legomena•27m ago•0 comments

Show HN: LinkedIn-ops – Zero-dependency CDP automation built for AI agents

https://github.com/shashtag-ventures/linkedin-ops
1•shashtag•27m ago•0 comments

Show HN: TariffPedia – HS code lookup and import duty comparison

https://tariffpedia.com/
1•chuanbuilds•27m ago•0 comments

Show HN: Make Python Great Again – Free tools and desktop apps built with Python

https://pythongreatagain.com/
1•elharakimm•28m ago•0 comments

Summer of Math Exposition Archive

https://some.3b1b.co/archive
1•agnishom•29m ago•0 comments

Medo: A modern UHD 4K open source Media editor for Haiku OS in less than 1.44MB

https://github.com/smallstepforman/Medo
1•embedding-shape•35m ago•0 comments

What a mother's 1834 letter about measles tells us about MAHA

https://www.statnews.com/2026/10/30/maha-measles-letter-1834-pseudoscience-women/
3•EA-3167•36m ago•1 comments

Elsag SignalTrace maps cars using phone, car radio, headphone, watch, key finder

https://www.leonardocompany-us.com/lpr/elsag-signaltrace
1•rexbee•37m ago•0 comments

The Soft Machine (1961)

https://www.semiovox.com/articles/2026/03/05/the-soft-machine/
1•windows1000•38m ago•0 comments

WiCi: Connecting GPUs over WiFi

https://wici.ai
1•shubham0204•44m ago•1 comments

Design systems for agents

https://design.how
1•handfuloflight•46m ago•1 comments

Show HN: Analog Video Feedback Fractals

https://www.youtube.com/watch?v=znkzM9-FVzw
3•i2pi•48m ago•0 comments

Formalities

https://pluralistic.net/2026/10/31/burn-berne/
2•dgudkov•50m ago•1 comments

Eulogy for the Software Engineer [video]

https://www.youtube.com/watch?v=uuKOXGVIP8I
2•mhsdef•52m ago•0 comments

Ask HN: Old experimental website that made photos sing?

1•jesuisdieu•56m ago•0 comments

RequestRocket Promo Key

https://requestrocket.com
1•geoicons•1h ago•1 comments

Doop

https://doop.design/
1•handfuloflight•1h ago•0 comments

What Happened to the TI-83? Sold to Every Student in 1996 Then Destroyed Itself

https://www.youtube.com/watch?v=X9YqHX0Twg4
2•cable2600•1h ago•1 comments

RustDrop – privacy-first P2P file transfer for your LAN (Rust)

https://github.com/hakuxyz/rustdrop
2•xyzhaku•1h ago•0 comments

How AI may drive union-resistant tech workers to the bargaining table

https://www.theguardian.com/technology/2026/jul/21/ai-tech-workers-unionize
6•civilchaos•1h ago•0 comments

Avoid Public Functions Calling Other Public Functions

https://matklad.github.io/2026/10/29/pub-calls-pub.html
3•birdculture•1h ago•0 comments

Wikimedia Foundation amicus brief regarding OpenAI [pdf]

https://commons.wikimedia.org/w/index.php?title=File%3A26.10.29_WMF_motion_and_amicus_In_re_OAI.p...
2•gnabgib•1h ago•0 comments

Amazon made the AUX input on older Alexa devices less useful

https://www.engadget.com/2300219/amazon-made-alexa-devices-aux-port-less-useful/
5•NordStreamYacht•1h ago•2 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.