frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Mock – An API creation and testing utility: Examples

https://dhuan.github.io/mock/latest/examples.html
11•dhuan_•29m ago•0 comments

Backpropagation is a leaky abstraction (2016)

https://karpathy.medium.com/yes-you-should-understand-backprop-e2f06eab496b
161•swatson741•6h ago•67 comments

We reduced a container image from 800GB to 2GB

https://sealos.io/blog/reduce-container-image-size-case-study
30•untrimmed•6d ago•16 comments

Notes by djb on using Fil-C (2025)

https://cr.yp.to/2025/fil-c.html
112•transpute•6h ago•30 comments

Visopsys: OS maintained by a single developer since 1997

https://visopsys.org/
368•kome•13h ago•73 comments

When O3 is 2x slower than O2

https://cat-solstice.github.io/test-pqueue/
26•keyle•4d ago•12 comments

How I use every Claude Code feature

https://blog.sshh.io/p/how-i-use-every-claude-code-feature
287•sshh12•11h ago•92 comments

Claude Code can debug low-level cryptography

https://words.filippo.io/claude-debugging/
340•Bogdanp•17h ago•164 comments

Updated practice for review articles and position papers in ArXiv CS category

https://blog.arxiv.org/2025/10/31/attention-authors-updated-practice-for-review-articles-and-posi...
456•dw64•21h ago•209 comments

Pomelli

https://blog.google/technology/google-labs/pomelli/
193•birriel•12h ago•69 comments

Crossfire: High-performance lockless spsc/mpsc/mpmc channels for Rust

https://github.com/frostyplanet/crossfire-rs
71•0x1997•8h ago•7 comments

LM8560, the eternal chip from the 1980 years

https://www.tycospages.com/other-themes/lm8560-the-eternal-chip-from-the-1980-years/
57•userbinator•7h ago•19 comments

FlightAware Map Design

https://andywoodruff.com/posts/2024/flightaware-maps/
33•marklit•6d ago•11 comments

GHC now runs in the browser

https://discourse.haskell.org/t/ghc-now-runs-in-your-browser/13169
317•kaycebasques•19h ago•105 comments

Welcome to hell; please drive carefully

https://2earth.github.io/website/20251026.html
6•2earth•5d ago•1 comments

Context engineering

https://chrisloy.dev/post/2025/08/03/context-engineering
10•chrisloy•3h ago•0 comments

Show HN: Why write code if the LLM can just do the thing? (web app experiment)

https://github.com/samrolken/nokode
340•samrolken•18h ago•241 comments

Automatically Translating C to Rust

https://cacm.acm.org/research/automatically-translating-c-to-rust/
67•FromTheArchives•1w ago•19 comments

SQLite concurrency and why you should care about it

https://jellyfin.org/posts/SQLite-locking/
315•HunOL•23h ago•141 comments

Anonymous credentials: rate-limit bots and agents without compromising privacy

https://blog.cloudflare.com/private-rate-limiting/
70•eleye•11h ago•34 comments

Beginner-friendly, unofficial documentation for Helix text editor

https://helix-editor.vercel.app/start-here/basics/
139•Curiositry•16h ago•46 comments

3M Diskette Reference Manual (1983) [pdf]

https://retrocmp.de/fdd/diskette/3M_Diskette_Reference_Manual_May83.pdf
84•susam•5d ago•18 comments

Hyperbolic Non-Euclidean World (2007)

http://web1.kcn.jp/hp28ah77/
18•ubavic•6d ago•3 comments

The Smol Training Playbook: The Secrets to Building World-Class LLMs

https://huggingface.co/spaces/HuggingFaceTB/smol-training-playbook
207•kashifr•2d ago•12 comments

From 400 Mbps to 1.7 Gbps: A WiFi 7 Debugging Journey

https://blog.tymscar.com/posts/wifi7speedhunt/
114•tymscar•16h ago•84 comments

CLI to manage your SQL database schemas and migrations

https://github.com/gh-PonyM/shed
25•PonyM•5h ago•13 comments

Chip Hall of Fame: Intel 8088 Microprocessor

https://spectrum.ieee.org/chip-hall-of-fame-intel-8088-microprocessor
28•stmw•6d ago•1 comments

A Few Words About Async

https://yoric.github.io/post/quite-a-few-words-about-async/
56•vinhnx•10h ago•18 comments

How to Build a Solar Powered Electric Oven

https://solar.lowtechmagazine.com/2025/10/how-to-build-a-solar-powered-electric-oven/
60•surprisetalk•1w ago•29 comments

SailfishOS: A Linux-based European alternative to dominant mobile OSes

