Linus Torvalds made his initial commit of Git's code on April 7th 2005, he added a file called README:

GIT - the stupid content tracker

"git" can mean anything, depending on your mood.

- random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
- stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
- "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
- "goddamn idiotic truckload of sh*t": when it breaks

This is a stupid (but extremely fast) directory content manager. It doesn't do a whole lot, but what it _does_ do is track directory contents efficiently.

https://initialcommit.com/blog/How-Did-Git-Get-Its-Name

Главное продолжать верить в хайлоад

Re: You don’t need reproducible builds

There are a lot of reasons to prefer reproducible builds, and many of them are not security related... It seems a bit presumptuous to argue that noone needs reproducible builds because one particular security argument is flawed.

First, a non-flawed security argument: it only takes one non-malicious person to build a package from source and find that it doesn't match the distributed binary to spot a problem. Sure, if you don't compile the binaries yourself, you might not find out until later that a binary was compromised, but that's still better than never finding out. The reality is that most people don't want to spend time building all their packages from source...

More generally, reproducible builds make build artifacts a pure function of their inputs. There are countless reasons why this might be desirable.

- If a binary is lost, it can be rebuilt exactly as it was. You only need to ensure the source is preserved.

- If a particular version of the code is tested, and the binary is not a pure function of the code, then you haven't really tested the binary. Bugs could still be introduced that were not caught during testing because your build is non-deterministic.

- It provides a foundation for your entire OS image to be built deterministically.

- If you use a build cache, intermediate artifacts can be cached more easily, and use less space. For example, changing the code from A -> B -> A will result in two distinct artifacts instead of three.

Diggsey, 6 hours ago

век живи, век учись — увидел сегодня новый формат даты: DD.MM.HHmm 🤦‍ (т.е. 04.08.2010 - это 20:10, 4 августа)

бегу собирать фичерлист, чтобы завезли по знакомству, чур я 1й в очереди

топ

Визуализация нового пропозала про дженерики с отличными примерами от Владимир Вивьен

https://twitter.com/vladimirvivien/status/1297595414590427142?s=21

2020 конечно прикольный год

One day, while studying old code, I found out that it's possible to encode Windows Portable Executable files as a UNIX Sixth Edition shell script, due to the fact that the Thompson Shell didn't use a shebang line.

Once I realized it's possible to create a synthesis of the binary formats being used by Unix, Windows, and MacOS, I couldn't resist the temptation of making it a reality, since it means that high-performance native code can be almost as pain-free as web apps.

https://justine.storage.googleapis.com/ape.html

Почему не стоит запускать python в папке с загрузками. Как легко догадаться - запускается все подряд.

Каким-то образом это всегда ощущалось шкурой, но раньше подобные статьи не встречал. Возможно какой-то там Руби имеет те же проблемы. А может и не только. Короч в Downloads ток компилировать можно.

https://glyph.twistedmatrix.com/2020/08/never-run-python-in-your-downloads-folder.html

Накинем на ЖС старым постом из 2017 (в начале статьи чуть ню-фотка)(я не пытался вас привлечь этим к статье, чесн)

So it got me thinking a lot about this JS situation, and the only plausible explanation is this : Frontend has been despised by engineers because it is less scientific and more intuitive, and also because tooling has failed us over the years. So designers have picked up the ball and now they want to program, the result being NodeJS, JS and blindness to their holes ( — craters) . Designers are no engineers and vice versa, we should stick to our respective strengths.

https://hackernoon.com/the-javascript-phenomenon-is-a-mass-psychosis-57adebb09359

Найди снг и заплачь. А вообще прикольно.

Друзья, тут вышла хорошая статья про QUIC в Го, надо лайкать.

https://www.reddit.com/r/golang/comments/igg1os/experimenting_with_quic_and_webtransport_in_go/

https://news.ycombinator.com/item?id=24273371

https://lobste.rs/s/asllz4/experimenting_with_quic_webtransport_go

#rust (other versions + dark theme) https://github.com/usagi/rust-memory-container-cs

Выложены доклады с GopherCon Russia 2020 August.

С самим Go я мало связан, но три видео "на посмотреть" себе закинул

eBPF: современные возможности интроспекции в Linux, или Ядро больше не черный ящик. Марко Кевац
https://www.youtube.com/watch?v=GSzxg6wucbA

Воркшоп: Знакомимся с Observability на практике. Елена Граховац
https://www.youtube.com/watch?v=7h7HOge2MAw

Воркшоп: TLA+/TLC: практичный инструмент формальной верификаций алгоритмов. Алексей Найденов
https://www.youtube.com/watch?v=wGEbOHX2hCs

Все доклады
https://www.youtube.com/playlist?list=PLJTW0ZQ22rrEtvqbz0rxhNQTm0bkJV4Nb

Программа
https://www.gophercon-russia.ru/

Вот это я понимаю оптимальное приготовление хавчика.

https://www.ethanrosenthal.com/2020/08/25/optimal-peanut-butter-and-banana-sandwiches/

Эй, сесурити озадаченные, подскажите такой сервис(ы), которые проверяют, какие данные торчат из браузера?

Кроме юзер-агента и разрешения экрана :))))))) Хочется узнать, что можно узнать про пользователя, если просто он(а) открыл страницу.

Был какой-то сайтик, которые проверял на сколько уникальное комбо таких данных, но я как-то не нагуглил. Уверен что еще есть. Слать сюда @olegkovalov пошарю если что-то будет хорошее. (подборку каналов на днях докину кстати)

UPD: https://amiunique.org спасибо всем, ща еще денёк подожду и другие варианты докину постом