In some European countries like Germany, there are recommendations by institutions like the Federal Center for the "Protection of Children and Young People from Harmful Media (BzKJ)" about TV time or screen time in general [0]:
- 0 to 3 years: Ideally, no screen time at all. If media is used, then only in very short intervals and not every day.
- 4 to 5 years: Up to half an hour of screen time per day.
- 6 to 9 years: Up to one hour of screen time per day.
- For older children aged 10 and above, it is advisable to agree on a weekly time allowance.
I would watch up to two hours of tv a day right after school. TV time was up to 5 o clock. Earlier ages had school close at 3:30. Later ages had school close at 2:30. It was a good stress buster. And after that it was homework. Sometimes we would go out and play instead.
I agree with the 6-9 years old tv time. It is about what we did. But the 4-5 years? I know all my friends learned the most from tv this way. I did not because we didn’t have cable. We watched pbs.
I‘m in the process of migrating Kotlin code back to Java in our product. My experiment with Kotlin is over and I‘m sticking 100% with Java. I like writing Kotlin, but I dislike reading Kotlin code.
It’s always a pleasure to read Anton’s Go write ups. Excerpt from the summary:
> Go 1.26 is incredibly big — it's the largest release I've ever seen, and for good reason:
> It brings a lot of useful updates, like the improved new builtin, type-safe error checking, and goroutine leak detector.
> There are also many performance upgrades, including the new garbage collector, faster cgo and memory allocation, and optimized fmt.Errorf and io.ReadAll.
> On top of that, it adds quality-of-life features like multiple log handlers, test artifacts, and the updated go fix tool.
> Finally, there are two specialized experimental packages: one with SIMD support and another with protected mode for forward secrecy.
I'm on Hetzner as well; migrated from DigitalOcean. They are stable, but they got a bit of bad reputation, since they were hacked at least 2 times already [0] [1]. Stable != Secure.
I wouldn't make such a conclusion. I don't think there is any info about whether OP got financial incentives for his work or not. In fact, he posted on Mastodon, he's gonna be doing open source Rust work further on.
I could believe it, the timespan should be 1966-1976, so maybe in late 70s. I know a lot of automation software was being written in my Eastern European socialist country in assembly language around 1974. I think mostly for 6800-based chips like probably MOS 6502.