https://sailfishos.org/info/
294•ForHackernews•13h ago•123 comments
Open in hackernews

NJVL: Nim's New Intermediate Representation

https://github.com/nim-lang/nimony/blob/master/doc/njvl-spec.md
66•generichuman•3d ago

Comments

ebb_earl_co•15h ago
I am really only familiar with Python, in which I’m pretty sure that the .py becomes .pyc and then CPython translates .pyc into machine instructions.

How does this differ? Is an IR the same idea as Python’s .pyc?

BoingBoomTschak•14h ago
> and then CPython translates .pyc into machine instructions.

What do you mean? CPython is a bytecode compiler and a virtual machine interpreting that bytecode. Or are you talking about the new experimental JIT?

almostgotcaught•12h ago
strictly speaking bytecode isn't IR because typically it's not further transformed - IRs are designed to be further transformed. as with all things these aren't hard and fast rules (plenty of compilers run transformations on bytecode, and there are plenty of interpreters for some IRs).
digdugdirk•13h ago
Nim seems to be almost a pet project of a single individual. Is that just my interpretation or is it an actual representation of reality?

If it is correct, and mostly created by one person - how? Are they a genius? Is creating your own programming language from scratch something anyone can accomplish if they just go for it?

Or is it just something that shouldn't be trusted/used for commercial purposes because it's not as "legit" as a newer language like rust for example?

It's just a weird vibe - it seems like it should be so much more popular than it is.

plainOldText•13h ago
The main designer is Andreas Rumpf, but investigating the git commits of the new Nim reveals more people being involved. [1] Whether Andreas is a genius, I have no idea, but he has been doing compiler and language development for over 20 years [2] so he's probably extremely knowledgeable regardless.

[1] https://github.com/nim-lang/nimony/commits/master/

[2] https://en.wikipedia.org/wiki/Nim_(programming_language)

elcritch•13h ago
The BDFL Araq is the primary creator but there's a small team of paid core developers. There's also a number of open source contributors. So it's a commercial project as well. They offer support contracts too.

> If it is correct, and mostly created by one person - how? Are they a genius? Is creating your own programming language from scratch something anyone can accomplish if they just go for it?

Creating a compiler can be one by a single person. Maintaining it is harder, especially for commercial support contracts. That's where teams are needed, and Nim has that.

However a lot of the issues many languages is overcomplicated design. Nim is ardantly a pragmatic language. NJVL is an example of that.

> Or is it just something that shouldn't be trusted/used for commercial purposes because it's not as "legit" as a newer language like rust for example?

I say it can be trusted. It's survived ~20 years. Statistically it'll likely survive another 20.

I'd say it's not too different from Zig or Elixir on the compiler and language side. There's a number companies and open source projects using it.

Sure Rust is going to be bigger but also Rust is far more complicated as a language. Similarly for packages I found there's 10 crates of varying quality and incompatible. With Nim I can take something like Pixie for images and make an image finding library in a day that outperforms opencv without struggling with crates or dev compiler features.

Nim's used at Reddit, Status IM, and more. Especially with LLMS it's pretty easy to switch languages, to make support libraries, get devs productive, etc so there's much less risk these days IMO.

> It's just a weird vibe - it seems like it should be so much more popular than it is.

It should be more popular!

A few things hold back broader adoption IMHO. A big one is that it's a "European" language as Araq and team is European which sort of distances it from the SV and HN zeitgeist. There's a lot to "hype" factor. Nim has a more of a slow and steady adoption like early Python, IMHO.

Secondly it's just found it's niche by focusing on being a systems language with reference counted memory system with excellent metaprogramming. In the past things community issues arose, or lots of people disliked case insensitivity. Those issues have mostly settled though with case insensitivity being phased out.

LSP needs improvement. Nimony is designed to solve that.

elcritch•13h ago
It's an interesting take on an IR. It's goal is to support the current C/C++/JS backend but also to make generating native assembly easy to do as well.

It also doesn't rely on lexical scopes to do analysis for things like lifetimes, nil tracking, destructors, etc. Instead it uses the versioned variables AFICT to enable those features more directly. Should be much simpler for the compiler implementation for 99% of cases versus traditional SSA blocks.

Unfortunately I'm busy writing Nim code and not able to play with the new Nimony compiler framework. I'm excited about incremental compilation and borrow checking features though.

fuhsnn•13h ago
The tree-like syntax interested me but unless this new layer enforces it, there's no guaranteed evaluation order among its backends[1], which IMO kind of defeat it's usability as general purpose IR.

[1] https://github.com/nim-lang/nimony/issues/792