Can anyone mention how you can "save the state" so it doesn't have to train from scratch on every run?
Readit Newsborplk commented on Microgpt karpathy.github.io/2026/0... · Posted by u/tambourine_man
borplk commented on Claws are now a new layer on top of LLM agents twitter.com/karpathy/stat... · Posted by u/Cyphase
I don't understand the mac mini hype. Why can it not be a vm?
I don't know but I'm guessing that it's because it makes it easy to give access to it to Mac desktop apps? Not sure what's the VM story with Mac but usually cloud VM stuff is linux so it may be inconvenient for some users to hook it up to their apps/tools.
You have to think about the threat model. The OS itself is rarely a problem. It's all the other stuff around it such as apps, browsers, websites, etc...
What is your use case? If you need a private computer to read and write you can setup a desktop with Linux and air-gap it (ZERO connectivity to the outside world, no wi-fi, no internet, nothing). Then transfer specific data in and out of it using a USB stick. That's just one example.
In all of this, people forget that NPM packages are largely maintained by volunteers. If you are going to put up hurdles and give us extra jobs, you need to start paying us. Open source licenses explicitly state some variation of "use at your own risk". A big motivation for most maintainers is that we can create without being told what to do.
I had 25 million downloads on NPM last year. Not a huge amount compared to the big libs, but OTOH, people actually use my stuff. For this I have received exactly $0 (if they were Spotify or YouTube streams I would realistically be looking at ~$100,000).
I propose that we have two NPMs. A non-commercial NPM that is 100% use at your own risk, and a commerical NPM that has various guarantees that authors and maintainers are paid to uphold.
Yes! I despise how the open source and free software culture turns into just free labour for freeloading million-dollar and billion-dollar companies.
The culture made sense in the early days when it was a bunch of random nerds helping each other out and having fun. Now the freeloaders have managed to hijack it and inject themselves into it.
They also weaponise the culture against the devs by shaming them for wanting money for their software.
Many companies spend thousands of dollars every month on all sorts of things without much thought. But good luck getting a one-time $100 license fee out of them for some critical library that their whole product depends on.
Personally I'd like to see the "give stuff to them for free then beg and pray for donations" culture end.
We need to establish a balance based on the commercial value that is being provided.
For example I want licensing to be based on the size and scale of the user (non-commercial user, tiny commercial user, small business, medium business, massive enterprise).
It's absurd for a multi-million company to leech off a random dev for free.
borplk commented on Ask HN: We built an air-gapped document vault with encrypted print and export · Posted by u/KevinG777
Not quite what you asked, but here are some thoughts.
Do you have the sales "fire power" to sell this solution?
Because it sounds like the kind of thing that governments or complicated companies would potentially buy. And they are not easy to sell to, to put it lightly.
I used to have some startup ideas that are in this category => "Most people don't need or want it, and people who do need or want it are not going to buy it from my flimsy bootstrapped startup (they will take 2 years and spend 100M with Deloitte on it instead)".
Not sure what's your situation/size/funding/scale but personally I'm happy to stay away from that category.
Driving 7 minutes to work and stopping at a drive-thru to pick up McDonalds breakfast every day. The man is a true American hero.
His whole "I love fast food and coca cola" thing is a fake persona
Simply speaking "Postgres for everything" is meant as a fool-proof default choice for the average person making an average app. It helps startups avoid tangling themselves with some bespoke/complex combination of Redis+Postgres+RabbitMQ+MongoDB from day 1 for their app that reaches a peak of 10 requests per second with 100 daily average users if they are lucky.
This usually happens because a junior dev wants to have fun and pad their resume while playing around with tech. Or they are insecure and want to make the "maximally proper" choice with everything so they appear to be an expert. For example they think storing any JSON or cache data in Postgres is somehow incorrect or forbidden and they must use something more specific to feel like they've made the correct choice.
In general Postgres will take people very far. Majority of companies could start with it and live with it forever. If they are lucky enough to need something else by that point hopefully they have enough money and staff to re-evaluate the stack and make changes for the future of the company.
routing in SPAs
Yes but usually the routing is done as part of a library so the developers are unlikely to interact with the API themselves. It will just affect the internals of their routing library. Those libraries already have their own implementation of similar stuff.
At first glance it seems like this API would be more useful on the server side to do URL routing. What are the use cases for it on the client side?
If true, looking forward to the post-mortem. I guess no-one is on-call at Cloudflare.
It would appear that there is no sense of urgency or seriousness at the company and I assume that they might have taken the AI agent cool-aid.
Clearly that is not going so well, and it seems like they want to ruin their reputation on every incident.
They seem to beat their chest in every elaborate highly technical post-mortem as they report the timestamp of events down to the millisecond as if we should be impressed!