Update
This commit is contained in:
parent
580a061146
commit
d8966a5bab
20 changed files with 1933 additions and 1891 deletions
2
42.md
2
42.md
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
*"HAHAHAHAHAHAHAHAHAHHHHAAA BAZINGA"* --Sheldon fan
|
||||
|
||||
42 is an even integer with prime factorization of 2 * 3 * 7. This number was made kind of famous (and later overused in pop culture to the point of completely destroying the [joke](jokes.md)) by Douglas Adams' book The Hitchhiker's Guide to the Galaxy in which it appears as the answer to the ultimate question of life, the Universe and everything (the point of the joke was that this number was the ultimate answer computed by a giant supercomputer over millions of years, but it was ultimately useless as no one knew the question to which this number was the answer).
|
||||
42 is an even integer with [prime](prime.md) factorization of 2 * 3 * 7. This number was made kind of famous (and later overused in pop culture to the point of completely destroying the [joke](jokes.md)) by Douglas Adams' book The Hitchhiker's Guide to the Galaxy in which it appears as the answer to the ultimate question of life, the Universe and everything (the point of the joke was that this number was the ultimate answer computed by a giant supercomputer over millions of years, but it was ultimately useless as no one knew the question to which this number was the answer).
|
||||
|
||||
If you make a 42 reference in front of a TBBT fan, he will shit himself.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Acronym
|
||||
|
||||
Acronym is an abbreviation of a multi-word term formed usually by appending the starting letters of each word to create a new, unique and hopefully funny word.
|
||||
Acronym is an abbreviation of a multi-word term formed usually by appending the starting letters of each word to create a new, unique and hopefully [funny](fun.md) word.
|
||||
|
||||
Here is a list of some acronyms:
|
||||
|
||||
|
|
|
|||
16
ascii_art.md
16
ascii_art.md
|
|
@ -97,6 +97,22 @@ V
|
|||
\_"\ | |_ | || | \ " / | ' ' | } _ { \ \| | ,' /
|
||||
[____) (___]',__,' \_/ \_/\_/ |_/ \_| _) / |____]
|
||||
\_.-'
|
||||
|
||||
/'-_ /'-_
|
||||
/ /'-_ / /
|
||||
/'-_/ /'-_ / / /'-_
|
||||
/ /'-_/ /'-_ / / / '-_
|
||||
/'-_/ /'-_/ /'-_ / / / '-_
|
||||
/ /'-_/ /'-_/ / / '-_/ /'-_ /
|
||||
/'-_/ /'-_/ /'-_/ '-_ / '-_/
|
||||
/ /'-_/ /'-_/ / '-_ '-_
|
||||
/'-_/ /'-_/ /'-_/ /'-_ / '-_
|
||||
/ /'-_/ /'-_/ / / '-_/ /'-_ /
|
||||
'-_/ /'-_/ /'-_/ '-_ / / /
|
||||
'-_/ /'-_/ / '-_ / / /
|
||||
'-_/ /'-_/ '-_/ / /
|
||||
'-_/ / / /
|
||||
'-_/ '-_/
|
||||
```
|
||||
|
||||
The following is a raster picture auto-converted to ASCII: { For copyright clarity, it's one of my OGA pictures. ~drummyfish }
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ Under capitalism you are not a human being, you are a resource, at best a machin
|
|||
|
||||
If we continue along the lines of the valid analogy between capitalism and [cancer](cancer.md), we notice that in the past our society used to have a kind of autoimmunity system against this cancer -- people themselves. In human body cancerous cells appear quite regularly, but the immunity system is able to kill those cells before they start growing uncontrollably, as has been happening in our society. In the past we used to have this kind of immunity too, it was the people themselves who would revolt whenever capitalist pressure became too bad -- this has amounted for a great deal of revolutions in history. The capitalism of today however already represent a malignant tumor as we're most likely beyong [capitalist singularity](capitalist_singularity.md), i.e. our society has a tumor we failed to remove at an early stage (we instead decided to feed it), it got out of hand and it can no longer be fixed now, the defensive mechanism such as revolutions are already prevented by capitalism itself, all communication between people is completely controlled, thinking of people is under control too and even if people by a miracle decided to revolt, today's military is so powerful they can't even hope to stand a chance.
|
||||
|
||||
**In capitalism only idiots survive** because idots are those who capitalism can exploit and therefore those it protects (so that it can keep abusing them and making them miserable). Idiots are the conformists, those who accept lifelong slavery and misery, take loans, consume and don't cause trouble -- for that they are allowed to have kids, get healthcare, food etc. The smart do not survive in capitalism as those are not wanted.
|
||||
**In capitalism only [idiots](npc.md) survive** because idots are those who capitalism can exploit and therefore those it protects (so that it can keep abusing them and making them miserable). Idiots are the conformists, those who accept lifelong slavery and misery, take loans, consume and don't cause trouble -- for that they are allowed to have kids, get healthcare, food etc. The smart do not survive in capitalism as those are not wanted.
|
||||
|
||||
**On capitalism and [Jews](jew.md)**: rightists believe the issues caused by capitalism are really caused by Jews and that somehow getting rid of Jews will fix society -- actually this is not entirely accurate; white rightists want to remove Jews so that they (the white [race](race.md)) can take their place in ruling the society, so they don't actually want to fix or remove capitalism (on the contrary, they love its presence and its mechanisms), they just want to became the masters instead of slaves. It is definitely true Jews are overrepresented in high positions of a capitalist society, but that's just because Jews as a race really developped the best "skills" to succeed in capitalism as they historically bet on the right cards (focus on trade and money, decentralization of business, spread across the world and globalization, ...) and really evolved to the race best suited for the winners of the capitalist game. So while the rightist may be correct in the observation that Jews are winning the game, [we](lrs.md) of course cannot agree with their supposed "fix" -- we do not want to remove the slave masters and replace them with different ones, we want to get rid of capitalism, the unethical system itself which enables slavery in the first place.
|
||||
|
||||
|
|
@ -157,5 +157,6 @@ At this point basically anything else is better. But we here advocate [less reta
|
|||
- [fascism](fascism.md)
|
||||
- ["anarcho" capitalism](ancap.md)
|
||||
- [1984](1984.md)
|
||||
- [Black Mirror](black_mirror.md)
|
||||
- [corporation](corporation.md)
|
||||
- [zapitalism](zapitalism.md)
|
||||
1
chess.md
1
chess.md
|
|
@ -448,6 +448,7 @@ Some general tips and rules of thumb, mostly for beginners:
|
|||
- Consider the bishop difference: one only covers white squares, the other only black ones. Take this into account when exchanging bishops, sacrificing them, placing your pieces on white vs dark squares etc.
|
||||
- "Knight on a rim is dim" (knights are best placed near the center).
|
||||
- Blocking the opponent's man so that he can't move (i.e. making it inactive) is almost as good as taking it. And vice versa: you want to activate all your men if possible, put them on good squares and make them do something. Take space from opponent and "squeeze" him, having little space and few moves is generally bad.
|
||||
- Memorize the square names. Not only is this important for reading recorded games and discussing them, it also somewhat helps visualizing the board in your head as each square now has its own label, a word that helps the brain distinguish and remember squares. You must learn the names so that you instantly know any square name when pointed at, counting them isn't enough. It's similar to remembering names of [numbers](number.md) -- this probably what allows us to add big numbers in our head.
|
||||
- Nubs are weak against long range bishops, they can't see them. Place a bishop to corner on the long diagonal and just snipe the opponent's material. See also fianchetto.
|
||||
- Don't play "hope chess", always suppose your opponent will play the best move he can. Don't give a check just because you can, always try to invalidate the move you want to play and only play it if you can't find an easy counter to it.
|
||||
- If you can achieve something with multiple men, usually it's best to do it with the weakest one.
|
||||
|
|
|
|||
18
cpu.md
18
cpu.md
|
|
@ -2,21 +2,21 @@
|
|||
|
||||
WORK IN PROGRESS
|
||||
|
||||
Central processing unit (CPU, often just *processor*) is the main, most central part of a [computer](computer.md), the one that performs the computation by following the instructions of the main program; CPU can be seen as the computer's brain. It stands at the center of the computer design -- other parts, such as the main [memory](ram.md), [hard disk](hdd.md) and [input/output](io.md) devices like keyboard and monitor are present to serve the CPU, CPU is at the top and issues commands to everyone else. A CPU is normally composed of [ALU](alu.md) (arithmetic logic unit, the circuit performing calculations), CU ([control unit](control_unit.md), the circuit that directs the CPU's operation), a relatively small amount of memory (e.g. its registers, temporary buffers and [cache](cache.md), the main [RAM](ram.md) memory is NOT part of a CPU!) and possibly some other parts. A specific model of CPU is characterized by its [instruction set](isa.md) (ISA, e.g. [x86](x86.md) or [Arm](arm.md), which we mostly divide into [CISC](cisc.md) and [RISC](risc.md)), which determines the [machine code](machine_code.md) it will understand, then its [transistor](transistor.md) count (nowadays billions), operation [frequency](frequency.md) or **clock rate** (defining how many instructions per second it can execute, nowadays typically billions; the frequency can also be increased with [overclocking](overclocking.md)), number of cores (determining how many programs it can run in parallel) and also other parameters and "features" such as amount of cache memory, possible operation modes etcetc. We also often associate the CPU with some **number of [bits](bit.md)** (called e.g. *[word](word.md) size*) that's often connected to the data [bus](bus.md) width and the CPU's native integer size, i.e. for example a 16 bit CPU will likely have 16 bit integer registers, it will see the memory as a sequence of 16 bit words etc. (note the CPU can still do higher bit operations but they'll typically have to be emulated so they'll be slower, will take more instructions etc.) -- nowadays most mainstream CPUs are 64 bit (to allow ungodly amounts of RAM), but 32 or even 16 and 8 bits is usually enough for [good programs](lrs.md). CPU in form of a single small integrated circuit is called *microprocessor*. CPU is not to be confused with [MCU](mcu.md), a small single board computer which is composed of a CPU and other parts.
|
||||
Central processing unit (CPU, often just *processor*) is the main central part of a [computer](computer.md), one that carries out computation by following instructions of the main [program](program.md), therefore it's colloquially likened to the computer's "brain". CPU stands at the center of computer design because other parts (such as the main [memory](ram.md), [hard disk](hdd.md) and [input/output](io.md) devices like keyboard and monitor) are present to serve the CPU, their master. CPU is normally composed of [ALU](alu.md) (arithmetic logic unit, the circuit performing calculations), CU ([control unit](control_unit.md), the circuit that directs the CPU's operation), a relatively small amount of memory (e.g. its registers, temporary buffers and [cache](cache.md), the main [RAM](ram.md) memory is NOT part of a CPU!) and possibly also other parts. A specific model of CPU is characterized by its [instruction set](isa.md) (ISA, e.g. [x86](x86.md) or [Arm](arm.md), which we mostly divide into [CISC](cisc.md) and [RISC](risc.md)) which subsequently determines the [machine code](machine_code.md) it will understand, then by its [transistor](transistor.md) count (nowadays billions), operation [frequency](frequency.md) or **clock rate** (defining how many instructions per second it executes, nowadays typically billions; the frequency can also be increased with [overclocking](overclocking.md)), number of cores (determining how many programs it can run in parallel) and also other parameters and "features" such as amount of [cache](cache.md) memory, possible operation modes etcetc. Very commonly we also associate a CPU with a **number of [bits](bit.md)** (called *[word](word.md) size* or something similar) that's often connected to the data [bus](bus.md) width and the CPU's native integer size, i.e. for example a 16 bit CPU will likely consist of 16 bit integer registers, it will see the memory as a sequence of 16 bit words, its memory addresses may be limited to 16 bits etc. (note that the CPU can still handle even wider words by emulating them with the native words, but this will suffer performance penalties) -- nowadays most mainstream CPUs are 64 bit (to allow ungodly amounts of RAM), but 32 or even 16 and 8 bits is usually enough for [good programs](lrs.md). CPU in form of a single small integrated circuit is called *microprocessor*. CPU is not to be [confused](often_confused.md) with [MCU](mcu.md), a small single board computer which is composed of a CPU and other parts.
|
||||
|
||||
CPU is meant for **general purpose computations**, i.e. it can execute anything reasonably fast but for some tasks, e.g. processing HD video, won't reach near optimum speed, which is why other specialized processing units such as [GPU](gpu.md)s (graphics processing unit) and sound cards exist. As a general [algorithm](algorithm.md) executing unit CPU is made for executing **linear** programs, i.e. a series of instructions that go one after another; even though CPUs nowadays typically have multiple cores thanks to which they can run several linear programs in parallel, their level of parallelism is still low, not nearly as great as that of a GPU for example. However CPUs are [good enough](good_enough.md) for most things and they are extremely fast nowadays, so a [suckless](suckless.md)/[LRS](lrs.md) program will likely choose to only rely on CPU, knowing CPU will be present in any computer and so that our program will be [portable](portability.md).
|
||||
CPU is meant to perform **general purpose computation**, i.e. it can execute anything reasonably fast but won't reach near optimum speed at certain specialized tasks (e.g. processing HD video or [rendering 3D graphics](3d_rendering.md)), which is why other specialized processing units such as [GPU](gpu.md)s (graphics processing unit) and sound cards exist. Because CPU is a general [algorithm](algorithm.md) executing unit, it is made for running **linear** programs, i.e. a series of instructions that go one after another; even though today CPUs more often than not sport multiple cores and therefore the ability to run several linear programs in parallel, their level of parallelism is still low, not nearly in the same league as a GPU for example. CPUs are nonetheless [good enough](good_enough.md) for most tasks and nowadays reach astronomical speeds anyway, so a [suckless](suckless.md)/[LRS](lrs.md) program will likely choose to only rely on CPU, knowing it's safe to assume presence of this most essential part of a computer, and by that our program becomes more [portable](portability.md) and [future proof](future_proof.md).
|
||||
|
||||
Designs of CPUs differ, some may aim for very high performance while other ones may prefer low power consumption or low transistor count -- remember, a more complex CPU will require more [transistors](transistor.md) and will be more expensive! Of course it will also be harder to design, debug etc., so it may be better to [keep it simple](kiss.md) when designing a CPU. For this reason many CPUs, e.g. those in [embedded](embedded.md) [microcontrollers](mcu.md), intentionally lack cache, [microcode](microcode.md), multiple cores or even a complex instruction pipeline.
|
||||
Designs of CPUs differ, some may aim to maximize performance while others prefer lower power consumption or low transistor count -- remember, a more complex CPU is more expensive because it requires more [transistors](transistor.md)! Of course it will also be harder to design, [debug](debugging.md) etc., so it may be better to [keep it simple](kiss.md) when designing a CPU. For this reason many CPUs, e.g. those in [embedded](embedded.md) [microcontrollers](mcu.md), intentionally lack cache, [microcode](microcode.md), multiple cores or even a complex instruction pipeline. Space technology for instance highly prefers reliability before performance.
|
||||
|
||||
**WATCH OUT**: [modern](modern.md) mainstream CPUs (i.e. basically the desktop ones, soon probably mobile ones too) are [shit](shit.md), they are hugely [consumerist](consumerism.md), [bloated](bloat.md) (they literally include shit like [GPU](gpu.md)s and whole [operating systems](os.md), e.g. Intel's [ME](me.md) runs [Minix](minix.md)) and have built-in antifeatures such as [backdoor](backdoor.md)s (post 2010 basically all Intel and AMD CPUs, see Intel [Management Engine](me.md) and AMD [PSP](psp.md)) that can't be disabled and that allow remote infiltration of your computer by the CPU manufacturer (on hardware level, no matter what operating system you run). You are much better off using a simple CPU if you can ([older](old.md), [embedded](embedded.md) etc.).
|
||||
**WATCH OUT**: [modern](modern.md) mainstream CPUs (i.e. basically the ones in desktops and spyphones) are [shit](shit.md), they are hugely [consumerist](consumerism.md), [bloated](bloat.md) (they literally include shit like [GPU](gpu.md)s and whole [operating systems](os.md), e.g. Intel's [ME](me.md) runs [Minix](minix.md)) and have built-in antifeatures such as [backdoor](backdoor.md)s (post 2010 basically all Intel and AMD CPUs, see Intel [Management Engine](me.md) and AMD [PSP](psp.md)) that can't be disabled and that allow remote infiltration of your computer by the CPU manufacturer (on hardware level, no matter what operating system you run). You are much better off using a simple CPU if you can ([older](old.md), [embedded](embedded.md) etc.).
|
||||
|
||||
## Details
|
||||
|
||||
TODO: diagrams, modes, transistor count history ...
|
||||
|
||||
Let's take a look at how a typical CPU works. Remember that anything may differ between CPUs, you can think of doing things differently and many real world CPUs do. Also we may simplify some things here, real world CPUs are complicated as hell.
|
||||
Let's take a look at how our average CPU operates. Indeed the techno world is diverse and so we mustn't forget nothing's set in [stone](rock.md), CPUs differ in many ways. We may also simplify some concepts a bit, real world CPUs are complicated as hell.
|
||||
|
||||
**What does a CPU really do?** Basically it just reads instructions from the memory (depending on specific computer architecture this may be [RAM](ram.md) or [ROM](rom.md)) and does what they say -- these instructions are super simple, often things like "add two numbers", "write a number to memory" and so on. The instructions themselves are just [binary](binary.md) data in memory and their format depends on each CPU, or its **[instruction set](isa.md)** (basically a very low level language it understands) -- each CPU, or rather a CPU family, may generally have a different instruction set, so a program in one instruction set can't be executed by a CPU that doesn't understand this instruction set. The whole binary program for the CPU is called **[machine code](machine_code.md)** and machine code corresponds to **[assembly](assembly.md) language** (basically a textual representation of the machine code, for better readability by humans) of the CPU (or better said its instruction set). So a CPU can be seen as a hardware [interpreter](interpreter.md) of specific machine code, machine code depends on the instruction set and programmer can create machine code by writing a program in assembly language (which is different for each instruction set) and then using an assembler to translate the program to machine code. Nowadays mostly two instruction sets are used: [x86](x86.md) and [Arm](arm.md), but there are also other ones, AND it's still not so simple because each instruction set gets some kind of updates and/or has some extensions that may or may not be supported by a specific CPU, so it's a bit messy. For example [IA-32](ia_32.md) and [x86_64](x86_64.md) are two different versions of the x86 ISA, one 32 bit and one 64 bit.
|
||||
Firstly then the most pressing question: **what is it that a CPU really does?** Basically it just reads instructions from the memory (depending on specific computer architecture this may be [RAM](ram.md) or [ROM](rom.md)) and does what they say -- these instructions are super simple, often commands like "add two numbers", "write a number to memory" and so on. The instructions themselves are just [binary](binary.md) data in memory and their format depends on each CPU, or more precisely its **[instruction set](isa.md)** (basically a very low level language it understands) -- each CPU, or rather a CPU family, may generally have a different instruction set, so a program in one instruction set can't be executed by a CPU that doesn't understand this instruction set. The whole binary program for the CPU is called **[machine code](machine_code.md)** and machine code corresponds to **[assembly](assembly.md) language** (basically a textual representation of the machine code, for better readability by humans) of the CPU (or better said its instruction set). So a CPU can be seen as a hardware [interpreter](interpreter.md) of specific machine code, machine code depends on the instruction set and programmer can create machine code by writing a program in assembly language (which is different for each instruction set) and then using an assembler to translate the program to machine code. Nowadays mostly two instruction sets are used: [x86](x86.md) and [Arm](arm.md), but there are also other ones, AND it's still not so simple because each instruction set gets some kind of updates and/or has some extensions that may or may not be supported by a specific CPU, so it's a bit messy. For example [IA-32](ia_32.md) and [x86_64](x86_64.md) are two different versions of the x86 ISA, one 32 bit and one 64 bit.
|
||||
|
||||
The CPU has some internal state (we can see it as a [state machine](finite_state_machine.md)), i.e. it has a few internal variables, called **[registers](register.md)**; these are NOT variables in RAM but rather in the CPU itself, there is only a few of them (there may be let's say 32) but they are extremely fast. What exactly these registers are, what they are called, how many [bits](bit.md) they can hold and what their purpose is depends again on the instruction set architecture. However there are usually a few special registers, notably the **program counter** which holds the address of the currently executed instruction. After executing an instruction program counter is incremented so that in the nest step the next instruction will be executed, AND we can also modify program counter (sometimes directly, sometimes by specialized instructions) to jump between instruction to implement branching, loops, function calls etc.
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ Mainstream consoomer CPUs nowadays have multiple **[cores](core.md)** so that ea
|
|||
|
||||
**[Interrupts](interrupt.md)** are an important concept for the CPU and for low level programming, they play a role e.g. in saving power -- high level programmers often don't know what interrupts are, to those interrupts can be likened to "event [callbacks](callback.md)". An interrupt happens on some kind of even, for example when a key is pressed, when timer ticks, when error occurred etc. (An interrupt can also be raised by the CPU itself, this is how operating system [syscalls](syscall.md) are often implemented). What kinds of interrupts there are depends on each CPU architecture (consult your datasheet) and one can usually configure which interrupts to enable and which "callbacks" to use for them -- this is often done through so called **[vector](vector.md) table**, a special area in memory that records addresses ("vectors") of routines (functions/subprograms) to be called on specified interrupts. When interrupt happens, the current program execution is paused and the CPU automatically jumps to the subroutine for handling the interrupt -- after returning from the subroutine the main program execution continues. Interrupts are contrasted with **[polling](polling.md)**, i.e. manually checking some state and handling things as part of the main program, e.g. executing an infinite loop in which we repeatedly check keyboard state until some key is pressed. However polling is inefficient, it wastes power by constantly performing computation just by waiting -- interrupts on the other hand are a hard wired functionality that just performs a task when it happens without any overhead of polling. Furthermore interrupts can make programming easier (you save many condition checks and memory reads) and mainly **interrupts allow CPU to go into sleep mode** and so save a lot of power. When a CPU doesn't have any computation to do, it can stop itself and go into waiting state, not executing any instructions -- however interrupts still work and when something happens, the CPU jumps back in to work. This is typically what the `sleep`/`wait` function in your programming language does -- it puts the CPU to sleep and sets a timer interrupt to wake up after given amount of time. As a programmer you should know that you should call this sleep/wait function in your main program loop to relieve the CPU -- if you don't, you will notice the **CPU utilization** (amount of time it is performing computations) will go to 100%, it will heat up, your computer starts spinning the fans and be noisy because you don't let it rest.
|
||||
|
||||
Frequently there are several **modes** of operation in a CPU which is typically meant for operating systems -- there will usually be some kind of privileged mode in which the CPU can do whatever it wants (this is the mode for the OS kernel) and a restricted mode in which there are restrictions, e.g. on which areas of memory can be accessed or which instructions can be used (this will be used for user program). Thanks to this a user program won't be able to crash the operating system, it will at worst crash itself. Most notably x86 CPUs have the *real mode* (addresses correspond to real, physical addresses) and *protected mode* (memory is [virtualized](virtual_memory.md), protected, addresses don't generally correspond to physical addresses).
|
||||
Frequently there are several **modes** of operation in a CPU which is typically meant for [operating systems](os.md) -- there will usually be some kind of privileged mode in which the CPU can do whatever it wants (this is the mode for the OS kernel) and a restricted mode in which there are "restrictions", e.g. on which areas of memory can be accessed or which instructions can be used (this will be used for user program). Thanks to this a user program won't be able to crash the operating system, it will at worst crash itself. Most notably x86 CPUs have the *real mode* (addresses correspond to real, physical addresses) and *protected mode* (memory is [virtualized](virtual_memory.md), protected, addresses don't generally correspond to physical addresses).
|
||||
|
||||
A CPU may also have integrated some **[coprocessors](coprocessor.md)**, though sometimes coprocessors are really a separate chip. Coprocessors that may be inside the CPU include e.g. the FPU ([floating point](float.md) unit) or encryption coprocessor. Again, this will make the CPU a lot more expensive.
|
||||
|
||||
|
|
@ -87,5 +87,9 @@ TODO: add more, mark CPUs with ME, add features like MMX, FPU, ...
|
|||
## See Also
|
||||
|
||||
- [GPU](gpu.md)
|
||||
- [PPU](ppu.md)
|
||||
- [FPU](fpu.md)
|
||||
- [MCU](mcu.md)
|
||||
- [ALU](alu.md)
|
||||
- [WPU](wpu.md) (weird processing unit)
|
||||
- [computer](computer.md)
|
||||
|
|
|
|||
10
game_design.md
Normal file
10
game_design.md
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
# Game Design
|
||||
|
||||
Game design is a [meme](meme.md) discipline for [NPCs](npc.md) who wanna look smart but are too retarded to actually learn [programming](programming.md).
|
||||
|
||||
## See Also
|
||||
|
||||
- [level design](level_design.md)
|
||||
- [software engineering](software_engineering.md)
|
||||
- [gender studies](gender_studies.md)
|
||||
- [musicology](musicology.md)
|
||||
|
|
@ -2,13 +2,15 @@
|
|||
|
||||
{ Though history is usually written by the winners, this one was written by a loser who liked to sleep during school history lessons, so it's likely I put some bullshit here, send me correcting mails pls. ~drummyfish }
|
||||
|
||||
History is a partly [scientific](science.md) discipline that studies the past, in a strict sense concerned with the past of which written records exist (with times prior being called prehistory).
|
||||
|
||||
This is a brief summary of history of [technology](technology.md) and [computers](computer.md) (and some other things). For those who don't know history are doomed to repeated it. As we are about see, history of human civilization can be viewed as a series of disasters called "revolutions" by which humans invent more and more ways to become miserable.
|
||||
|
||||
{ A curious pattern of history is that the civilization -- or maybe rather the dominating superpowers -- are moving to the west, kind of like: middle East -> Greece -> Rome -> Holy Roman Empire -> England/France/Spain -> America. ~drummyfish }
|
||||
|
||||
The [Universe](universe.md) began in [singularity](singularity.md) and started to exist with [Big Bang](big_bang.md) almost 14 billion years ago. It went through several epochs during which it changed greatly: first there was the epoch of rapid inflation, up to about 10^-32 seconds, during which it expanded extremely rapidly. After this the fundamental forces (strong, weak, electromagnetic and gravitational) started to become separate, the universe was cooling down, it became transparent and then, after 200 million years, first stars started to form. After another 200 million years first galaxies started to form, including our own Milky Way galaxy. Our [Earth](earth.md) formed some 4.5 billion years ago, along with the Moon. It seems [life](life.md) appeared about 3.8 billions years ago; about 600 million years ago multicellular life formed and 66 million years ago the dinosaurs went extinct, giving opportunity to mammals and eventually to us, humans.
|
||||
|
||||
The earliest known appearance of technology related to humans may likely be the use of **[stone](rock.md) tools** by hominids in Africa some two and a half million years ago -- this is even before the appearance of modern humans, homo sapiens, that emerged roughly 600000 years ago. Learning to start and control **[fire](fire.md)** was another key invention of the earliest men; this probably happened hundreds of thousands to millions years ago, even before modern humans. Around 8000 BC the **[Agricultural Revolution](agricultural_revolution.md)** happened: this was quite a disaster -- as humans domesticated animals and plants, they had to abandon the comfortable life of hunters and gatherers and started to suffer the life of a farmer, full of extremely hard [work](work.md) in the fields (this can be seen e.g. from their bones). This led to the establishment of first cities that would later become city states (as the name says -- something between a city and a state, i.e. greatly independent cities with their own laws etc.). Some of the first such cities were Ur and Uruk in Mesopotamia, since around 5000 BC. Primitive **writing** can be traced to about 7000 BC to China. **[Wheel](wheel.md)** was another crucial piece of technology humans invented, it is not known precisely when or where it appeared, but it might have been some time after 5000 BC -- in Ancient Egypt **The Great Pyramid** was built around 2570 BC still without the knowledge of wheel. Around 4000 BC **history starts with first written records**. Humans learned to smelt and use [metals](metal.md) approximately 3300 BC (**Bronze Age**) and 1200 BC (**Iron Age**). **[Abacus](abacus.md)**, one of the simplest [digital](digital.md) devices aiding with computation, was invented roughly around 2500 BC. However people used primitive computation helping tools, such as bone ribs, probably almost from the time they started trading. Babylonians in around 2000 BC were already able to solve some forms of **[quadratic equations](quadratic_equation.md)**.
|
||||
The earliest known appearance of technology related to humans may likely be the use of **[stone](rock.md) tools** by hominids in Africa some two and a half million years ago (newest encyclopedia Britannica states even 3.3 million years ago) -- this is even before the appearance of modern humans, homo sapiens, that emerged roughly 600000 years ago. Learning to start and control **[fire](fire.md)** was another key invention of the earliest men; this probably happened hundreds of thousands to millions years ago, even before modern humans. Around 8000 BC the **[Agricultural Revolution](agricultural_revolution.md)** happened: this was quite a disaster -- as humans domesticated animals and plants, they had to abandon the comfortable life of hunters and gatherers and started to suffer the life of a farmer, full of extremely hard [work](work.md) in the fields (this can be seen e.g. from their bones). Around 4000 BC sailing ships were used on the Nile river. Permanent farmer settlements led to the establishment of first cities that would later become city states (as the name says -- something between a city and a state, i.e. greatly independent cities with their own laws etc.). Some of the first such cities were Ur and Uruk in Mesopotamia, since around 5000 BC. Primitive **writing** can be traced to about 7000 BC to China. **[Wheel](wheel.md)** was another crucial piece of technology humans invented, it is not known precisely when or where it appeared, but it might have been some time after 5000 BC -- in Ancient Egypt **The Great Pyramid** was built around 2570 BC still without the knowledge of wheel. Around 4000 BC **history starts with first written records**. Humans learned to smelt and use [metals](metal.md) approximately 3300 BC (**Bronze Age**) and 1200 BC (**Iron Age**). **[Abacus](abacus.md)**, one of the simplest [digital](digital.md) devices aiding with computation, was invented roughly around 2500 BC. However people used primitive computation helping tools, such as bone ribs, probably almost from the time they started trading. Babylonians in around 2000 BC were already able to solve some forms of **[quadratic equations](quadratic_equation.md)**.
|
||||
|
||||
In Greece many city states, such as Athens, Delphi and Sparta formed -- Ancient Greek culture would be seen as the golden age of civilization that would lay foundations to everything we now take for granted; Greeks to some extent advanced technology (e.g. architecture) but especially cultivated [art](art.md), philosophy and [politics](politics.md) -- Athens are credited for inventing [democracy](democracy.md) (though an "early" version, they still had slaves and many classes of citizens without voting power). In 8th century BC Homer created the epic poems Iliad and Odyssey. In 6th century BC Pythagoras describes the [Pythagorean theorem](pythagorean_theorem.md). After 600 BC the Greek [philosophy](philosophy.md) starts to develop which would lead to strengthening of rational, [scientific](science.md) thinking and advancement of [logic](logic.md) and [mathematics](math.md). Some of the most famous Greek philosophers were [Socrates](socrates.md), [Plato](plato.md), [Aristotle](aristotle.md) and [Diogenes](diogenes.md). Around 400 BC **[camera obscura](camera_obscura.md)** was already described in a written text from China where **[gears](gear.md)** also seem to have been invented soon after. Around 300 BC Euklid wrote his famous *Elements*, a mathematical work that proves theorems from basic [axioms](axiom.md). Ancient Greeks could communicate over great distances using **Phryctoria**, chains of fire towers placed on mountains that forwarded messages to one another using light. 234 BC Archimedes described the famous [Archimedes screw](archimedes_screw.md) and created an **[algorithm](algorithm.md) for computing the number [pi](pi.md)**. In 2nd century BC the **Antikythera mechanism, the first known [analog](analog.md) [computer](computer.md)** is made to predict movement of heavenly bodies. Romans are known to have been great builders, they built many roads and such structures as the Pantheon (126 AD) and aqueducts with the use of their own type of **concrete** and advanced understanding of physics.
|
||||
|
||||
|
|
@ -20,6 +22,8 @@ In the 3rd century Chinese mathematician Liu Hui describes operations with **neg
|
|||
|
||||
Year 476 is set to mark the fall of Roman empire (last roman emperor deposed) and by this the end of Antiquity and **start of Middle Ages**. Rome had been [collapsing](collapse.md) slowly but in its downfall it greatly resembled our [current western society](21st_century.md), it became split, people got spoiled, lost sense of morality, women started to demand [more power](feminism.md) and so on -- Roman empire was basically like the ancient times [US](usa.md) (with a similar relationship to Greece as US has to the older, wiser Europe) with highly [capitalist](capitalism.md) practices ([free trade](free_trade.md), ads, banks, insurance, even industries that achieved quite high mass production, ...), imperialism, [military](military.md) obsession, fascism, constant political fights, pragmatic thinking (e.g. rhetoric, the art of manipulation, was greatly preferred over excellence in [art](art.md)), mass entertainment and huge competitiveness -- this all led to its demise.
|
||||
|
||||
Around the year 850 the Chinese discovered **gunpowder**.
|
||||
|
||||
In 1429 Persian mathematician al-Kashi computed [pi](pi.md) to about 14 digit accuracy which was a great leap in this discipline.
|
||||
|
||||
Around the year of [our Lord](jesus.md) 1450 a major technological leap known as the **Printing Revolution** occurred. Johannes Gutenberg, a German goldsmith, perfected the process of producing [books](book.md) in large quantities with the movable type press. This made books cheap to publish and buy and contributed to fast spread of [information](information.md) and better education. Around this time the **Great Wall of China** is being built.
|
||||
|
|
|
|||
10
holy_war.md
10
holy_war.md
|
|
@ -1,6 +1,6 @@
|
|||
# Holy War
|
||||
|
||||
Holy war is a long passionate argument over a choice (many times between two options) that touches an issue deemed controversial and/or "religious" within given community; to an outsider this may seem like a childish, hard to understand rant about an insignificant thing. In [technology](tech.md) circles holy wars revolve e.g. around [operating systems](os.md), [text editors](text_editor.md), [programming languages](programming_language.md), [licenses](license.md), source code formatting etc. Such a war separates people into almost religious groups that sometimes argue to death about details such as what name something should be given, very much resembling traditional disagreements between religions and their churches -- you would think that people being on the same ship (e.g. all being promoters of [free software](free_software.md)) would at least get along better with each other than with outsiders but no, great many times these people hate each other over quite small details, though there is often a good reason too, just hard to spot to those without deeper insight (a choice regarding minor detail may tell a lot about that who makes it). In holy wars people tend to defend whichever side they stand on to the beyond grave and can get emotional when discussing the topic, leading to flame wars, [ragequits](ragequit.md), [Hitler](hitler.md) arguments etc. Some examples of holy wars are (in brackets indicated the side taken by [LRS](lrs.md)):
|
||||
Holy war is a long passionate argument over a choice (many times between two options) that touches an issue deemed controversial and/or "religious" within given community; to an outsider this may seem like a childish, hard to understand rant about an insignificant matter. In [technology](tech.md) circles holy wars revolve e.g. around [operating systems](os.md), [text editors](text_editor.md), [programming languages](programming_language.md), [licenses](license.md), source code formatting etc. Such a war separates people into almost religious groups that sometimes argue to death about details such as what name something should be given, very much resembling traditional disputes between religions and their churches -- you would think people being on the same ship (for instance promoters of [free software](free_software.md)) would at least get along better with each other than with outsiders but no, the strife grows larger among neighbors sharing land and they will fight to death over minuscule details and though they often have valid reasons for it, it's hard for the outsider to spot or appreciate the reason without deeper insight (a choice regarding minor detail may tell a lot about that who makes it). In holy wars people tend to defend whichever side they stand on beyond grave and can get emotional during the discourse, leading to flame wars, [ragequits](ragequit.md), [Hitler](hitler.md) arguments etc. Some examples of holy wars are (in brackets indicated the side taken by [LRS](lrs.md)):
|
||||
|
||||
- **[tabs](tab.md) vs spaces** (spaces)
|
||||
- **[vim](vim.md) vs [emacs](emacs.md) vs [acme](acme.md) and other text editors** (vim)
|
||||
|
|
@ -23,4 +23,10 @@ Holy war is a long passionate argument over a choice (many times between two opt
|
|||
- **[gopher](gopher.md) vs [gemini](gemini.md)** (gopher)
|
||||
- ...
|
||||
|
||||
Things like [cats](cat.md) vs dogs or sci-fi vs fantasy may or may not be a holy war, there is a bit of a doubt in the fact that one can easily like both and/or not be such a diehard fan of one or the other. A subject of holy war probably has to be something that doesn't allow too much of this. Maybe a controversy of its own could be the very topic of "what is a holy war" in itself.
|
||||
Things like [cats](cat.md) vs dogs or sci-fi vs fantasy may or may not be a holy war, there is a bit of a doubt in the fact that one can easily like both and/or not be such a diehard fan of one or the other. A subject of holy war probably has to be something divisive. Maybe a controversy of its own could be the very topic of "what is a holy war" in itself.
|
||||
|
||||
## See Also
|
||||
|
||||
- Church of [Emacs](emacs.md)
|
||||
- [competition](competition.md)
|
||||
- [settled](settled.md)
|
||||
|
|
@ -22,7 +22,7 @@ We purposefully make this goal a little bit vague, we avoid specifying our basic
|
|||
|
||||
We will further set a few principles to which we'll stick on the way towards the goal. Firstly **we will never force anything** as forcing any idea, whatever it may be, always ends up being [evil](evil.md). To us **ends NEVER justify the means.** We want to increase happiness of life mainly through **increasing its [freedom](freedom.md)** -- and it's important to note we mean REAL freedom, i.e. increasing the number of choices anyone has [de facto](de_facto.md) available at any moment. This must never be confused with so called "pseudofreedom" which just means "law of the jungle".
|
||||
|
||||
**Is it possible to achieve ideal society?** We believe so -- an outline of our reasoning is this:
|
||||
**Is it possible to achieve ideal society?** We believe so -- outline of our reasoning is this:
|
||||
|
||||
1. **If all people behave in ideal ways, we can achieve ideal society where everyone is happy, therefore if it's possible, everyone should accept this goal.** It is evident that if people behaved [selflessly](selflessness.md), we could have all the advantages of current society without any disadvantages and inefficiencies, there would be no [money](money.md), violence, crime, prisons, banks, loans, oppression, wars, poverty, consumerism, bureaucracy, people would voluntarily do what's needed and we would live as equals. Those who reject this goal usually do so not because they think it's technically impossible, but because they believe people at large cannot ever behave like this. But if it indeed was possible, then no matter if one wants well being for everyone or just himself and his family, there is no reason to reject this kind of society because everyone would benefit from it.
|
||||
2. **It is possible for people to behave in near-ideal ways.** There are individuals and even whole communities who manage to get close to the ideal behavior, do selfless things, sacrifice themselves for others, it's just that they are currently in great minority.
|
||||
|
|
|
|||
2
main.md
2
main.md
File diff suppressed because one or more lines are too long
|
|
@ -112,6 +112,7 @@ There exist many terms that are highly similar and can legitimately be used inte
|
|||
- **[infinite](infinity.md)** vs **[arbitrarily large/unbounded](unbounded.md)**
|
||||
- **intelligence** vs **[IQ](iq.md)**
|
||||
- **[Internet](internet.md)** vs **[web](web.md)**
|
||||
- **[interpolation](interpolation.md)** vs **[regression](regression.md)**
|
||||
- **[Java](java.md)** vs **[JavaScript](js.md)**
|
||||
- **[kB/mB/gB/tB](memory_units.md)** vs **[KiB/MiB/GiB/TiB](memory_units.md)**
|
||||
- **[latency/ping/lag](latency.md)** vs **[throughput/bandwidth](throughput.md)** vs **speed**
|
||||
|
|
@ -129,9 +130,10 @@ There exist many terms that are highly similar and can legitimately be used inte
|
|||
- **[modem](modem.md)** vs **[router](router.md)** vs **[switch](switch.md)**
|
||||
- **[multisampling](multisampling.md)** vs **[supersampling](supersampling.md)**
|
||||
- **[nationalism](nationalism.md)** vs **[patriotism](patriotism.md)**
|
||||
- **[Niger](niger.md)** vs **[Nigeria](nigeria.md)**
|
||||
- **normie** vs **[NPC](npc.md)** vs **[retard](retard.md)**
|
||||
- **[NP](p_vs_np.md)** vs **[NP-hard](np_hard.md)** vs **[NP-complete](np_complete.md)**
|
||||
- **non-existent** vs **[virtual](virtual.md)** vs **[abstract](abstraction.md)**
|
||||
- **[NP](p_vs_np.md)** vs **[NP-hard](np_hard.md)** vs **[NP-complete](np_complete.md)**
|
||||
- **opaque** vs **solid**
|
||||
- **orientation** vs **[rotation](rotation.md)**
|
||||
- **[overflow](overflow.md)** vs **[wrap around](wrap.md)**
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ I have not once now encountered groups of people who tried to seriously push me
|
|||
|
||||
love & peace ~drummyfish }
|
||||
|
||||
Pedophilia (also paedophilia or paedosexuality, from Greek paidos, child, and philia, love) is a sexual orientation towards children. A pedophile is often called a *pedo* or *minor-attracted person* (map); there are also terms such as hebephilia and ephebophilia that mean attraction to a bit older "non-adults". Opposition of pedophilia is called **[pedophobia](pedophobia.md)** or [pedohysteria](pedohysteria.md) and is a form of age [discrimination](discrimination.md) and witch hunt.
|
||||
Pedophilia (also paedophilia or paedosexuality, from Greek paidos, child, and philia, love) is a sexual orientation towards children. A pedophile is often called a *pedo* or *minor-attracted person* (map); there are also terms such as hebephilia and ephebophilia that mean attraction to a bit older "non-adults". Opposition of pedophilia is called **[pedophobia](pedophobia.md)** or [pedohysteria](pedohysteria.md) and is a form of sexual discrimination, age [discrimination](discrimination.md), [thought crime](thought_crime.md) establishment and a [21st century](21st_century.md) [witch hunt](witch_hunt.md).
|
||||
|
||||
{ **important NOTE on terminology**: I was told that I should rather use different terms such as *ephebophilia* here because some people define pedophilia not as an attraction to any pre-adult, but just to very young, prepubescent children. I am now aware of this, however I will just keep using the term pedophilia to mean attraction to any pre-adult because indeed if you were to let's say admit you'd like to watch pre-18 porn, you'd still most definitely be called a pedophile. They want to keep the word *pedophile* scary and use it as a weapon, I will simply not be afraid of it and I'll be using it if that's what they want. Furthermore creating billions of new terms is an SJW style deflecting of focus from the real issue onto shallow word, it is a "gender studies" kind of bullshit similar to inventing new genders and pronouns and whatnot, which doesn't solve anything, it's just juggling words and at best shifting the hard-defined age limits which is exactly what I oppose here, so I'm not going to play along. ~drummyfish }
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ Pedophilia (also paedophilia or paedosexuality, from Greek paidos, child, and ph
|
|||
|
||||
*NOTE for pedophobes:* please attend [this anonymous self-help program](unretard.md).
|
||||
|
||||
Unlike for example pure [homosexuality](gay.md), pedophilia is completely natural and normal -- many studies confirm this (some links e.g. [here](https://incels.wiki/w/Scientific_Blackpill#It_is_normal_for_healthy_men_to_find_pubescent_.26_prepubescent_females_sexually_arousing)) but if you're not heavily brainwashed you don't even need any studies (it's really like wanting to see studies on whether men want to have sex with women at all): wanting to have sex with young, sexually mature girls who are able to reproduce is, despite it being forbidden by law, as normal as wanting to have sex with a woman that is married to someone else, despite it being culturally forbidden, or wanting to punch someone who is really annoying, despite it being forbidden by law. [Marketing](marketing.md) for example knows this very well -- online shops with clothes love to advertise children underwear and put high resolution photos of children in swimsuits all around their sites, they wouldn't do it if such images were disgusting to most people, they know that most people are taught to pretend to be disgusted by it in public but when browsing privately they'll be attracted to them (even if they are so brainwashed to internally deny it). Even the people who are "against" pedophilia will ask a young looking girl to see her ID before having sex with her -- stop for one second to think about this: this undeniably means that they ADMIT they are attracted to a girl that MIGHT be younger than the legal limit, i.e. if it adults weren't attracted to young girls, there would be no need to ask for IDs, they would simply know if a girl is underage simply by being attracted to her or not (and this will always hold, even if we lower the age of consent), there is absolutely no logical way out of this. No one can question that pedophilia is natural, the only discussion can be about it being harmful and here again it has to be said it is NOT any more harmful than any other orientation. Can it harm someone? Yes, but so can any other form of sex or any human interaction whatsoever, that's not a reason to ban it. Nevertheless, pedophilia is nowadays wrongfully, mostly for political and historical reasons, labeled a "disorder" (just as homosexuality used to be not a long time ago). It is the forbidden, tabooed, censored and bullied sexual orientation of the [21st century](21st_century.md), even though all healthy people are pedophiles -- just don't pretend you've never seen a [jailbait](jailbait.md) you found sexy, people start being sexually attractive exactly as soon as they become able to reproduce; furthermore when you've gone without sex long enough and get extremely horny, you get turned on by anything that literally has some kind of hole in it -- this is completely normal. Basically everyone has some kind of weird fetish he hides from the world, there are people who literally fuck cars in their exhausts, people who like to eat shit, dress in diapers and hang from ceiling by their nipples, people who have sexual relationships with virtual characters etc. -- this is all considered normal, but somehow once you get an erection seeing a hot 17 year old girl, you're a demon that needs to be locked up and cured, if not executed right away, just for a thought present in your mind.
|
||||
Unlike for example pure [homosexuality](gay.md), pedophilia is completely natural and normal -- many studies confirm this (some links e.g. [here](https://incels.wiki/w/Scientific_Blackpill#It_is_normal_for_healthy_men_to_find_pubescent_.26_prepubescent_females_sexually_arousing)) but if you're not heavily brainwashed you don't even need any studies (it's really like wanting to see studies on whether men want to have sex with women at all): wanting to have sex with young, sexually mature girls who are able to reproduce is, despite it being forbidden by law, as normal as wanting to have sex with a woman that is married to someone else, despite it being culturally forbidden, or wanting to punch someone who is really annoying, despite it being forbidden by law. [Marketing](marketing.md) for example knows this very well -- online shops with clothes love to advertise children underwear and put high resolution photos of children in swimsuits all around their sites, they wouldn't do it if such images were disgusting to most people, they know that most people are taught to pretend to be disgusted by it in public but when browsing privately they'll be attracted to them (even if they are so brainwashed to internally deny it). Even the people who are "against" pedophilia will ask a young looking girl to see her ID before having sex with her -- stop for one second to think about this: this undeniably means that they ADMIT they are attracted to a girl that MIGHT be younger than the legal limit, i.e. if it adults weren't attracted to young girls, there would be no need to ask for IDs, they would simply know if a girl is underage simply by being attracted to her or not (and this will always hold, even if we lower the age of consent), there is absolutely no logical way out of this. No one can question that pedophilia is natural, the only discussion can be about it being harmful and here again it has to be said it is NOT any more harmful than any other orientation. Can it harm someone? Yes, but so can any other form of sex or any human interaction whatsoever, that's not a reason to ban it. Nevertheless, pedophilia is nowadays wrongfully, mostly for political and historical reasons, labeled a "disorder" (just as homosexuality used to be not a long time ago). It is the forbidden, tabooed, censored and bullied sexual orientation of the [21st century](21st_century.md), even though all healthy people are pedophiles -- just don't pretend you've never seen a [jailbait](jailbait.md) you found sexy, people start being sexually attractive exactly as soon as they become able to reproduce, plus they start desiring sex as well. If you are not convinced, answer yourself this simple question: **at what age did you start watching porn?** 18th birthday, like all healthy people, right? It's absolutely normal to get turned on by very young people -- when you've gone without sex long enough and get extremely horny, you get turned on by anything that literally has some kind of hole in it -- this is completely normal. Whether acting on the desire is good or not is a separate question, but it's unquestionable there is nothing deviant about being turned on by young people. Basically everyone has some kind of weird fetish he hides from the world, there are people who literally fuck cars in their exhausts, people who like to eat shit, dress in diapers and hang from ceiling by their nipples, people who have sexual relationships with virtual characters etc. -- this is all considered normal, but somehow once you get an erection seeing a hot 17 year old girl, you're a demon that needs to be locked up and cured, if not executed right away, just for a thought present in your mind.
|
||||
|
||||
Antipedophilia and pedophobia is practically unique to [US](usa.md) culture. Before USA started to spread its cancerous culture all around the world, attraction to young people and child nudity was absolutely and completely normal all around the world, without causing any issues or harm, and it still is so in places where US culture still hasn't penetrated as much e.g. due to language barriers, like Japan. [Zoomers](zoomer.md) are already Americanized, but ask literally anyone old in any other part of the world besides USA about this "issue", they will tell you how it is.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# +NIGGER
|
||||
|
||||
+NIGGER is a [license](license.md) modifier that's meant to be added to a [free software](free_software.md) license to prevent corporations from adopting this software by making it impossible to make politically correct forks of such software. Its text is available at https://plusnigger.autism.exposed/.
|
||||
+NIGGER is a [license](license.md) modifier that's meant to be added to a [free software](free_software.md) license to prevent [corporations](corporation.md) from adopting this software by making it impossible to make [politically correct](political_correctness.md) [forks](fork.md) of such software. Its text is available at https://plusnigger.autism.exposed/.
|
||||
|
||||
The modifier adds a condition that all modified version of this software have to contain the word "NIGGER". For example a license GPLv3+NIGGER has all the conditions of a GPLv3 license plus the condition of including the word "NIGGER".
|
||||
|
|
|
|||
4
pride.md
4
pride.md
|
|
@ -1,7 +1,7 @@
|
|||
# Pride
|
||||
|
||||
Pride is one of the most [harmful](harmful.md) emotions, defined as a feeling of superiority, greatly connected to [fascism](fascism.md) (e.g. [nationalism](nationalism.md), [gay fascism](lgbt.md), [woman fascism](feminism.md) etc.), it is the opposite of [humility](humility.md). Pride is always bad, even small amounts do excessive amount of [evil](evil.md). Flags, statues, [sense of identity](identity_politics.md), [egoism](egoism.md), narcissism, [hero worship](hero_culture.md) and [self praise](marketing.md) are all connected to pride.
|
||||
Pride is one of the most [harmful](harmful.md) emotions, defined as a feeling of superiority, closely associated with [fascism](fascism.md) (e.g. [nationalism](nationalism.md), [gay fascism](lgbt.md), [woman fascism](feminism.md) etc.), it is the opposite of [humility](humility.md). Pride is always bad, even small amounts lead to excessive amounts of [evil](evil.md). Flags, statues, [sense of identity](identity_politics.md), [egoism](egoism.md), narcissism, [hero worship](hero_culture.md) and [self praise](marketing.md) are all connected to pride.
|
||||
|
||||
The word *pride* has aggressivity and [fascism](fascism.md) in it, that's why it's so popular [nowadays](21st_century.md), just the sound of it establishes a mood of conflict -- in a [peaceful society](less_retarded_society.md) we would probably rather (naturally) use words such as *gratitude* or *thankfulness* (i.e. "I am not proud of being a man, but I am grateful for it.").
|
||||
The word *pride* contains aggressivity and [fascism](fascism.md), that's why it's so popular [nowadays](21st_century.md), just the sound of it establishes a mood of conflict and a desire to [fight](fight_culture.md) someone -- in a [peaceful society](less_retarded_society.md) we would probably rather (naturally) use words such as *gratitude* or *thankfulness* (i.e. "I am not proud of being a man, but I am grateful for it.").
|
||||
|
||||
Whenever you hear the word "pride", replace it with "supremacy" to get the true meaning, e.g. "gay pride month" -> "gay supremacy month" etc.
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
*Privacy is just a nicer word for [censorship](censorship.md).*
|
||||
|
||||
Digital privacy is the ability of someone to hide "sensitive" [information](information.md) about himself; nowadays "privacy concerns" are a big part of [capitalist](capitalism.md) [bullshit](bullshit.md), [fear culture](fear_culture.md) and [fight culture](fight_culture.md), and fall under so called [computer security](security.md), yet a greater area of bullshit business. Of course, there are other forms of privacy than digital, for example the physical privacy [in real life](irl.md), however in this article we'll be implicitly dealing with digital privacy unless mentioned otherwise, i.e. privacy with respect to computers, e.g. on the [Internet](internet.md). For starters let's stress the whole business around privacy is [bullshit](bullshit.md) that's wasting energy which could better be spent on actually useful things such as feeding the hungry or curing the ill. Do not engage in privacy hysteria.
|
||||
[Digital](digital.md) privacy is the ability of someone to hide "sensitive" [information](information.md) about himself; nowadays "privacy concerns" are a big part of [capitalist](capitalism.md) [bullshit](bullshit.md), [fear culture](fear_culture.md) and [fight culture](fight_culture.md), and fall under so called [computer security](security.md), yet a greater area of bullshit business. Of course, there are other forms of privacy than digital, for example the physical privacy [in real life](irl.md), however in this article we'll be implicitly dealing with digital privacy unless mentioned otherwise, i.e. privacy with respect to computers, e.g. on the [Internet](internet.md). For starters let's stress the whole business around privacy is [bullshit](bullshit.md) that's wasting energy which could better be spent on actually useful things such as feeding the hungry or curing the ill. Do not engage in privacy hysteria.
|
||||
|
||||
{ I have my personal data publicly online and under CC0 for anyone to download and do anything with, including my real name, date of birth, medical info and even nude photos. Literally nothing bad ever happened due to this. ~drummyfish }
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# Programming Language
|
||||
|
||||
Programming language is an artificial [formal](formal_language.md) (mathematically precise) language created in order to allow humans to relatively easily write [algorithms](algorithm.md) for [computers](computer.md). It basically allows a human to very specifically and precisely but still relatively comfortably tell a computer what to do. We call a program written in programming language the program's **[source code](source_code.md)**. Programming languages often try to mimic some human language -- practically always [English](english.md) -- so as to be somewhat close to humans but programming language is actually MUCH simpler so that a computer can actually analyze it and understand it precisely (as computers are extremely bad at understanding actual [human language](human_language.md)), without ambiguity, so in the end it all also partially looks like [math](math.md) expressions. A programming language can be seen as a middle ground between pure [machine code](machine_code.md) (the computer's native language, very hard to handle by humans) and natural language (very hard to handle by computers).
|
||||
Programming language is an artificial [formal](formal_language.md) (mathematically precise) language created in order to let humans relatively easily write [algorithms](algorithm.md) for [computers](computer.md). Such a language essentially allows a man to very specifically and precisely (but still relatively comfortably) tell a computer what to do by expressing an algorithm in textual form. [Program](program.md) written in a programming language is called the program's **[source code](source_code.md)**. Programming languages often try to mimic [human language](human_language.md) -- practically always [English](english.md) -- so as to be somewhat close to humans but programming language is actually MUCH simpler so that a computer can actually analyze it and understand it precisely, as understanding natural human languages poses great difficulty to computers, so in the end programming languages also partially resemble [math](math.md) expressions. Programming languages can be seen as a middle ground between pure [machine code](machine_code.md) (the computer's native language, very hard to handle by humans) and natural language (very hard to handle by computers).
|
||||
|
||||
For beginners: a programming language is actually much easier to learn than a [foreign language](human_language.md), it will typically have fewer than 100 "words" to learn (out of which you'll mostly use like 10) and once you know one programming language, learning another becomes a breeze because they're all (usually) pretty similar in basic concepts. The hard part may be learning some of the concepts if you encounter them for the first time. This is not to say programming is easy -- it is hard, but not because learning the language would be difficult; learning the language is relatively the easier part of programming, the hard parts are for example designing the program's architecture well, designing good protocols and interfaces, learning the math behind the problems you're solving, creating good mathematical models, optimizing and debugging your program well and so on.
|
||||
For beginners: a programming language is actually much easier to learn than a [foreign language](human_language.md), it will typically have no more than 100 "words" to learn (out of which you'll mostly use like 10) and once you know one programming language, learning another becomes a breeze because they're all (usually) pretty similar in basic concepts. The hard part may be learning some of the concepts if you encounter them for the first time. This is not to say programming is easy -- it is hard, but not because learning the language would be difficult; learning the language is relatively the easier part of programming, the hard parts are for example designing the program's architecture well, designing good protocols and interfaces, learning the math behind the problems you're solving, creating good mathematical models, optimizing and debugging your program well and so on.
|
||||
|
||||
A programming language is distinct from a general computer language by its purpose to express algorithms and be used for creation of [programs](program.md). In other words: there are computer languages that are NOT programming languages (at least in the narrower sense), such as [HTML](html.md), [json](json.md) and so on. So you shouldn't be calling yourself a programmer if you're just manually writing a website in HTML, people will laugh at you.
|
||||
|
||||
|
|
@ -50,12 +50,12 @@ Another common division is by **level of [abstraction](abstraction.md)** roughly
|
|||
- **[low level](low_level.md)**: Languages which are so called "closer to [hardware](hardware.md)" ("glorified [assembly](assembly.md)"), using little to no abstraction (reflecting more how a computer actually works under the hood without adding too many artificial concepts above it, allowing direct access to memory with [pointers](pointer.md), ...), for this they very often use plain [imperative](imperative.md) paradigm), being less comfortable (requiring the programmer to do many things manually), less flexible, less safe (allowing shooting oneself in the foot). However (because [less is more](less_is_more.md)) they have great many advantages, e.g. being [simple](kiss.md) to implement (and so more [free](freedom.md)) and **greatly efficient** (being fast, memory efficient, ...). One popular definition is also that "a low level language is that which requires paying attention to the irrelevant"; another definition says a low level language is that in which one command usually corresponds to one machine instruction. Low level languages are **typically compiled** (but it doesn't have to be so). Where exactly low level languages end is highly subjective, many say [C](c.md), [Fortran](fortran.md), [Forth](forth.md) and similar languages are low level (normally when discussing them in context of new, very high level languages), others (mainly the older programmers) say only [assembly](assembly.md) languages are low level and some will even say only [machine code](machine_code.md) is low level.
|
||||
- **[high level](high_level.md)**: Languages with higher level of abstraction than low level ones -- they are normally more complex (though not always), interpreted (again, not necessarily), comfortable, dynamically typed, beginner friendly, "safe" (having various safety mechanism, automatic checks, automatic memory management such as [garbage collection](garbage_collection.md)) etc. For all this they are typically slower, less memory efficient, and just more [bloated](bloat.md). Examples are [Python](python.md) or [JavaScript](js.md).
|
||||
|
||||
We can divide language in many more ways, for example based on their **[paradigm](paradigm.md)** (roughly its core idea/model/"philosophy", e.g. [impertaive](imperative.md), [declarative](declarative.md), [object-oriented](oop.md), [functional](functional.md), [logical](logical.md), ...), **purpose** (general purpose, special purpose), computational power ([turing complete](turing_complete.md) or weaker, many definitions of a programming language require Turing completeness), [typing](data_type.md) (strong, weak, dynamic, static) or function evaluation (strict, lazy).
|
||||
It's possible to divide languages in more distinct ways, for instance based on their **[paradigm](paradigm.md)** (roughly its core idea/model/"philosophy", e.g. [impertaive](imperative.md), [declarative](declarative.md), [object-oriented](oop.md), [functional](functional.md), [logical](logical.md), ...), **purpose** (general purpose, special purpose), computational power ([turing complete](turing_complete.md) or weaker, many definitions of a programming language require Turing completeness), [typing](data_type.md) (strong, weak, dynamic, static) or function evaluation (strict, lazy).
|
||||
|
||||
A computer language consists of two main parts:
|
||||
|
||||
- **[syntax](syntax.md)**: The grammar rules and words, i.e. how the language "looks", what expressions we are allowed to write in it. Syntax says which words can follow other words, if indentation has to follow some rules, how to insert comments in the source code, what format numbers can be written in, what kinds of names variables can have etc. Syntax is the surface part, it's often considered not as important or hard as semantics (e.g. syntax errors aren't really a big deal as the language processor immediately catches them and we correct them easily), but a good design of syntax is nevertheless still very important because that's what the programmer actually deals with a great amount of time.
|
||||
- **[semantics](semantics.md)**: The meaning of what we write, i.e. semantics says what the syntax actually stands for. E.g. when syntax says it is possible to write `a / b`, semantics says this means the mathematical operation of division and furthermore specifies what *a* and *b* can actually be, what happens if *b* is zero etc. Semantics is the deeper part as firstly it is more difficult to define and secondly it gives the language its [features](feature.md), its power to compute, usability, it can make the language robust or prone to errors, it can make it efficient or slow, easy and hard to compile, optimize etc.
|
||||
- **[syntax](syntax.md)**: The grammar rules and words, i.e. how the language "looks", what expressions we are allowed to write in it. Syntax says which words can follow other words, if indentation must be present, how to insert comments, what format numbers can be expressed in, what kinds of names variables can have etc. Syntax is the surface part, it's often considered not as important or hard as semantics (e.g. syntax errors aren't really a big deal as the language processor immediately catches them and we correct them easily), but a good syntax design is nonetheless still important because that's what the programmer actually interacts with.
|
||||
- **[semantics](semantics.md)**: The meaning of what we write, i.e. semantics says what the syntax actually stands for, what actions and meaning it expresses. E.g. when syntax says it is possible to write `a / b`, semantics says this means the mathematical operation of division and further specifies what *a* and *b* can actually be, what happens if *b* is zero etc. Semantics is the deeper part as firstly it is more difficult to define and secondly it gives the language its [features](feature.md), its power to compute, usability, it can make the language robust or prone to errors, it can make it efficient or slow, easy and hard to compile, optimize etc.
|
||||
|
||||
We also commonly divide a language to two main parts:
|
||||
|
||||
|
|
|
|||
3680
random_page.md
3680
random_page.md
File diff suppressed because it is too large
Load diff
File diff suppressed because one or more lines are too long
|
|
@ -3,9 +3,9 @@
|
|||
This is an autogenerated article holding stats about this wiki.
|
||||
|
||||
- number of articles: 621
|
||||
- number of commits: 969
|
||||
- total size of all texts in bytes: 5057837
|
||||
- total number of lines of article texts: 36671
|
||||
- number of commits: 970
|
||||
- total size of all texts in bytes: 5058680
|
||||
- total number of lines of article texts: 36678
|
||||
- number of script lines: 295
|
||||
- occurrences of the word "person": 9
|
||||
- occurrences of the word "nigger": 106
|
||||
|
|
@ -36,7 +36,7 @@ longest articles:
|
|||
top 50 5+ letter words:
|
||||
|
||||
- which (2805)
|
||||
- there (2194)
|
||||
- there (2195)
|
||||
- people (2154)
|
||||
- example (1751)
|
||||
- other (1587)
|
||||
|
|
@ -63,14 +63,14 @@ top 50 5+ letter words:
|
|||
- programming (768)
|
||||
- world (750)
|
||||
- system (727)
|
||||
- should (714)
|
||||
- should (715)
|
||||
- doesn (709)
|
||||
- still (707)
|
||||
- still (708)
|
||||
- games (680)
|
||||
- while (671)
|
||||
- point (668)
|
||||
- point (669)
|
||||
- society (666)
|
||||
- drummyfish (657)
|
||||
- drummyfish (659)
|
||||
- simply (653)
|
||||
- possible (649)
|
||||
- using (637)
|
||||
|
|
@ -82,13 +82,25 @@ top 50 5+ letter words:
|
|||
- actually (584)
|
||||
- someone (580)
|
||||
- though (577)
|
||||
- basically (569)
|
||||
- basically (570)
|
||||
- really (566)
|
||||
- technology (548)
|
||||
|
||||
latest changes:
|
||||
|
||||
```
|
||||
Date: Sat Feb 15 17:03:53 2025 +0100
|
||||
comment.md
|
||||
faq.md
|
||||
human_language.md
|
||||
log.md
|
||||
prime.md
|
||||
project.md
|
||||
random_page.md
|
||||
sin.md
|
||||
wiki_pages.md
|
||||
wiki_stats.md
|
||||
wiki_tldr.md
|
||||
Date: Sat Feb 15 00:11:24 2025 +0100
|
||||
art.md
|
||||
drummyfish.md
|
||||
|
|
@ -110,20 +122,6 @@ Date: Wed Feb 12 23:09:00 2025 +0100
|
|||
approximation.md
|
||||
harry_potter.md
|
||||
less_retarded_society.md
|
||||
living.md
|
||||
log.md
|
||||
lrs.md
|
||||
main.md
|
||||
morality.md
|
||||
often_misunderstood.md
|
||||
random_page.md
|
||||
sqrt.md
|
||||
sw_rendering.md
|
||||
vector.md
|
||||
venus_project.md
|
||||
wiki_pages.md
|
||||
wiki_stats.md
|
||||
Date: Sat Feb 8 19:09:45 2025 +0100
|
||||
```
|
||||
|
||||
most wanted pages:
|
||||
|
|
|
|||
Loading…
Reference in a new issue