|
Members in Shoutbox
None.
Shoutbox Search
Shoutbox Commands
/w [name] > Whisper
/r > Reply to last whisper /me > Marks as action Shoutbox Information
Moderators may delete any and all shouts at will.
|
Global Shoutbox
Please log in to shout.
[2016-12-05. : 3:09 am]  CecilSunkure -- It's like where is the tradeoff? Should we just require good C programmers? Or should we take a performance hit and higher lesser goons...[2016-12-05. : 3:08 am] CecilSunkure -- jjf28jjf28 shouted: CecilSunkure jjf28 CecilSunkure an interpreter could just run the byte code itself, or the hardware could have a built in byte-code processor, or ofc, JIT compilation could be used - the exact behavior is platform dependent but even if it's JIT compilation there's a big difference from C-style compilation Bytecode still needs to be compiled. All bytecode does is remove heftier front-end parsing. It's still interpreted. JIT is pretty cool, but at that point really why not use C? Interpretation for cross platform is silly, when interpretation can be much more powerful for fast iteration time... Cross-platform at the cost of performance? Really? I'd argue a good C programmer can shit out features faster than any Java goon, and have it still be cross-platform, without any performance hits.[2016-12-05. : 3:06 am]  Moose -- Because embedded systems. Like, nobody putting the JVM on your microwave. Yet. X^D[2016-12-05. : 3:05 am] jjf28 -- CecilSunkureCecilSunkure shouted: Compiling = interpreting a JAR file. fyi jjf28jjf28 shouted: not really CecilSunkureCecilSunkure shouted: What do you mean not really. That's exactly what interpreting is -- runtime compilation an interpreter could just run the byte code itself, or the hardware could have a built in byte-code processor, or ofc, JIT compilation could be used - the exact behavior is platform dependent but even if it's JIT compilation there's a big difference from C-style compilation[2016-12-05. : 3:05 am]  Dem0n -- I guess literally all android phones are unusable pieces of shit X^ D[2016-12-05. : 3:04 am] CecilSunkure -- so i guess if u just write basic bitch code it doesn't matter if u use java[2016-12-05. : 3:03 am] CecilSunkure -- Dem0nDem0n shouted: CecilSunkure why do people act like we still use computers with like 64 mbs ram and shit. like this matters LMAO It only does for certain pieces of code[2016-12-05. : 3:03 am] Dem0n -- CecilSunkureCecilSunkure shouted: So Java: compile your program every time it's run! why do people act like we still use computers with like 64 mbs ram and shit. like this matters LMAO[2016-12-05. : 3:03 am] CecilSunkure -- I'm now more interested in watching this guy write than explain FT LMAO[2016-12-05. : 3:01 am] Moose -- https://www.nayuki.io/page/free-small-fft-in-multiple-languages oh ya, this was part of what I ended up using[2016-12-05. : 3:00 am] CecilSunkure -- https://www.youtube.com/watch?v=1JnayXHhjlg -- beautiful AF hand writing[2016-12-05. : 2:58 am] Moose -- https://en.wikipedia.org/wiki/Fast_Fourier_transform ya, the ones from here[2016-12-05. : 2:57 am] CecilSunkure -- So there's multiple flavors of algorithms to apply FFT? Cooley-Tukey made one, and you mentioned another?[2016-12-05. : 2:56 am] Moose -- The DFT isn't too bad to understand the computation of, but for the amount of depth I went into understanding, anything more advanced than the Cooley-Tukey FFT algorithm does magical bullshit that just works LMAO[2016-12-05. : 2:53 am] Moose -- FFT approximates a function (the signal) as a sum of sin/cos at different frequencies[2016-12-05. : 2:51 am] CecilSunkure -- Also FFT approximates a frequency as a sum of sin/cos. So I'm guessing there's some kind of iterative matching algorithm to generate that sin/cos sum[2016-12-05. : 2:50 am] Moose -- CecilSunkureCecilSunkure shouted: C: Compile it once and run the machine code from then on Ya, but they called javac the compiler and building the JAR compiling, so nobody even knows what compiling really is anymore LMAO[2016-12-05. : 2:50 am] CecilSunkure -- OK so FFT is like, transform into frequency domain. Data is exposed and we modify it easily. Then apply inverse.[2016-12-05. : 2:47 am] Moose -- Of course they all offer pre-built binaries for different platforms, but still[2016-12-05. : 2:46 am] Moose -- jjf28jjf28 shouted: Mini Moose 2707 have fun with your 1k max end users C|X^D Yeah, who the fuck uses Linux or Apache HTTPD or git or Octave or ...[2016-12-05. : 2:46 am] CecilSunkure -- There's lexing, parsing, and codegen in both a C compiler and the interpreting of a JAR file[2016-12-05. : 2:45 am] jjf28 -- Mini Moose 2707Mini Moose 2707 shouted: jjf28 use source code as distributable imo C|X^D have fun with your 1k max end users C|X^D[2016-12-05. : 2:45 am] CecilSunkure -- What do you mean not really. That's exactly what interpreting is -- runtime compilation[2016-12-05. : 2:44 am] Moose -- jjf28jjf28 shouted: CecilSunkure compiles into non-cross platform distributables use source code as distributable imo C|X^D[2016-12-05. : 2:44 am] jjf28 -- CecilSunkureCecilSunkure shouted: jjf28 OK but then we can say Java interprets into non-cross platform runtimes too can deploy executable JARs anywhere with a JVM, can't deploy a compiled C program anywhere with C[2016-12-05. : 2:44 am] CecilSunkure -- jjf maybe you mean, use Java because it's runtime interpreted. It sounds like you might have conflated "cross platform" with "runtime interpreted"[2016-12-05. : 2:43 am] Moose -- Like, I love C, I really do, I configure/make/install all day, I just don't know it. XD[2016-12-05. : 2:43 am] CecilSunkure -- jjf28jjf28 shouted: CecilSunkure compiles into non-cross platform distributables OK but then we can say Java interprets into non-cross platform runtimes too[2016-12-05. : 2:42 am] jjf28 -- CecilSunkureCecilSunkure shouted: The only thing about C that isn't cross platform is platform specific headers, which need to be accessed by the JVM itself anyway compiles into non-cross platform distributables[2016-12-05. : 2:42 am] Moose -- TBH, probably just mad that Java is OO and just mad at OO to mask your hatred for shitty programmers LMAO[2016-12-05. : 2:41 am] CecilSunkure -- The only thing about C that isn't cross platform is platform specific headers, which need to be accessed by the JVM itself anyway[2016-12-05. : 2:41 am] Moose -- You could write the JVM in whatever if it conforms to the Java specs[2016-12-05. : 2:40 am] Moose -- jjf28jjf28 shouted: CecilSunkure *cough* cross-platform *cough* Ya, if your platform has a JVM LMAO[2016-12-05. : 2:40 am] jjf28 -- CecilSunkureCecilSunkure shouted: literally no reason to use it over C *cough* cross-platform *cough*[2016-12-05. : 2:39 am] CecilSunkure -- Fucking hipsters cross compiling their garbage collected trash[2016-12-05. : 2:38 am] Moose -- TBH, there are compilers that can turn Java into machine code or w/e[2016-12-05. : 2:38 am] CecilSunkure -- Either barebones low level, or just high in the sky. No pretending.[2016-12-05. : 2:37 am] CecilSunkure -- In that case use a real high level language. Like please, go all the way. No fence sitting![2016-12-05. : 2:37 am] Moose -- Use it when conserving developer time is more of a priority than runtime, tbh[2016-12-05. : 2:37 am] CecilSunkure -- So instead of fake registers, it will just shit out native instructions and run those[2016-12-05. : 2:34 am] CecilSunkure -- JVM is implemented in C. So it's reading in Java bytecode, running a shitload of C switch statements, and then executing things with an array of integers that represents "registers" of a machine |