frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

CapROS: The Capability-Based Reliable Operating System

https://www.capros.org/
38•gjvc•2h ago•14 comments

2002: Last.fm and Audioscrobbler Herald the Social Web

https://cybercultural.com/p/lastfm-audioscrobbler-2002/
157•cdrnsf•6h ago•93 comments

Elevated errors across many models

https://status.claude.com/incidents/9g6qpr72ttbr
270•pablo24602•5h ago•132 comments

JSDoc is TypeScript

https://culi.bearblog.dev/jsdoc-is-typescript/
121•culi•7h ago•148 comments

Hashcards: A plain-text spaced repetition system

https://borretti.me/article/hashcards-plain-text-spaced-repetition
256•thomascountz•10h ago•106 comments

Ask HN: What Are You Working On? (December 2025)

156•david927•10h ago•557 comments

In the Beginning was the Command Line (1999)

https://web.stanford.edu/class/cs81n/command.txt
101•wseqyrku•6d ago•44 comments

History of Declarative Programming

https://shenlanguage.org/TBoS/tbos_15.html
34•measurablefunc•4h ago•11 comments

An attempt to articulate Forth's practical strengths and eternal usefulness

https://im-just-lee.ing/forth-why-cb234c03.txt
21•todsacerdoti•1w ago•11 comments

The Typeframe PX-88 Portable Computing System

https://www.typeframe.net/
93•birdculture•9h ago•28 comments

Interview with Kent Overstreet (Bcachefs) [audio]

https://linuxunplugged.com/644
44•teekert•3d ago•29 comments

Shai-Hulud compromised a dev machine and raided GitHub org access: a post-mortem

https://trigger.dev/blog/shai-hulud-postmortem
194•nkko•17h ago•115 comments

Advent of Swift

https://leahneukirchen.org/blog/archive/2025/12/advent-of-swift.html
61•chmaynard•7h ago•19 comments

AI and the ironies of automation – Part 2

https://www.ufried.com/blog/ironies_of_ai_2/
216•BinaryIgor•13h ago•93 comments

DARPA GO: Generative Optogenetics

https://www.darpa.mil/research/programs/go
17•birriel•3h ago•2 comments

Developing a food-safe finish for my wooden spoons

https://alinpanaitiu.com/blog/developing-hardwax-oil/
157•alin23•4d ago•97 comments

GraphQL: The enterprise honeymoon is over

https://johnjames.blog/posts/graphql-the-enterprise-honeymoon-is-over
189•johnjames4214•9h ago•164 comments

Price of a bot army revealed across online platforms

https://www.cam.ac.uk/stories/price-bot-army-global-index
96•teleforce•10h ago•34 comments

Baumol's Cost Disease

https://en.wikipedia.org/wiki/Baumol_effect
94•drra•14h ago•97 comments

Checkers Arcade

https://blog.fogus.me/games/checkers-arcade.html
25•fogus•2d ago•1 comments

Claude CLI deleted my home directory and wiped my Mac

https://old.reddit.com/r/ClaudeAI/comments/1pgxckk/claude_cli_deleted_my_entire_home_directory_wi...
176•tamnd•3h ago•135 comments

Microsoft Copilot AI Comes to LG TVs, and Can't Be Deleted

https://www.techpowerup.com/344075/microsoft-copilot-ai-comes-to-lg-tvs-and-cant-be-deleted
65•akyuu•2h ago•57 comments

SPhotonix – 360TB into 5-inch glass disc with femtosecond laser

https://www.tomshardware.com/pc-components/storage/sphotonix-pushes-5d-glass-storage-toward-data-...
16•peter_d_sherman•2h ago•6 comments

Checkpointing the Message Processing

https://event-driven.io/en/checkpointing_message_processing/
8•ingve•6d ago•0 comments

Show HN: Dograh – an OSS Vapi alternative to quickly build and test voice agents

https://github.com/dograh-hq/dograh
8•a6kme•6d ago•2 comments

Compiler Engineering in Practice

