Recent submissions

Comment · 4 months ago
Is slopcoded somehow better?
Comment · 4 months ago
No it's not. Araq does use LLM to generate code in Nimony but his approach involves very strict control over the produced code, it's nothing like Bun's Zig to Rust endeavor where they just asked it to dk the migration and it produced a million lines of incomprehensible code. Calling it slopcoding is a misnomer.
Comment · 4 months ago
My love letter video turned out a bit chaotic, I apologize upfront.

But the core points I make there I can get behind any day of a week. I do think Nim is the best language out there and I'm tired of pretending it isn't (insert the DeNiro-Phoenix-Joker meme here :-)

Comment · 6 months ago
On the other hand, this format allows people from all around the world to participate.
Comment · 6 months ago
We use custom types for that usually, optionally with parametric polymorphism.

But as others said already, Nimony (codename for the next Nim iteration) introduces revamped concepts which should be even more convenient.

Comment · 6 months ago
Please do share your progress with FigDraw. Interactive demoes always look great.
Comment · 6 months ago
I plan to give a couple of talks this year.

Can't wait for NimConf, it is way overdue.

Comment · 2 years ago
Comment · 2 years ago
Thanks for the kind words!

> Presumably, your server stores a registry of Device IDs and IPs to route messages?

Not IPs but Push API registration objects.

> What about replacing this with some sort of partitioned DHT to make it decentralized?

I guess this could be done but it's a task I can't tackle at this point.

> Also, the messages flow through your servers?

Yes but I don't store them. My API just dispatches the message to the recipient's push service. Which means the message exists on my server only in the form of an in-memory variable for several microseconds between being received and sent further.

> Would it be possible to set up WebSocket connections between the users instead, and how would that compare from a security model perspective?

This generally can't be done in a PWA. OS won't allow a persistent WebSocket to run in background.

Also, this would disclose too much information about a client to all the other clients. Currently, all I know about other clients is their Device IDs which are just random strings.

Comment · 2 years ago
Yeah Apple kinda hates PWA it seems. I honestly tried to make it usable on iOS but it just fails with anything I'm trying to do.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton