â„–33819[Quote]
C# is a programing language from megazog, so it would be appropriate to be represented by one and not whatever is handsome squidward looking wojak is
â„–33820[Quote]
also where is my visual basic representation
â„–33843[Quote]
bump, let's get to the point
â„–33852[Quote]
learn go.
â„–33854[Quote]
>>33818 (OP)make all of these soy and rust gigachad and you've solved it
â„–33855[Quote]
what is better, compiling into machine code, compiling into bytecode which runs on your vm, of interpreting? Discuss in which fields each option is the best.
â„–33859[Quote]
>>33854Make Java and Rust gigachad, all of the rest are jartycuck
â„–33861[Quote]
I know python and javascript, I'm retarded this is accurate
â„–33862[Quote]
Make speaking English to Claude giga and all the rest tranny
â„–33863[Quote]
What if we make an OOP-like system of methods you can call for each variable (so many operations can be done easily), but we don't treat everything as an object by default?
â„–33864[Quote]
>>33863hhmm that's intriguing
â„–33872[Quote]
concatenative language with HoTT based data types and low level memory management. System F,OOP and Interpreters need to die
â„–33888[Quote]
A glimpse into a world where high quality wojaks intermingle with high quality soyjaks. May we dream.
â„–33889[Quote]
c but with the generics and classes with c# syntax ( . for static methods instead of :: like in c++)
â„–33890[Quote]
>>33889and with namespaces instead of .h nigger files
â„–33891[Quote]
>>33855machine code, it has the best performance
â„–33895[Quote]
>>33889:: is aryan
honestly java but with :: for scope resolution, memory management/delete operator and no garbage collection, and rust-style lifetime management would be the most aryan language
â„–33896[Quote]
>>33890header files are jewish and gay btw
â„–33898[Quote]
<opcode> <operand(s)>, but alao
r0xf c0xf iffff
letter prefix (where from)
immediates are loaded from next word
alu <operation> r0x0 r0x1 r0x2
operation could be 1 digit hexadecimal or something like add sub shl whatever (they both mean the same thing, the aliases just get assembled to the 4 bit alu function address)
func label
some instruction # the entry point the assembler jumps to when called
return # not a real instruction, uses jump to go BACK! with a predefined register for storing the return address. now, how WOULD i do nested function calling. it doesn't actually HAVE memory other than the i/o devices. i can see how this could get complicated fast
â„–33904[Quote]
i love how lua programmers are mist
â„–33931[Quote]
>>33818 (OP)what the fuck does half of these images mean
â„–33938[Quote]
we need to start decapitating normies like above as they have no soul and are a wast of space and air
â„–33958[Quote]
>>33896this, so much this.
â„–33961[Quote]
>>33864But we'd have to keep the scope limited in order to cut down on bloat, and for programmers to know what to expect when calling the "methods"
â„–34044[Quote]
>>33863That is literally what Rust has. It's called traits.
â„–34200[Quote]
>no cobol
>no assembly
>no zig
â„–34201[Quote]
$sh|sh
the above shell ^ can change its syntax to any possible coding language syntax while its running