- [encryption](encryption.md), [security](security.md), [memory safety](memory_safery.md) (just don't care and/or don't handle sensitive data with computers connected to the internet, don't live in a shitty society)
- [X11](x11.md) (just pure screen drawing is better)
- [database](database.md) software (plain files are better)
- [database](database.md) software (plain files are better, see [flatfile](flatfile.md))
- [C](c.md) (something in between C and [brainfuck](brainfuck.md) would is likely ideal, e.g. [comun](comun.md) or [Forth](forth.md))
- [glibc](glibc.md), [gcc](gcc.md), [clang](clang.md) etc. (better alternatives are [tcc](tcc.md), [musl](musl.md), [uclibc](uclibc.md) etc.)
- letter accents/diacritics (can normally be ignored in most languages that use them)
@ -108,7 +108,7 @@ Small/medium bloat includes for example:
- [vim](vim.md) (things like [ed](ed.md) are probably better?)
- sound (picture is usually enough)
- high resolution (640x480 is probably the maximum you'll ever need, lower resolution takes less RAM and makes rendering faster)
- [true color](true_color.md) (256 colors, e.g. [332](332.md) palette, is better)
- [true color](true_color.md) (256 colors, e.g. [332](332.md) palette, is better, even 1 bit displays suffice for most things), high [FPS](fps.md) (25 is more than enough), high resolution ([320 x 240](320_240.md) is more than enough) etc.
- [GNU](gnu.md) Unix utils (things like [busybox](busybox.md) or [sbase](sbase.md) are probably better)
- [data types](data_type.md) (untyped or single type is better, everything can be just a [number](number.md))
- [package managers](package_manager.md) (just don't use them, install just a few programs manually, or at least make package managers as simple as possible)
@ -24,4 +24,5 @@ Here there will be a constantly WIP list of [books](book.md) that might be of in
- **The Pig and the Box** (MCM, 2009): A short story for kids showing the dangers of [DRM](drm.md), released under [CC0](cc0.md)!
- **The Tao of Programming** (James, 1987): Famous piece of [hacker culture](hacking.md) literature, wisdom of programming written in taoist style.
- **Tricks of the Game Programming Gurus** (1994): Very nice, readable book, that implements a whole 90s shooter game in [C](c.md), without drowning the reader in tons of equations and smartass talk. It's written with the 90s mindset and in common language, contains many practical tricks for optimizing the code etc.
- older books by **Andreas Eschbach** { The new ones seemed to have some Feminist shit etc., had to stop reading it :D ~drummyfish }, mainly **Carpet Makers** and **Jesus Video**: This is not directly related to LRS but it feels right to mention one of the most underrated [sci-fi](sci_fi.md) authors here -- many LRS followers will probably appreciate high quality sci-fi dealing with super interesting topics that are at least loosely related to LRS. Really Eschbach is so superior to just 99% of all sci-fi you'll encounter, his books are extremely readable, believable and greatly interesting in choosing topics, he makes you think about society, religion etcetc. Spoilers probably won't help, just go check out the books.
@ -35,6 +35,8 @@ Mathematically there cannot exist a lossless compression algorithm that would al
**Dude, how does compression really work tho?** The basic principle of lossless compression is **removing [redundancy](redundancy.md)** ([correlations](correlation.md) in the data), i.e. that which is explicitly stored in the original data but doesn't really have to be there because it can be reasoned out from the remaining data. This is why a completely random [noise](noise.md) can't be compressed -- there is no correlated data in it, nothing to reason out from other parts of the data. However human language for example contains many redundancies. Imagine we are trying to compress English text and have a word such as "computer" on the input -- we can really just shorten it to "computr" and it's still pretty clear the word is meant to be "computer" as there is no other similar English word (we also see that compression algorithm is always specific to the type of data we expect on the input -- we have to know what nature of the input data we can expect). Another way to remove redundancy is to e.g. convert a string such as "HELLOHELLOHELLOHELLOHELLO" to "5xHELLO". Lossy compression on the other hand tries to decide what information is of low importance and can be dropped -- for example a lossy compression of text might discard information about case (upper vs lower case) to be able to store each character with fewer bits; an all caps text is still readable, though less comfortably.
{ A quick intuitive example: [encyclopedias](encyclopedia.md) almost always have at the beginning a list of abbreviations they will use in the definition of terms (e.g. "m.a. -> middle ages", ...), this is so that the book gets shorter and they save money on printing. They compress the text. ~drummyfish }
**OK, but how much can we really compress?** Well, as stated above, there can never be anything such as a universal uber compression algorithm that just makes any input file super small -- everything really depends on the nature of the data we are trying to compress. The more we know about the nature of the input data, the more we can compress, so a general compression program will compress only a little, while an image-specialized compression program will compress better (but will only work with images). As an extreme example, consider that **in theory we can make e.g. an algorithm that compresses one specific 100GB video to 1 bit** (we just define that a bit "1" decompresses to this specific video), but it will only work for that one single video, not for video in general -- i.e. we made an extremely specialized compression and got an extremely good compression ratio, however due to such extreme specialization we can almost never use it. As said, we just cannot compress completely random data at all (as we don't know anything about the nature of such data). On the other hand data with a lot of redundancy, such as video, can be compressed A LOT. Similarly video compression algorithms used in practice work only for videos that appear in the real world which exhibit certain patterns, such as two consecutive frames being very similar -- if we try to compress e.g. static (white noise), video codecs just shit themselves trying to compress it (look up e.g. videos of confetti and see how blocky they get). All in all, some compression [benchmarks](benchmark.md) can be found e.g. at https://web.archive.org/web/20110203152015/http://www.maximumcompression.com/index.html -- the following are mentioned types of data and their best measured compression ratios: English text 0.12, image (lossy) 0.76, executable 0.24.
@ -30,7 +30,7 @@ Here is a list of notable encyclopedias, focused on general knowledge English la
| Chambers Encyclopedia (new) | 2001 | proprietary | 1 vol. 980p | | 1 vol republication of old multivol. enc. (going back to 1800s, already PD), topic-sorted |
| Collier's New Encyclopedia | 1921 | PD (old) | 10 vol. | | NOT TO BE CONFUSED with Collier's Encyclopedia (different one), digitized on Wikisource (txt) |
| Columbia Encyclopedia |1935...| proprietary | 1 vol. ~3Kp | ~50K | high quality, lots of information { Read the 1993 edition, it's super nice. ~drummyfish } |
|[Conservaedia](conservapedia.md)|2006...| proprietary | online | 52K | American fascist wiki, has basic factual errors |
|[Conservaped.](conservapedia.md)|2006...| proprietary | online | 52K | American fascist wiki, has basic factual errors |
| Larousse Desk Reference Enc. | 1995 | proprietary | 1 vol. 800p | 200K? | by James Hughes, nice, quality general overviews, topic-ordered { I bought this, it's nice. ~drummyfish } |
@ -49,6 +49,8 @@ Would you like to create [LRS](lrs.md) but don't have enough spare time/money to
### How To Make A Website
{ If you REALLY want something dead simple to quickly make a site, try https://rentry.co. Making a real custom website is still better if you can. ~drummyfish }
Making your own tiny independent website is pretty simple and a very good thing to do for being able to share opinions and files relatively freely -- using "social networks" for sharing non-mainstream stuff will not work as these get hardcore censored (yes, even the "FOSS" ones like [Mastodon](mastodon.md) etc.). By making your own website you also help decentralize the [web](www.md) again, take a bit of control from the [corporations](corporation.md), and you can greatly help others by sharing useful information with them. See also [smol internet](smol_internet.md). Watch out though, getting into controversial topics on your site will nowadays greatly complicate your life, so firstly set up some "neutral" site and once you get into it, look for ways to somehow add [free speech](free_speech.md) to that. Even if you keep using mainstream social media, it's good to also have your own site and have a link to it on your profile.
Also please take a look at [gopher](gopher.md) (a much better alternative to web) and how to make your own gopherhole -- mainstream web is really becoming unusable, uninhabitable and will die soon, moving to gopher (or hosting your site both on the web and gopher, which is the best option possibly) is a good thing to do, you will not only simplify your life and avoid a lot of censorship but you will also support this smaller network. Another way of sharing your stuff is through things like [torrents](torrent.md), [IPFS](ipfs.md) and so on. But back to websites now.
KISS (Keep It Simple, Stupid!) is a design philosophy that favors simplicity, both internal and external (simplicity of use), [technology](tech.md) that is **as simple as possible** to achieve given task. This philosophy doesn't primarily stem from laziness and a want to save time (though these are valid reasons too), but mainly from the fact that higher [complexity](complexity.md) comes with increasingly negative effects such as the cost of development, cost of [maintenance](maintenance.md), greater probability of [bugs](bug.md) (e.g. [security](security.md) vulnerabilities) and failure, more [dependencies](dependency.md). This stance is related to technology [minimalism](minimalism.md).
KISS (Keep It Simple, Stupid!) is a design philosophy that favors simplicity, both internal and external (simplicity of use), [technology](tech.md) that is **as simple as possible** to achieve given task. This philosophy doesn't primarily stem from laziness and a want to save time (though these are valid reasons too), but mainly from the fact that higher [complexity](complexity.md) comes with increasingly negative effects such as the cost of development, cost of [maintenance](maintenance.md), greater probability of [bugs](bug.md) and failure, more [dependencies](dependency.md). This stance is related to technology [minimalism](minimalism.md).
Under dystopian [capitalism](capitalism.md) simple technology, such as simple software, has at least one more advantage related to "[intellectual property](intellectual_property.md)": a simple solution is less likely to step on a [patent](patent.md) landmine because such a simple solution will either be hard to patent or as more obvious will have been discovered and patented sooner and the patent is more likely to already be expired. So in this sense KISS technology is legally safer.
- **[flatfile](flatfile.md)**: Using files instead of [database](database.md).
- **[rock carved binary data](rock_carved_binary_data.md)**: Way of recording binary data for ages by manually carving them into rock, plastic or similar durable material.
- **[gopher](gopher.md)**: Simple alternative to the [Web](www.md).
- **[json](json.md)**: Simple [data](data.md) text format.
Programming is the act, [science](science.md) and [art](art.md) of writing computer [programs](program.md); it involves creation of [algorithms](algorithm.md) and [data structures](data_structure.md) and implementing them in [programming languages](programming_language.md). It may involve related activities such as [testing](testing.md), [debugging](debugging.md), [hacking](hacking.md) and drinking coffee.
Programming is the act, [science](science.md) and [art](art.md) of writing [computer](computer.md) [programs](program.md); it involves creation of [algorithms](algorithm.md) and [data structures](data_structure.md) and implementing them in [programming languages](programming_language.md). It may involve related activities such as [testing](testing.md), [debugging](debugging.md), [hacking](hacking.md) and drinking coffee.
You may also encounter the term [coding](coding.md) which is used by [noob](noob.md) [wannabe programmers](soydev.md), so called "coders" or [code monkeys](code_monkey.md). "Coding" doesn't reach the quality of programming, it is done in baby handholding languages like [Python](python.md), [JavaScript](javascript.md) or [Rust](rust.md) by people with very shallow knowledge of technology and its context, barely qualified to turn on a computer (like [jewtubers](youtube.md)), who have flooded the computer industry since it became lucrative. It is mostly done for money and/or creating an image for oneself. What they do is not real programming. Do not try to imitate them.
XXIIVV is a website and personal [wiki](wiki.md) (similar concept to [our wiki](lrs_wiki.md)) of a Canadian [minimalist](minimalism.md)/esoteric programmer/artist/[generalist](generalism.md) David Mondou-Labbe who calls himself "Devine Lu Linvega" (lol) who is a part of an artist/programmer group called [Hundred Rabbits](hundred_rabbits.md) who live on a ship. David seems to be a normie [SJW](sjw.md) [fascist](fascist.md), proclaiming "aggressivity" on his web (under "/ethics.html" on his site). The site is accessible at http://wiki.xxiivv.com/site/home.html. There are some real good and pretty bad things about it.
XXIIVV is a website and personal [wiki](wiki.md) (similar concept to [our wiki](lrs_wiki.md)) of a Canadian [minimalist](minimalism.md)/esoteric programmer/artist/[generalist](generalism.md) David Mondou-Labbe who calls himself "Devine Lu Linvega" (lol) who is a part of an artist/programmer group called [Hundred Rabbits](100r.md) (100r) who live on a ship. David seems to be a normie [SJW](sjw.md) [fascist](fascist.md), proclaiming "aggressivity" on his web (under "/ethics.html" on his site). The site is accessible at http://wiki.xxiivv.com/site/home.html. There are some real good and pretty bad things about it.
{ Holy shit his webring is cringe and toxic as fuck. One huge gay nazi wannabe "artist" circlejerk. It's like a small village worth of the kind of psychopaths who draw cute childish drawings of tiny animals with small hearts and love all around while at the same time advocating live castration of anyone who dislikes them. ~drummyfish }
@ -18,4 +18,6 @@ There are also nice things though, a few of them being:
