archargelod

I've only watched the original series, once, and understood most of it.

It's just meaning is very very vague on purpose. It's not meant to be specific. Most of Japanese art is like that.

Also, if you start learning Japanese language, you'll quickly notice that the "I'm not going to tell you anything directly" and "read the room" permeates even casual and especially formal daily conversations.

Blocking popular websites is certainly going to boost this number, dramatically.

Fail fast, with no one succeeding is not healthy.

One vibe-coded app is no better than other, or if it's better - not for long. So why would anyone invest in product that is going to be superseded in a few months/weeks/days?

It's not just em dashes, it's 1: typewriter em dashes aka `--` and 2: usage of them in pairs, like parenthesis, that is completely different from how LLMs use them.

Notice how I didn't say that I "learned" both in a day, I "remembered" them. Of course actual learning will take some time, especially with less used characters. But remembering shapes and differentiating between them using mnemonics should not be too hard for most people.

Absolutely agree. Romaji was absolutely pointless for me and probably a detriment overall to learning a language. Japanese uses consonant + vowel pairs as a rule, and the faster you train your intuition for this, the better.

Remembering both Hiragana and Katakana took me no more than a day each. Although I have to admit that I already tried learning them around 5 years ago and gave up back then out of lack of motivation.

Depends on what you mean by "simple". In my head, specifically with software, simple is defined as "does less", which is definitely somewhat easier to make, than a complex program that "does more".

Literally doesn't matter, player closest to dice at the moment you open the box.

Can somebody explain why not just make a die with 5! sides, and roll it once to decide the order? With each side having a unique order printed e.g. 12345 -> 12354 -> ...

Especially, that 120-sided dice are already invented and commercially available.

How do you write a spec for correctness? Only the small and unimpressive programs can be checked exhaustively.

I indeed don't know about Java, but with C# there are a lot of limitations if you want AOT compilation and you still get the bloated binary and limited performance.

I also, personally, never seen a single project written in either Java or C# that distributes aot binaries.

Inferior to languages that compile to native binaries, not burning dramatically more cpu cycles than necessary.

I was excited to try Julia, but then, as I saw it was an interpreted language, with bulky runtime, slow startup times and bloated library sizes - my initial interest quickly faded.

For the same reasons I see languages like Python, Java, C# as inferior.