Fast film (you can see how grainy it is when you zoom in a little) and shooting in full bright sun = you can shoot very short exposure and freeze motion. There were already cameras in the 1930s with mechanical shutters that could do 1/500th and even 1/1000th of a second exposure, which is plenty fast for this type of shot.

The lens looks pretty fast too - depth of field is very shallow, although part of that is also due to possible use of medium or large format - faster lens (lower f stop) and larger film both allow more light capture, and therefore faster exposure as well, but at the cost of less depth of field.

You have to realize that popular culture was very tightly controlled and restricted by the Polish communist government at this time. This photo was taken at the Jarocin festival, which was a rare chance to see many bands play that otherwise had no radio play or record contracts and often played styles of music that were viewed with great suspicion by the establishment. Recording these live performances and trading tapes was often the only way people got to hear many of these bands.

I grew up in a neighboring country during this time, but I wasn't much into the rock scene then - I was into folk music, which had a similar scene in my country - many folk artists were straight up banned by the government, so it was impossible to hear them on the radio or buy their records, but tape recordings of live performances existed and were traded among the fans. Same of my favorite music from this period only existed in this form. There were even recordings of shows that got shut down by the police mid-set.

The 80s were a period of economic stagnation in eastern Europe, resulting in a lot of pent up anger and angst in the youth, and at the same time, the establishment was slowly losing its grip on the population. As a result artists were getting increasingly bold in channeling this anger and dissatisfaction, of pushing the boundaries of what was allowed, sometimes crossing them and getting slapped down - but you never knew what could happen at a large gathering of the youth back then - taping was an important tool to document and spread this to the wider population.

Looks like a JVC RC-660

The guys in the back both have some kind of Grundig - probably C260 or similar.

Here are a bunch of Grundigs as well, also in Poland.

Even more here

Edit: found the same guy as well

Reagan was a union leader in the 40s and 50s, governor of California in the 60s, and elected president in 84 - he didn't just go from acting to being president, he had a lot more political experience and track record than Trump.

Sure he had charisma and was a good public speaker, but that's pretty much what got Obama the presidency as well.

It's a play on this trope

YouTube video ads can't be blocked with just DNS blocking unfortunately, they are served from the same hosts as YouTube videos.

I think "popular" is stretching it here, Debian GNU/kFreeBSD is dead now, and while Hurd is interesting, it has ways to go.

Alpine is actually popular, particularly as a lightweight host OS to run docker.

You can have a Linux distro without GNU -Alpine Linux is a popular example

What is your source for this ? Recent polls show reunification support is still <2%, with about 6% open to reunification eventually but not now.

In 2018, before the crackdown in HK, the reunification support was 3%, with 13% open to it eventually - the events in HK have definitely significantly eroded support for reunification in Taiwan.

I have family in Taiwan and literally don't know a single Taiwanese person that wants reunification with the PRC.

Early computers had very limited resources, RAM, storage, etc. (first computer I worked with only had 4k of RAM for example) It often made sense to only use the last 2 digits of the year as an optimization in many common tasks that computers were used for, as both the 1800s and the 2000s were far enough away that most basic date calculations worked fine. Also, the industry was changing rapidly, and few people expected their software to be used for more than a few years - certainly not for decades, so focus was usually on solving the immediate tasks as efficiently as possible, without much consideration for the distant future.

However, it turned out that a lot of the code written in this period (70s and 80s) became "legacy code" that companies started relying on for far longer than was expected, to the point that old retired COBOL programmers were being hired for big $$ in late 90s to come and fix Y2K issues in code written decades ago. Many large systems had some critical ancient mainframe code somewhere along the dependency chains. On top of that, even stuff that was meant to handle Y2K was not always tested well, and all kinds of unexpected dependencies crept up where a small bug here, or some forgotten non-compliant library there could wreak havoc once date rolled over into the 2000s.

A lot of the Y2K work was testing all the systems and finding all the places such bugs were hiding.

The first computer I used was a PDP-8 clone, which was a very primitive machine by today's standards - it only had 4k words of RAM (hand-made magnetic core memory !) - you could actually do simple programming tasks (such as short sequences of code to load software from paper tape) by entering machine code directly into memory by flipping mechanical switches on the front panel of the machine for individual bits (for data and memory addresses)

You could also write assembly code on paper, and then convert it into machine code by hand, and manually punch the resulting code sequence onto paper tape to then load into the machine (we had a manual paper punching device for this purpose)

Even with only 4k words of RAM, there were actually multiple assemblers and even compilers and interpreters available for the PDP-8 (FOCAL, FORTRAN, PASCAL, BASIC) - we only had a teletype interface (that printed output on paper), no monitor/terminal, so editing code on the machine itself was challenging, although there was a line editor which you could use, generally to enter programs you wrote on paper beforehand.

Writing assembly code is not actually the same as writing straight machine code - assemblers actually do provide a very useful layer of abstraction, such as function calls, symbolic addressing, variables, etc. - instead of having to always specify memory locations, you could use names to refer to jump points/loops, variables, functions, etc. - the assembler would then convert those into specific addresses as needed, so a small change of code or data structures wouldn't require huge manual process of recalculating all the memory locations as a result, it's all done automatically by the assembler.

So yeah, writing assembly code is still a lot easier than writing direct machine code - even when assembling by hand, you would generally start with assembly code, and just do the extra work that an assembler would do, but by hand.

The kids always adapt though.

There is a strong survivorship bias in this though. Some kids do adapt, maybe even most, but many still are harmed, and have been by unhealthy exposure to radio, television, videogames, etc. in the past. Social media is even wreaking havoc in the older generations right now.

It's easy to point at the survivors and the success stories and say see, there is nothing to worry about - but that's also a bit like pointing at the lifelong smokers who do not get lung cancer as an argument against promoting non-smoking.