| 27 Sep 2022 |
 eris | In reply to @chrispsn:matrix.org
there's a callback to when Conor asked in this room about the state of the k ecosystem here | 11:48:23 |
| eris | i remember someone asking | 11:48:28 |
 chrispsn |
Is there like a "State of K" article? I have read:
- https://k.miraheze.org/wiki/History
- https://aplwiki.com/wiki/K
I kind of want to understands how K folks feel about K3 vs K4 vs K7 vs K9? What do most k-users choose to write in when do hobby stuff? What is the most popular one, etc
^ here, from code_report#8896
| 12:11:33 |
| chrispsn | tbh if someone asked me why i like k, "i like where and dicts" is like 80% of the answer | 12:15:22 |
| chrispsn | that and the constant struggle to do more with less, and finding there's always room to improve, it's just that it hasn't been thought of yet | 12:16:14 |
| chrispsn | back to the summary: some discussion/speculation of why k is fast | 12:23:41 |
| chrispsn | the importance of being bundled with a DB to its success | 12:25:45 |
| chrispsn |
2 valence and projections making k special in the apl world
| 12:27:42 |
| chrispsn | * more than 2 valence and projections making k special in the apl world | 12:27:54 |
| chrispsn | mentions b (may be worth putting bcc in the shownotes) | 12:31:54 |
| chrispsn | and for APL?, ktye's zoo has it as an option | 12:32:53 |
| chrispsn | * and for "APL?", ktye's zoo has it as an option | 12:33:01 |
| chrispsn | * and for "APL?\", ktye's zoo has it as an option | 12:33:07 |
| chrispsn | and that's a wrap | 12:37:13 |
 ColTim#5847 | I guess something that trips me up a lot is the lack (and questionable nature of) publicly available information on K/Q/Kx/etc. | 13:09:36 |
| ColTim#5847 | my analogy is that it's like going to a corporate headquarters and asking people standing around outside what the company does | 13:10:02 |
 ngn | for me the major problem is the lack of a free implementation. in other respects k is superior to other array langs. | 14:00:02 |
| ngn | i think documentation is not so important. the primary concern should be to get the design right. if it picks up users and (more importantly) commercial users, someone will eventually document it. look at shakti - there are even several competing documentation sets. | 14:03:00 |
| ngn | ColTim#5847: don't you think q's docs are ok? | 14:08:32 |
| ngn | well mostly.. | 14:09:05 |
| ColTim#5847 | I'm referring more to things around the language | 14:09:13 |
| 28 Sep 2022 |
| ngn | does anyone have or can anyone think of an arrayful solution to https://adventofcode.com/2018/day/1 part2? | 13:43:14 |
| ngn | summary: least n such that +\n#inputs has a duplicate | 13:44:53 |
| ColTim#5847 | would BQN's "progressive index of" do most of the heavy lifting? | 13:56:15 |
| ngn | ColTim#5847: is that about the aoc problem or something unrelated? | 13:57:48 |
| ColTim#5847 | the AoC one | 13:58:12 |
| ngn | ok. what is "progressive index of"? | 13:58:35 |
| ColTim#5847 | https://mlochbaum.github.io/BQN/doc/search.html | 14:01:08 |
| ColTim#5847 | it's like x?y find except that duplicates map to other instances in the array being looked up from | 14:01:51 |
| ngn | ColTim#5847: how does that help? | 14:15:38 |
