| 30 Mar 2018 |
| *  @emilia:disroot.org pokes @davidar:matrix.org | 18:29:00 |
| @emilia:disroot.org | to perhaps set a room title :3 | 18:29:15 |
| @emilia:disroot.org | Nathan: it is written in a new language hurhur | 18:35:38 |
| 31 Mar 2018 |
 @SyrupThinker:matrix.org | 
Download Screenshot_Settings_20180331-131212.png | 11:12:36 |
| @SyrupThinker:matrix.org | Firefox default to Korean now... | 11:12:47 |
| @SyrupThinker:matrix.org | *defaults | 11:12:56 |
| @emilia:disroot.org | nice | 12:33:52 |
 Nathan |
Nathan: it is written in a new language hurhur
A bit late, but how much "lower" is Go than Python? Because as I understood Python being a high level language was one of the performance problems. | 12:33:01 |
| @emilia:disroot.org | Aren't they both kinda high level﹖ | 12:35:50 |
| @emilia:disroot.org | no, high level languages as such aren't really a performance problem | 12:36:02 |
| @emilia:disroot.org | compiling code vs interpreting it can be one (as in run the code on bare metal, or run code on bare metal which runs your code) | 12:36:24 |
| Nathan |
Aren't they both kinda high level﹖
Well that is what I was wondering. | 12:34:50 |
| Nathan | Ah okay. Isn't Python interpeted at run-time? | 12:35:31 |
| @emilia:disroot.org | Normally yes | 12:38:02 |
| @emilia:disroot.org | I think there are python compilers, but don't qoute me on that :p | 12:38:19 |
| Nathan | So that could be a performance problem right? | 12:36:23 |
| @emilia:disroot.org | high level vs low level usually doesn't have that much to do with speed, theoretically assembler code would be the fastest, but perhaps your compiler is just smarter at optimizing than you are ;) | 12:39:13 |
| @emilia:disroot.org | It coudl i guess, haven't really looked at synapse so not sure | 12:39:27 |
| Nathan | Oh, I always thought that low-level languages were faster and that that was the advantage of high-level languages. | 12:40:30 |
| @emilia:disroot.org | High level languages don't have to be slower, some are i guess :3 | 12:43:15 |
| @SyrupThinker:matrix.org | Nathan: The separation of high and low level is more about abstractions and less about interpretation of the code.
In C you need to be very verbose for simple things because you can control what happens directly (memory (de)allocations, pointers to raw memory etc.), in Python you don't need to worry about that, thr language abstracts that away, is thus higher level.
Rust for example has features that are known from higher level languages, like iterators, closures, all the functional goodness, which makes it more higher level than C or C++, despite having | 13:08:05 |
| @SyrupThinker:matrix.org | comparable speed and being compiled | 13:08:56 |
| @emilia:disroot.org | interesting | 13:21:38 |
| Nathan |
In C you need to be very verbose for simple things because you can control what happens directly (memory (de)allocations, pointers to raw memory etc.), in Python you don't need to worry about that, thr language abstracts that away, is thus higher level.
Yes, so that's why I thought that C is faster in general, because is doesn't have those abstractions.
| 13:19:38 |
| @emilia:disroot.org | apparently writing 1.000.000.000,1 and 1,000,000,000,000.1 are both wrong | 13:22:04 |
| Nathan | Why? | 13:20:49 |
| Nathan | To prevent confusion? | 13:21:14 |
| @emilia:disroot.org | wikipedia sais that the correct character for seperation according to SI/ISO 31-0 is a space | 13:24:31 |
| @emilia:disroot.org | so 1 000 000 000 000,1 would be ok | 13:24:49 |
| @emilia:disroot.org | lol first it sais current standard and then superseeded standard | 13:26:08 |
