2 ms·

> I can't honestly believe anyone that thinks spending twenty days on a problem is better than five minutes. Nobody thinks that and I didn't say that. I was ta

> I can't honestly believe anyone that thinks spending twenty days on a problem is better than five minutes. Nobody thinks that and I didn't say that. I was talking about that specific file (although the rest of them are equally unapproachable). > If you can't get there, it's going to be really hard to talk about what's amazing in k! Well, the thing is that at this point the only amazing things that have been talked about is that it's fast (in some specific use cases of data queries) and extremely concise. What more there is to K? What more reasons are there to use it, and with which downsides does it come with?

geocar 7y ago
> Nobody thinks that and I didn't say that. I was talking about that specific file I hope nobody thinks that, but unless you can come to terms with the fact that you're wrong, and that this is a completely fair comparison, you're going to be the guy who writes okon2 at some point instead of using a better tool. > the only amazing things that have been talked about is that it's fast (in some specific use cases of data queries) Those weasel words are preventing you from seeing what should be obvious: The k program is faster, shorter, obviously correct, and it took less time to write. That's the amazing thing. Who doesn't want that? > What more reasons are there to use it? This is the wrong way to think about things, because there's an infinity of such reasons. Instead, invert it: You should always use the best tool you can. If you don't know k, it can never be used even if it would otherwise be the best tool. I don't recommend people use k (except when it works), but I recommend people learn k because it'll make them better programmers. > which downsides does it come with? The biggest downside is that you don't know it, and the only person who can fix that is you

geocar 7y ago

> Nobody thinks that and I didn't say that. I was talking about that specific file I hope nobody thinks that, but unless you can come to terms with the fact that you're wrong, and that this is a completely fair comparison, you're going to be the guy who writes okon2 at some point instead of using a better tool. > the only amazing things that have been talked about is that it's fast (in some specific use cases of data queries) Those weasel words are preventing you from seeing what should be obvious: The k program is faster, shorter, obviously correct, and it took less time to write. That's the amazing thing. Who doesn't want that? > What more reasons are there to use it? This is the wrong way to think about things, because there's an infinity of such reasons. Instead, invert it: You should always use the best tool you can. If you don't know k, it can never be used even if it would otherwise be the best tool. I don't recommend people use k (except when it works), but I recommend people learn k because it'll make them better programmers. > which downsides does it come with? The biggest downside is that you don't know it, and the only person who can fix that is you