oleg_log
1.72K subscribers
1.88K photos
131 videos
9 files
2.82K links
Shelter for antisocial programmers "Oleg"

halp: @olegkovalov
web: https://olegk.dev
fov: @oleg_fov
chat: @oleg_log_blabla
podcast: @generictalks
Download Telegram
Forwarded from Generative Anton
Там Андрей Карпатый выложил miniGPT (потому что не у всех есть несколько лямов для тренировки GPT3). Можно даже куда-то засунуть попробовать (осталось придумать куда).

Самый кайф - картинка в репозитории.
Крутая демка по адаптивному ресайзу изображений (2007 вернули).

Сейчас наверное мало кого таким удивишь, ведь есть другие алгоритмы (это мы еще в DL не смотрели), но подход красивый и рабочий.

https://www.youtube.com/watch?v=6NcIJXTlugc
В коменте у xkcd упоминается ImageMagick и что когда оно сломается, нам придется страдать.
When you query one of these postmodern databases you don't get back a fact you get back an opinion. depending on your application sometimes that might be okay but you just but you don't want to do this for absolutely everything (c) D. Richard Hipp

https://twitter.com/electron0zero/status/1280431762133270529
hacktoberfest.digitalocean.com

1. September is Preptember – a full month to scour repositories and educate participants on quality pull requests.

2. We’re introducing a virtual event kit to help event organizers and attendees get together remotely and safely.

3. We’re offering an alternative, environmentally friendly choice of swag: You can choose the ‘pick trees, not tees’ option to replace a Hacktoberfest T-shirt with a planted tree in celebration of your accomplishments.

собственно вопрос по 3му пункту - убивать природу или быть без ежегодной майки? 🤔 (выслали бы токенов на стим/эпик просто)
Раст таки будет жить, это хорошо.

Building on that work, the Rust Core Team and Mozilla are happy to announce plans to create a Rust foundation. The Rust Core Team's goal is to have the first iteration of the foundation up and running by the end of the year.

https://blog.rust-lang.org/2020/08/18/laying-the-foundation-for-rusts-future.html
Forwarded from Bortlog
The computer is so powerful and so useful
because it has eliminated many of the
physical constraints of electromechanical
devices. This is both its blessing and its
curse: We do not have to worry about the
physical realization of our software designs,
but we also no longer have physical laws the
limit the complexity of these designs—the latter
could be called the curse of flexibility.

- Nancy Leveson, 1995
роскошно
грусть-правдивая
Смотрю в лог билда, вижу предупреждение о депрекейтед, решил глянуть что там.

А это в принципе прикольно, что на каждую мажорную версию нужно переписывать тонну своего кода.

Правда возникает неглубокий вопрос - правда все так сильно изменилось в мире хттп клиентов, что нужно все выкинуть?

Между релизом Spring 4 & 5 конечно 4 года прошло, но хммм. Все это напоминает на писание кода, ради написания кода. Это неправильное, но популярное движение.
Приехали новости по дженерикам, встречайте квадратные скобки и any.

The result is declarations that look like this:
type Vector[T any] []T
func Print[T any](s []T) { … }
func Index[T comparable](s []T, e T) { … }

https://groups.google.com/g/golang-nuts/c/iAD0NBz3DYw/m/VcXSK55XAwAJ?pli=1

Но лучше прочитать фул, хотя не очень легко.
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
Главное продолжать верить в хайлоад
Forwarded from HN Best Comments
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