| 8 Jan 2020 |
| 16:51:55 |  yorickpeterse | Once we have a self-hosting compiler I plan to dig into this more |
| 17:43:51 |  kiti_nomad | 加油 |
| 20:18:06 | yorickpeterse | Ugh, the sheer amount of work needed for the compiler is at times a bit depressing |
| 20:18:23 | yorickpeterse | e.g. I'm working on the type checker, but there isn't really a single place you can start and incrementally work your way up |
| 20:18:42 | yorickpeterse | because right away you need 15 different things, all of which require careful thinking or risk having to rewrite them further down the line |
| 20:27:16 |  fsx | How to you manage to make time for this? Seems like an incredibly complex thing. |
| 23:56:09 | yorickpeterse | I try to spend an hour or two every evening on this, but it's challenging next to a full time job |
| 12 Jan 2020 |
| 08:26:37 | kiti_nomad | Can you add a version number to the import statement |
| 08:27:51 | kiti_nomad | Of course, you can also specify the version number when declaring the module |
| 08:28:50 | kiti_nomad | Maybe inko has package management tools, I don't know yet. Where you can specify the relevant version number you need |
| 15:00:15 | yorickpeterse | No, versioning won't be built into the import statements/module names |
| 15:00:48 | yorickpeterse | There's no package management either yet |
| 15 Jan 2020 |
| 08:50:04 | kiti_nomad | The purpose of calculation is to obtain the result of the operation. Except for the result of the operation, everything else is a side effect. In order to obtain more computing results, a programming language must support concurrency, distributed, and parallel. |
| 08:51:11 | kiti_nomad | It would be nice to write distributed parallel programs as easily as using instant messaging software |
| 08:52:23 | kiti_nomad | Obviously languages like inko and erlang have such opportunities。i love inko! |
| 22:05:55 | yorickpeterse | Thanks :) |
| 19 Jan 2020 |
| 21:44:34 | kiti_nomad | I feel that inko is Rust running on a virtual machine |
| 21:55:21 | kiti_nomad | I was wrong, I looked at the features on the homepage of inko, I thought inko was a language like erlang |
| 23:40:09 | yorickpeterse | Inko is quite different from Rust, and indeed closer to Erlang |
| 23:40:22 | yorickpeterse | The VM is written in Rust however |
| 20 Jan 2020 |
| 05:56:49 | fsx | What reasons do you have for writing Inko? I can imagine that writing Inko (in the future) would be more pleasant than writing Rust. The syntax looks a bit daunting and cumbersome (I've only followed a tutorial and read some code). |
| 05:57:30 | fsx | Just curious. Waiting on the train to work. Have nothing better to do. |
| 17:01:41 | yorickpeterse | I want a high-level language better suited for concurrent programs compared to Ruby, Python, etc. Erlang is a source of inspiration, but not quite what I am looking for (e.g. I am not the biggest fan of functional languages) |
| 21 Jan 2020 |
| 19:15:46 | kiti_nomad | I think concurrency is as important as distribution |
| 19:19:51 | yorickpeterse | Inko won't have built-in support for distributing work across hosts, I believe that's something better suited for an external library |
| 19:21:57 | kiti_nomad | you can design it simple enough, I don't care which it's built in |
| 19:28:04 | yorickpeterse | I'm not going to though, since that's way out of the scope of Inko. |
| 19:31:15 | kiti_nomad | 👌 |
| 19:33:00 | kiti_nomad | Whether you succeed or not, this is a test of your thinking |
| 19:38:19 | kiti_nomad | I am in wuhan, during this time I think I have a lot of time to learn inko |
