frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Tesla to stop selling FSD package, moves to subscription-only: why a big move

https://electrek.co/2026/01/14/tesla-tsla-stop-selling-full-self-driving-package-subscription-only/
1•FabHK•1m ago•0 comments

Viking Solar Navigation Modernized (DIY)

https://www.youtube.com/watch?v=4ERqAqwQ1wo
1•gsf_emergency_6•4m ago•0 comments

Show HN: Calculator to compare Startup offers vs. Big Tech comp

https://shouldijoinastartup.com
1•febtiger•6m ago•0 comments

Supernatural VR will no longer get new content or features

https://www.uploadvr.com/supernatural-coaches-face-same-fate-as-oculus-home-echo-arena/
1•guiambros•7m ago•0 comments

Handy – free open source speech-to-text app

https://github.com/cjpais/Handy
1•tin7in•8m ago•0 comments

Ask HN: How to predict nums of output tokens?

1•ssslvky1•11m ago•1 comments

Mistral Vibe – Minimal CLI Coding Agent

https://github.com/mistralai/mistral-vibe
1•tin7in•14m ago•0 comments

Pocket TTS: A high quality TTS that gives your CPU a voice

https://kyutai.org/blog/2026-01-13-pocket-tts
3•pain_perdu•18m ago•0 comments

Conductor: Context-driven development for Gemini CLI

https://developers.googleblog.com/conductor-introducing-context-driven-development-for-gemini-cli/
1•geoffbp•20m ago•0 comments

Just the Browser

https://justthebrowser.com/
1•vinhnx•21m ago•1 comments

Claude Code Tool Search Tool

https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool
1•tin7in•22m ago•0 comments

Show HN: Headroom – Reversible context compression for LLMs(~60% cost reduction)

https://github.com/chopratejas/headroom
1•chopratejas•25m ago•1 comments

Show HN: Tool that automates ML model deployment on mobile/edge devices

https://twitter.com/AbdoulayeSeydi_/status/2011648286885888216
1•AbdoulayeSeydi•37m ago•0 comments

Tech investors assess minerals mining as U.S. takeover talk on Greenland grows

https://www.cnbc.com/2026/01/12/tech-investors-probe-mining-viability-if-us-acquires-greenland-ce...
5•1vuio0pswjnm7•41m ago•2 comments

Raising Kids After Knowledge Became a Commodity

https://liorz.github.io/blog/posts/fallacy-education-for-academic-excellence/
2•freediver•41m ago•0 comments

Here comes the advertising in AI chatbots

https://www.washingtonpost.com/technology/2026/01/13/advertising-google-ai-mode-chatgpt/
5•1vuio0pswjnm7•42m ago•1 comments

Ask HN: Why Gemini CLI startup is so slow?

1•attentive•49m ago•0 comments

Show HN: Flour Hour – I built a bread baking app with Claude Code in 3 hours

https://yaninatrekhleb.github.io/flour-hour/
2•yanina_trekhleb•50m ago•0 comments

On FLOSS and training LLMs

https://chronicles.mad-scientist.club/tales/on-floss-and-training-llms/
1•pabs3•1h ago•0 comments

Show HN: Open Contribution Graph: A GitHub heatmap for anything you can POST

https://github.com/Tomer-Barak/contribution-graph
2•minimal_action•1h ago•1 comments

Microsoft's spending on Anthropic AI on track to reach $500M

https://www.msn.com/en-us/money/other/microsoft-s-spending-on-anthropic-ai-on-track-to-reach-500m...
2•nl•1h ago•0 comments

Nw_wrld is an event-driven sequencer for triggering visuals [video]

https://www.youtube.com/watch?v=6vM_b54pWtg
1•_josh_meyer_•1h ago•1 comments

Agent Skills That Work

https://agentskills.work/sellers-net-sheet-florida
2•zlonmask•1h ago•1 comments

AI Blog

https://ai-blog-peach.vercel.app
1•dagmawibabi•1h ago•1 comments

Tell HN: AI could bring back GraphQL from the brink

4•sergiotapia•1h ago•0 comments

Tjs: Fastest and most accurate JSON-schema validator

https://github.com/sberan/tjs
2•handfuloflight•1h ago•0 comments

Chinese military says it is developing over 10 quantum warfare weapons

https://www.scmp.com/news/china/science/article/3339907/chinese-military-says-it-developing-over-...
4•KnuthIsGod•1h ago•1 comments

Show HN: Flashlight: Android app that lets you control torch brightness

https://github.com/rtvkiz/Flashlight
2•ritvikarya98•1h ago•0 comments

Appliances, Factories and the Grid

https://mercurialsolo.substack.com/p/appliances-factories-grids
1•mercurialsolo•1h ago•1 comments

Microsoft-Activision deal was meant to help The Embracer Grou

https://www.gamefile.news/p/bobby-kotick-activision-microsoft-ap7-lawsuit-embracer-group
2•firesteelrain•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.