/g/ - Technology

install openbsd

[Make a Post]
[X]





How do I become /g/? Nanonymous No.1851 [D][U][F][S][L][A][C] >>1865
File: a8cf082d1341f167fb89c9e14fbed6fc06da6366f78de0d9da4330380fe47d99.jpg (dl) (50.69 KiB)

I've always been interested in tech but I've never really followed through in studying it. Where do I start to become a computer wizard?
I have some woman-tier Java and C++ knowledge but I want to learn more, like how to create an OS or a programming language.
What resources should I study? How do I become /g/?

Nanonymous No.1852 [D] >>1853

Start by learning a real programming language like C and asm for your cpu of choice, dosn't have to be x86-64.

Anonymous (OP) No.1853 [D] >>1885

>>1852
I already ordered a fair amount of books on C. I was planning on learning it to supplement my C++ knowledge.
As for an assembly language, I'll look into that.

Nanonymous No.1856 [D] >>1860 >>1865

If you want to become /g/, just get good at LARPing. Run Linux, or preferably Windows, but pretend that you run OpenBSD, and be sure to sperg out about anything that's not written in ANSI C. Also, use the word "botnet" a lot, even when it doesn't really apply. Especially when it doesn't really apply.

If you want to write an OS, go to https://wiki.osdev.org/Main_Page

If you want to create a programming language, you don't even need a computer. You can do it with pen and paper. I assume you mean you want to create a compiler, though. So read the dragon book.

If you just want to into programming in general, study algorithms (there are many free MOOCs) and data structures and implement them in C++. You don't even need to learn a new language if you don't want to.

Nanonymous No.1860 [D] >>1885

>>1856
>wiki.osdev.org
OSdev.org is good for the extreme basics, but everyone there is hyper-gay and insists that you enable some shitty protected mode and paging bullshit (which only exists on botnet CPUs). I was looking for resources for writing an OS for my old 286, but most of the knowledge was not applicable because they (for some retarded reason) assume that you're programming for 386+ CPUs. OSdev.org also assumes that real mode == BIOS and spergs out whenever you try to use it. Overall it's been extremely unhelpful and I have had more success looking on old DOS programmer's guides and documentation (even though my OS is far from a DOS clone).
Daily reminder that 386SL and 486+ are BOTNET because they have (((System Management Mode))).

Nanonymous No.1865 [D]

>>1856
>read the dragon book
Wtf? Making a simple compiler does NOT need the dragon book. Parsing a language into a stream of tokens is easy. Converting the stream of tokens into an AST is also relatively easy. Compiling the AST into machine code or bytecode is also not hard.
The issue is the amount of work involved. It takes a long time to write. Making your compiler optimizing is also very difficult. But to make some simple C compiler, or a compiler for your own custom-designed language wouldn't be super hard.
Write a brainfuck compiler if you want something easy. I once made a brainfuck-to-ASM converter but it wasn't optimizing and it only worked on (((64-bit))) (((Loonux))) so I got rid of it after I switched to openbsd.
>>1851
Learn real-mode assembly and write a shitty operating system (see the mikeOS source code). Then start designing a new real-mode OS that doesn't use the BIOS. This will teach good programming habits because you know exactly what is involved at the machine-code level when you use a high-level language construct. It will also teach you to make your programs small and simple, since you only have a maximum of 640KiB to work with (less if you're using a botnet computer with SMM.
After you've done that, learn C and use it as your main language.

Nanonymous No.1885 [D] >>1886

>>1853
Hitting the books is a meme. Start with a 2 hour tutorial for syntax and basic concepts. Then move onto reading the source code of a well written project. Then start editing the source code. For c I recommend 9cc:
https://github.com/rui314/9cc
It's small, unbloated, practical, and best of all is missing lots of features, so you have your work cut out adding them.
>>1860
>I was looking for resources for writing an OS for my old 286
>they (for some retarded reason) assume that you're programming for 386+ CPUs
wow. and I bet they told you to fuck off when you complained.

Nanonymous No.1886 [D]

>>1885
>Hitting the books is a meme
I remember when I was as foolish as you, but books are very useful. Books act as a compilation of knowledge for you to learn from. Of course not all books are good, but it can save you a lot of time over doing the research yourself and having to search through research papers you might not yet be able to fully understand yet.

Nanonymous No.1923 [D] >>1926

>wanting to invest time into tech
The point of /g/ to me has always been about how to avoid using technology as much as possible. BSD and Linux are good for this because they can only do boring things.

Nanonymous No.1926 [D]

>>1923
[ D ]