https://chisophugis.github.io/2025/12/08/compiler-engineering-in-practice-part-1-what-is-a-compil...
113•dhruv3006•19h ago•25 comments

Our emotional pain became a product

https://www.theguardian.com/us-news/ng-interactive/2025/dec/14/trauma-mental-health
24•worik•3h ago•7 comments

Getting into Public Speaking

https://james.brooks.page/blog/getting-into-public-speaking
114•jbrooksuk•4d ago•35 comments

GNU recutils: Plain text database

https://www.gnu.org/software/recutils/
125•polyrand•7h ago•35 comments

Efficient Basic Coding for the ZX Spectrum (2020)

https://blog.jafma.net/2020/02/24/efficient-basic-coding-for-the-zx-spectrum/
51•rcarmo•15h ago•13 comments
Open in hackernews

An attempt to articulate Forth's practical strengths and eternal usefulness

https://im-just-lee.ing/forth-why-cb234c03.txt
21•todsacerdoti•1w ago

Comments

ofalkaed•1h ago
Considerably better than most such articles that I have read on this but I think if the Forth community wants to get people into Forth it really needs to stop talking about how it can fit in a boot sector and the REPL; the former is not of interest or use to most programmers and the latter is probably a major cause of the misconception of Forth code being impossible to read.

What I see as the real strength of Forth is that if you write your program in source files, there is no abstraction. You stick your word definitions in those source files and let the application you are writing dictate the words you define instead of relying on the dictionary you built up on REPL and things quickly start becoming easy and the code remains readable. It might seem like a lot of work and endlessly reinventing the wheel but if you start with a featureful Forth like gforth it does not take that much time or effort once you have the basics down; you can build complex applications with gforth as easily as you can build up a full Forth with that minimal Forth that fits in your boot sector.

The main thing is learning that application development with Forth is top down design and bottom up writing. You break the application up into its major functions, break those into smaller functions, break those into words and then break those words into those simple sort words that everyone in the Forth community says you should write. Then you start writing code. I am just starting to get the hang of Forth and it is surprisingly quick and powerful once you start getting the sense of it.

kragen•42m ago
This is a pretty good explanation. I think it maybe undersells the importance of the REPL a bit. (I'm not a Forth expert, but I did write StoneKnifeForth, a self-compiling compiler in a Forth subset, and I've frequently complained about the quality of Forth explainers.)
vdupras•27m ago
I like the spirit of this article, but I find it strange that they open their article by quoting me, but then don't include Dusk OS's C compiler in the list.

Fairly counting SLOC is a tricky problem, but my count is 1119 lines of code for the C compiler (written in Forth of course), that's less than 8x the count of chibicc, described as the smallest.

kragen•18m ago
That's a good point, thanks. How complete is it?
entaloneralie•15m ago
It's complete in sofar as being capable of compiling C programs, but it has a few quirks.

https://git.sr.ht/~vdupras/duskos/tree/master/item/fs/doc/co...

kragen•11m ago
Possibly this is why it wasn't mentioned? There are enough differences in that list that I can't imagine any existing C library would compile unchanged.
entaloneralie•6m ago
After using cc<< for non-trivial programs, it's about as quirky as the Plan 9 C compiler, the lack of multi-dimensional arrays is the one thing that trips me up the most with cc<<
vdupras•14m ago
By design, it's not a fully compliant ANSI C compiler, so it's never going to be complete, but it's complete enough to, for example, successfully compile Plan 9's driver for the Raspberry Pi USB controller with a minimal porting effort.

So, Dusk's compiler is not apple-to-apple comparable to the other, but comparable enough to give a ballpark idea that its code density compares very, very favorably.

kragen•10m ago
It can be hard to tell how much extra complexity would be introduced by unimplemented features.
vdupras•1m ago
Indeed, and it might be why the author didn't try, but I still find it odd to not at least mention how small this C compiler is, even if it is to say that it's not apples-to-apples comparable. I mean, 8x smaller than the smallest C compiler listed is still something notable...
entaloneralie•16m ago
Came here to say exactly that, cc<< blows these numbers out of the water. Strange choice from the author.