Update
parent
6ea52fda1b
commit
8ec487492f
@ -0,0 +1,15 @@
|
||||
# Byte
|
||||
|
||||
TODO
|
||||
|
||||
**Byte frequency/probability**: it may be [interesting](interesting.md) and/or useful (e.g. for [compression](compression.md)) to know how often different byte values appear in the data we process with computers -- indeed, this always DEPENDS; if we are working with plain [ASCII](ascii.md) text, we will never encounter values above 127, and on the other hand if we are processing photos from a polar expedition, we will likely mostly encounter byte values of 255 (as snow will cause most pixels to be completely white). In general we may expect values such as [0](zero.md), 255, [1](one.md) and [2](two.md) to be most frequent, as many times these are e.g. assigned special meanings in data encodings, they may be cutoff values etc. Here is a table of measured byte frequencies in real data:
|
||||
|
||||
{ Measured by me. ~drummyfish }
|
||||
|
||||
| type of data | least c. | 2nd least c. | 3rd least c. | 3rd most c. | 2nd most c. | most c. |
|
||||
| -------------------------- | --------- | ------------ | ------------ | ------------ | ------------- | ------------- |
|
||||
| GNU/Linux 64bit executable | 0x9e (0%) | 0xb2 (0%) | 0x9a (0%) | 0x48 (2%) | 0xff (3%) | 0x00 (32%) |
|
||||
| bare metal ARM executable | 0xcf (0%) | 0xb7 (0%) | 0xa7 (0%) | 0xff (2%) | 0x01 (3%) | 0x00 (15%) |
|
||||
| UTF8 English txt book | 0x00 (0%) | 0x01 (0%) | 0x02 (0%) |0x74 (`t`, 6%)|0x65 (`e`, 8%) |0x20 (` `, 14%)|
|
||||
| C source code | 0x00 (0%) | 0x01 (0%) | 0x02 (0%) |0x31 (`1`, 6%)|0x20 (` `, 12%)|0x2c (`,`, 16%)|
|
||||
| raw 24bit RGB photo image | 0x07 (0%) | 0x09 (0%) | 0x08 (0%) | 0xdd (0%) | 0x00 (1%) | 0xff (25%) |
|
||||
@ -1,3 +1,5 @@
|
||||
# Technology
|
||||
|
||||
Technology (from Greek tekhnologia, "systematic treatment of art", also just "tech") encompasses tools and knowledge of making such tools invented and achieved mainly with the help of [science](science.md) and by long systematic effort. This includes everything from [stone tools](rock.md) to space rockets and [artificial intelligence](ai.md). On the Internet, as well as on this Wiki, this term is often used with the focus on [computer](computer.md) technology, i.e. [hardware](hardware.md) and [software](software.md), as this is the kind of technology that is being discussed and developed the most in our days. Technology, like fire, should serve us, but can also be dangerous and often gets misused and abused.
|
||||
Technology (from Greek tekhnologia, "systematic treatment of art", also just "tech") encompasses tools and knowledge of making such tools invented and achieved mainly with the help of [science](science.md) and by long systematic effort. This includes everything from [stone tools](rock.md) to space rockets and [artificial intelligence](ai.md). On the Internet, as well as on this Wiki, this term is often used with the focus on [computer](computer.md) technology, i.e. [hardware](hardware.md) and [software](software.md), as this is the kind of technology that is being discussed and developed the most in our days. Technology, like fire, should serve us, but can also be dangerous and often gets misused and abused.
|
||||
|
||||
**Knowledge of older technology gets lost extremely quickly in society** -- this is a very crucial realization that follow a naive idea of a young man who usually believes that we somehow pertain knowledge of all technology that's been invented from dawn of man until today. In history our society has always only held knowledge of technology it was CURRENTLY ACTIVELY USING; knowledge of decades outdated technology only stays in hands of extremely few individuals and perhaps in some obscure books which ARE UNREADABLE to most, sometimes to none; yet older technology often gets forgotten completely. For example renaissance had to largely reinvent many arts and sciences of making building and statues of antiquity because middle ages have simply forgotten them. A more recent example can be found at [NASA](nasa.md) and their efforts to recreate THEIR OWN old rocket engines: you would think that since they literally have detailed documentation of those engines, they'd be able to simple make them again, but that's not the case because the small undocumented (yet crucial) [know-how](know_how.md) of the people who built the engines decades ago was lost with those individuals who died or retired in the meanwhile; NASA had to start a ginormous project to reinvent its own relatively recent technology. The same is happening in the field of [programming](programming.md): [modern](modern.md) [soydevs](soydev.md) just CANNOT create as efficient software as hackers back then as due to normalization of wasting computing resources they threw away the knowledge of [optimization](optimization.md) technique and [wisdom](unix_philosophy.md) in favor of bullshit such as "soft skills" and memorizing one billion genders and personal pronouns. One might naively think that e.g. since our agriculture is highly efficient and advanced due to all the immense complexity of our current machines, simple farming without machines would be a child's play for us, however the opposite is true: we no longer know how to farm without machines. If a [collapse](collpase.md) comes, we are simply fucked.
|
||||
Loading…
Reference in New Issue