Ironically the reason Karpathy's is better is because he livecoded it and I can be sure it's not some LLM vomit.
Unfortunately, we are now indundated with newbies posting their projects/tutorials/guides in the hopes that doing so will catch the eye of a recuiter and land them a high paying AI job. That's not so bad in itself except for the fact that most of these people are completely clueless and posting AI slop.
I think I must have just spent more time (5 mins) looking at this repo trying to understand why you posted it, than you spent actually coding this.
I don't want to put you off, but there's no substance at all here, I'd have assumed Claude wrote it based on the fact you've vendored in rules, but the code is so questionable, even an LLM from 2022 would do better. E.g. 'flattenData' from utils could just be [1] rather than a BFS, though I don't really get why your public API allows TensorData to be a single integer in the first place, 50% of your logic is to work around that.
But rant over. My point is, maybe post this when you've built even 5% of PyTorch, or learnt something of value, or have something tangible to impart upon us, rather than a library of ill-thought-out array utils.
2. It’s clear you didn’t read the rules folder because it’s a rule to tell cursor to teach me
3. You say you don’t understand why TensorData can be a single integer. Scalars are tensors too. I’m trying to support PyTorch’s spec and ops as much as possible which is why I’m supporting it. The obvious use cases are for reduction ops and scalar unary ops.
+1 to a Kobo, they cheaper and better than Kindles, with full Calibre support (https://github.com/kovidgoyal/calibre - OSS which has been in development for ~20 years!).
The way you install additional software is literally just moving files into folders whilst its plugged into your computer. I'm sure it could handle Tailscale.
I agree with your sentiment that the Kobo is better than the Kindle from an... ethical standpoint, if you have the money for one. However, it is worth noting that Kindles will always be cheaper than Kobo devices [0] due to economies of scale and lockscreen advertisements (removable with jailbreaking). From a pure cost perspective, and assuming the user is technically-minded enough to accomplish the jailbreak, the Kindle is likely always [1] a better deal.
[0] as of today, 12/8/25, the "base model" Kindle 11th Generation is priced at $109.99 USD, and the respective Kobo Clara BW is $139.99 USD.
[1] I say "likely always" to cover my bases. To my knowledge Calibre supports Kindle, just not as well as Kobo. That said I have found that the KOreader app is more than powerful enough for my use case (reading my own epubs, using dictionaries, etc.)
The current colour kindles and kobos don't use real eink colour. It's just a bw screen with lcd colour overlay (eink kaleido)
The real colour screens are used on the remarkable (eink gallery) and they are indeed slow for full page updates though remarkable seems to have done a lot of smarts for local updates while drawing.
Where do I get DRM-free ebooks to put on a Kobo? I don't support breaking DRM. So I'm using a Kindle because it has the best access to and integration with almost any book I want.
I kinda love that buried in the koreader menu somewhere is an option that drops me at a linux shell. I have no use really for this feature, but i like it. Good for those times you absolutely have to crank out some awk on the plane or whatever. :)
But what I'd really like is an option not to hide the navigation bar while KOReader is open. I work with technical PDFs and need to jump between applications very often.
https://news.ysimulator.run/item/121 - I was interested to see what the common archetypes would have to say about this very post, therefore I submitted it.
I've been PSAs before on the front page with a reminder to check your flagged stories. I and others visited the link and were surprised to see how many stories I had fat-finger flagged. In fact I had never intentionally flagged a story yet the list was at least 10-15 long
Wow I checked mine and had about 20. I've never intentionally flagged a submission as far as I can remember and none of these were even close to flag worthy.
I've apparently flagged 6 articles and 1 post by accident.
That said, it's possible this is all accounted for in the system. Maybe the mods only get notified above some threshold and that threshold has been tuned to ignore the background noise of accidental flags. Adding a confirmation would lower the noise level, but perhaps not translate into any real benefit.
This is a punny code, and I'm fine - if not happy - that HN doesn't choose to render their underlying unicode symbols. It's very easy to spoof URLs this way, e.g. using a symbol from another language to craft a look-alike URL that can match a reputable site.
Browsers like now Chrome try and alert you if the URL visually looks spoofed (because they do support unicode symbols in the omnibox), but I'm yet to see how well this holds up in production.
And I hope in even 20 years we still can't use emojis here, our language isn't so pitiful that we must regress to brightly coloured symbols.
Basically what you’re saying is that other people (including all major browsers) have solved the problem rather than spitting out the underlying punycode which is human-unreadable and is at the expense of domains in languages that don’t use the Latin alphabet.
I imagine this issue is easily solved by everyone else but it’s just kind of accepted on one of the most popular tech industry message boards run by one of the most successful incubators/investment firms of all time who certainly has the money to make the experience less ancient.
Any Googler can write code and open source it on the Google GitHub (within reason, the process is quite straightforward). So no, Google as an entity does not official endorse it, all it means is at least one employee is working on that particular effort.
Easier for humans to parse, but introduces the threat vector of malicious attackers modifying the history and force submitting malicious code at or before a pinned time. That's why lock files exist.
SHA is still the way to go for those who are security sensitive.
reply