Message from @Silver0Fox

Discord ID: 481450846731632658


2018-08-21 13:08:10 UTC  

yes

2018-08-21 13:08:17 UTC  

welcome to the "modern" desktop app

2018-08-21 13:08:23 UTC  

not only that, but the discord client itself is 32-bit yet the installer forces you to use a 64-bit system even if the software doesn't 👏 👏 👏 👏

2018-08-21 13:08:42 UTC  

who made discord anyway

2018-08-21 13:08:52 UTC  

What effect can that have on performance?

2018-08-21 13:08:55 UTC  

a bunch of code bros who didn't like slack or skype?

2018-08-21 13:08:58 UTC  

well

2018-08-21 13:09:02 UTC  

discord being 32-bit is actually a good thing

2018-08-21 13:09:09 UTC  

because it can access/address less memory

2018-08-21 13:09:18 UTC  

heh

2018-08-21 13:10:37 UTC  

32-bit software actually runs slightly faster than 64-bit too, but due to architecture optimizations in modern processors, the effect is not really noticable

2018-08-21 13:11:21 UTC  

generally speaking, it's best if you compile your software for both 32-bit and 64-bit systems

2018-08-21 13:11:49 UTC  

but of course in the case of discord, the 32-bit/64-bit issue is mostly Electron's fault specifically, the people who made Electron probably have no idea how to use a compiler

2018-08-21 13:12:16 UTC  

and honestly I don't blame them, it takes over 30 hours to compile Chromium, why would you bother?

2018-08-21 13:12:43 UTC  

node.js has some pretty decent binding systems for calling into native libs, i wonder if they actually use it

2018-08-21 13:12:56 UTC  

What is compiling?

2018-08-21 13:13:05 UTC  

.exe

2018-08-21 13:13:16 UTC  

z80 can handle this one

2018-08-21 13:13:17 UTC  

compilation is the translation of high level code into assembly code your system can understand

2018-08-21 13:13:17 UTC  

lol

2018-08-21 13:13:46 UTC  

Your turning the data into something readable?

2018-08-21 13:14:25 UTC  

python however, is not a compiled language. it is itself a complex program that scans and executes your code on the fly. usually called an "interpreter"

2018-08-21 13:14:32 UTC  

aka you go from a hello world program to a bunch of 64-bit or 32-bit instructions the system will understand, so when you open your compiled file up into a hex editor, you'll only see something like.. `<insert random garbage here, too lazy>`, because it's nothing like your normal code

2018-08-21 13:14:57 UTC  

interpreters do compiling on the fly, JIT interpreters do compiling ahead of time

2018-08-21 13:15:10 UTC  

JIT interpreters, in rare cases, can actually be faster than compiled languages

2018-08-21 13:15:29 UTC  

take the Julia language's default interpreter's JIT system, for example

2018-08-21 13:15:53 UTC  

because Julia is like LUA on steroids

2018-08-21 13:16:12 UTC  

@Silver0Fox doesnt know what any of those langs are dude 😛

2018-08-21 13:16:18 UTC  

uhh

2018-08-21 13:16:26 UTC  

shit

2018-08-21 13:16:27 UTC  

well

2018-08-21 13:16:33 UTC  

its just making code into a program that you can actually run on your computer

2018-08-21 13:16:42 UTC  

yeah

2018-08-21 13:16:43 UTC  

basically

2018-08-21 13:16:47 UTC  

LUA is typically used to make plugins and addons for stuff

2018-08-21 13:16:52 UTC  

it's an embeddable language

2018-08-21 13:17:08 UTC  

so a LUA interpreter usually gets crammed into different projects to help with modular code

2018-08-21 13:17:10 UTC  

Nope, but I think I get it. It's different methods for your computer to process the instructions depending on the language and your desired outcome

2018-08-21 13:17:49 UTC  

the point is more that your CPU can only do the most basic instructions, like load two numbers from memory, add them together, and store the result somewhere else in memory

2018-08-21 13:17:50 UTC  

well your computer in the end processes them all the same way but sort of

2018-08-21 13:18:34 UTC  

every CPU has a slightly different instruction set, but most of them all come under one architecture, like x86 or ARM