Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tinygrad

github.com

Post reply on HN
Print view View original

21–30 of 159 posts

Re: Tinygrad

#21

Post by hwers »

thspimpolds wrote: post #20
hwers wrote: post #14

I like this guy mostly for preserving a hacker-ish culture in the atmosphere and for just being a real human being in public. Too often do I feel like I'm just interacting with interfaces to corporations or people who self censor themselves so much they barely feel human. I'm not sure this library matters much to me but I maintain positive perspective on this guy for these reasons.

Having gone to college and knowing this guy personally from then, you would have a much different opinion... Maybe he has grown up, but back then... yeeesh

I have gone to college with similar overachievers/braggers, and now that you mention it if they were in the spotlight as much as him I'd roll my eyes pretty hard. Still though, having not gone to college with this particular one somehow I can stand it.

Re: Tinygrad

#22

Post by a-dub »

babelfish wrote: post #10
jonahx wrote: post #2

>tinygrad will always be below 1000 lines. If it isn't, we will revert commits until tinygrad becomes smaller. Love this ethos so much. Wish more projects would follow suit.

Completely disagree - limiting lines of code as an ethos makes as much sense as using lines of code written as a business metric. What if they want to add a new feature that takes another ~1000 LoC? Can they just write it as a separate library and include it as a dependency? IMO trying to minimize LoC creates a perverse incentive to split up your package when it might not need it (in the same way maximizing LoC creat…

simplicity is a virtue. the project goal apparently isn't to have a lot of features, it's to do the core thing in the simplest way possible.

Re: Tinygrad

#23

Post by lazide »

a-dub wrote: post #22
babelfish wrote: post #10

Earlier quoted context omitted.

Completely disagree - limiting lines of code as an ethos makes as much sense as using lines of code written as a business metric. What if they want to add a new feature that takes another ~1000 LoC? Can they just write it as a separate library and include it as a dependency? IMO trying to minimize LoC creates a perverse incentive to split up your package when it might not need it (in the same way maximizing LoC creat…

simplicity is a virtue. the project goal apparently isn't to have a lot of features, it's to do the core thing in the simplest way possible.

And if someone does some code golf to stay under the 1000 line limit rather than go to 1050 lines that’s an improvement?

Re: Tinygrad

#24

Post by sydthrowaway »

thspimpolds wrote: post #20
hwers wrote: post #14

I like this guy mostly for preserving a hacker-ish culture in the atmosphere and for just being a real human being in public. Too often do I feel like I'm just interacting with interfaces to corporations or people who self censor themselves so much they barely feel human. I'm not sure this library matters much to me but I maintain positive perspective on this guy for these reasons.

Having gone to college and knowing this guy personally from then, you would have a much different opinion... Maybe he has grown up, but back then... yeeesh

I'm guessing only child syndrome + rich as hell parents.

Re: Tinygrad

#25

Post by tromp »

pixelpoet wrote: post #18
hmate9 wrote: post #9

This is the guy that did some iOS jailbreaks, reverse engineered the PS3 and now runs a self driving car startup.

And the shady cheapETH business last year: https://oldreddit.com/r/cheapETH/comments/lkzkso/george_hotz...

I had to replace oldreddit by reddit to make that link work...

Re: Tinygrad

#26

Post by [deleted] »

jonahx wrote: post #2

>tinygrad will always be below 1000 lines. If it isn't, we will revert commits until tinygrad becomes smaller. Love this ethos so much. Wish more projects would follow suit.

[deleted]

Re: Tinygrad

#28

Post by ZephyrBlu »

tromp wrote: post #25
pixelpoet wrote: post #18

Earlier quoted context omitted.

And the shady cheapETH business last year: https://oldreddit.com/r/cheapETH/comments/lkzkso/george_hotz...

I had to replace oldreddit by reddit to make that link work...

Yeah should be old.reddit.com, not oldreddit.com.

Re: Tinygrad

#29

Post by hbn »

tromp wrote: post #25
pixelpoet wrote: post #18

Earlier quoted context omitted.

And the shady cheapETH business last year: https://oldreddit.com/r/cheapETH/comments/lkzkso/george_hotz...

I had to replace oldreddit by reddit to make that link work...

I'm thinking he meant to link to old.reddit which forces the old (read: non-broken) reddit UI

Re: Tinygrad

#30

Post by blueblob »

dleslie wrote: post #12
babelfish wrote: post #10

Earlier quoted context omitted.

Completely disagree - limiting lines of code as an ethos makes as much sense as using lines of code written as a business metric. What if they want to add a new feature that takes another ~1000 LoC? Can they just write it as a separate library and include it as a dependency? IMO trying to minimize LoC creates a perverse incentive to split up your package when it might not need it (in the same way maximizing LoC creat…

> What if they want to add a new feature that takes another ~1000 LoC? They don't. The LoC limit exists as much to avoid scope creep and maintain focus as it is about anything else.

It trades off utility for managing scope creep. Keeping this code base tiny necessarily means that anything that uses it would need to write more code. If the point is a demonstration instead of a usable library, then that is good because it is much easier to follow without excess complexity.
Post reply on HN