frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Everyone's Watching Stocks. The Real Bubble Is AI Debt

https://www.bloomberg.com/news/newsletters/2025-12-31/everyone-s-watching-stocks-the-real-bubble-...
1•zerosizedweasle•55s ago•0 comments

Norman Foster's steroidal new skyscraper is an affront to the New York skyline

https://www.theguardian.com/artanddesign/2025/dec/03/eco-obscenity-norman-foster-skyscraper-jp-mo...
2•PaulHoule•1m ago•0 comments

Why users cannot create Issues directly (Ghostty)

https://github.com/ghostty-org/ghostty/issues/3558
1•xpe•2m ago•0 comments

Why CoreWeave Is Weighed Down by Its Debt Load

https://finance.yahoo.com/news/heres-why-coreweave-nasdaq-crwv-140015154.html
1•zerosizedweasle•3m ago•0 comments

DeepSeek MHC: Manifold-Constrained Hyper-Connections

https://huggingface.co/papers/2512.24880
1•marc__1•3m ago•0 comments

Bud-Sex: Sexual Flexibility Among Rural White Straight Men Who Have Sex with Men

https://scholarsbank.uoregon.edu/server/api/core/bitstreams/d38a6707-f38a-4b2f-b598-c4bf171b6c7c/...
1•lesk•4m ago•0 comments

From Silicon to Darude Sand-storm: breaking famous synthesizer DSPs [video]

https://media.ccc.de/v/39c3-from-silicon-to-darude-sand-storm-breaking-famous-synthesizer-dsps
1•tzmlab•8m ago•0 comments

Type-Safe User Interfaces and the Manifest Pattern

https://andrewhathaway.net/blog/manifest-pattern/
1•handfuloflight•8m ago•0 comments

California Delete Request and Opt-out Platform (DROP)

https://privacy.ca.gov/DROP/
1•8organicbits•20m ago•0 comments

Show HN: BreachLab – Can you hack our AI?

https://breachlab.xsourcesec.com
2•xsourcesec•20m ago•0 comments

California dessert empire Sprinkles Cupcakes abruptly closes all stores

https://www.sfgate.com/food/article/california-sprinkles-cupcakes-closes-21270149.php
3•apparent•22m ago•1 comments

Journalism, media, and technology trends and predictions 2025

https://reutersinstitute.politics.ox.ac.uk/journalism-media-and-technology-trends-and-predictions...
1•barishnamazov•22m ago•0 comments

LakeFS Acquires DVC

https://lakefs.io/blog/celebration-shared-vision-lakefs-dvc/
2•farhanhubble•26m ago•0 comments

In-house electronics manufacturing from scratch: How hard can it be? [video]

https://media.ccc.de/v/39c3-in-house-electronics-manufacturing-from-scratch-how-hard-can-it-be
1•Fnoord•27m ago•0 comments

File manager for the COSMIC desktop environment

https://github.com/pop-os/cosmic-files
1•doener•31m ago•0 comments

New California Laws Going into Effect in 2026

https://newsroom.courts.ca.gov/news/new-california-laws-going-effect-2026
2•ChadNauseam•32m ago•0 comments

You Are Not an Average

https://thinkhuman.com/you-are-not-an-average/
2•jamesgill•34m ago•0 comments

Lean: Open source algorithmic trading engine

https://github.com/QuantConnect/Lean
2•nateb2022•36m ago•0 comments

Fastest Electric Drone World Record Broken with $3000 Drone (655 KM/H) [video]

https://www.youtube.com/watch?v=Zag6qsalZgw
3•nomilk•38m ago•0 comments

U.S. Patent Law and Perpetual Motion Machines (2011)

https://ipwatchdog.com/2011/10/11/the-patent-law-of-perpetual-motion/
2•ilamont•39m ago•0 comments

Trump Mobile delays plan to launch gold-coloured smartphone this year

https://www.ft.com/content/29fc1e75-7bec-4011-acc3-603e51cf9fe2
3•doener•40m ago•0 comments

Show HN: FountainData – product, revenue, and GTM Intel from user conversations

https://fountaindata.com
2•j_mao•40m ago•0 comments

XWayland is the bridging mechanism between legacy Xorg programs and Wayland

https://wiki.hypr.land/Configuring/XWayland/
3•doener•42m ago•0 comments

The Rise of Homonationalism

https://www.spiked-online.com/2025/12/30/the-rise-of-homonationalism/
4•buggery•43m ago•0 comments

Donald Knuth "32 Years of Metafont" at the San Francisco Public Library [video]

https://www.youtube.com/watch?v=0LR_lBEy7qU
2•gjvc•44m ago•1 comments

Hidden Fortunes (2024)

https://www.imf.org/en/publications/fandd/issues/2024/12/hidden-fortunes-chady-el-khoury
1•hhs•48m ago•0 comments

Show HN: Stealth and Browsers and Solvers in Rust

https://github.com/ccheshirecat/chaser-oxide
1•ccheshirecat•53m ago•0 comments

The year of unaffordability

https://lawliberty.org/the-year-of-unaffordibility/
2•hhs•58m ago•0 comments

Show HN: AI Motion Poster – 1-click static image to animated poster

https://aimotionposter.app/
2•linkshu•1h ago•0 comments

It's Not Your Codebase

https://www.seangoedecke.com/not-your-codebase/
3•alpb•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•7mo 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•7mo 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•7mo 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•7mo 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.