When learning a bit of Japanese to me it was quite obvious that the script was most likely intentionally left (or made) complicated. By using a normal alphabet that actually fits to the structure of Japanese language it would be just another ordinary language to learn.

Using a syllables-script for an ending grammar just doesn't make sense. Using 2 syllable scripts is just strange.

It most likely helped the leaders there to stay in control. Without native Japanese translators foreigners are unable to get very far.

WE USE THREE SYLLABLE SCRIPTS ALL THE TIME IN ENGLISH. lowercase and uppercase are two divergent evolutions of the roman alphabet that got shoved together for no particular reason. 𝘢𝘯𝘥 𝘪𝘵𝘢𝘭𝘪𝘤𝘴 𝘪𝘴 𝘢 𝘵𝘩𝘪𝘳𝘥 𝘥𝘦𝘴𝘤𝘦𝘯𝘥𝘢𝘯𝘵 𝘰𝘧 𝘵𝘩𝘦 𝘢𝘭𝘱𝘩𝘢𝘣𝘦𝘵 𝘵𝘩𝘢𝘵 𝘸𝘦 𝘮𝘦𝘳𝘨𝘦𝘥 𝘪𝘯 𝘵𝘰𝘰. 𝕬𝖙 𝖑𝖊𝖆𝖘𝖙 𝖜𝖊 𝖉𝖔𝖓'𝖙 𝖚𝖘𝖊 𝕭𝖑𝖆𝖈𝖐𝖑𝖊𝖙𝖙𝖊𝖗 𝖆𝖓𝖞𝖒𝖔𝖗𝖊.

>SYLLABE

Ahem. Not even syllabes.

Also, Gothic letters are just a representation, such as cursive, which in the end are the same letter.

You have the Sans/Serif versions of the CJK characters, too.

Are you an Engul user? Syllabic scripts for English are rare. Usually people use letters.

False. Uppercase and lowercase are spelt identically, so do the italics.

LOL. You've been reading Roman letters for so long you've forgotten that A and a don't look even remotely alike.

Uppercase and lowercase are not spelt identically any more than katakana and hiragana are. q-Q, e-E, r-R, a-A, b-B and most of the rest are all completely different characters. Even m and M are not as straightforwardly connected as someone who learned a latin-character based language as their first language would think.

q-Q, e-E, a-A and b-B don't diverge a lot.

Now, put Kanjis in the list and we could guess the closes to that in Spanish would be & (et) and nothing more.

Thinking that e or a look anything like E or A is entirely down to your first language using the Latin alphabet (I'm making an assumption but I can't think of any other way they would look similar).

I've done language conversation exchanges with Japanese English learners and the characters really are completely different to someone learning them for the first time.

へ is virtually identical to ヘ visually. Most of the katakana and hiragana pairs derive from the same kanji and share visual similarities, especially if you’re familiar with Chinese calligraphy. So what?

What you've said is nonsensical.

A good example of the phrase "a little bit of knowledge is a dangerous thing"

The language is structured around those two syllable letters.

Well, I haven't made that up myself - I got the idea from linguistics books - and from people that lived there for a long time. And those linguists were very clear that the language came first and then syllable script was bolted on.

Yes it does. In some distributions receiving calls was a problem (they slept too deep and woke up too slow).

With Mobian for me it now works stable enough to be used as a daily driver.

Well, it works fine as a phone. With Mobian it is stable enough for me to be a daily driver.

When I need performance I usually turn to real computers or specialized gadgets.

I guess with the current state of even simple static website/apps we seem to often need performance. I hadn't even thought about compatibility of the web browser. Might any WebKit based browser (with user-agent overrides) be close enough?

I recently experimented with a ram disk. Practically it didn't change anything.

OS-caching seems to already be clever enough and once the OS has figured out that some directories are important anything in there seemed to get done in RAM anyway.

A RAM-disk will make this less black box and more deterministic regarding guaranteed access times, but in daily use the RAM-disk just didn't make a difference.

Which OS? And were you already on SSD? Those can both greatly influence the outcome.

I'm on Windows. Other OS may differ. I experimented a lot with load times - and compared HDD, SSD, RAM-Disk.

I wrote a small program that loads everything from a big code-repository into RAM. The first time HDD and SSD and RAM-Disk make a big difference, when reading files a second time the lag of HDD (50s?) almost disappeared completely. Caching kicked in.

The RAM-Disk has less initial lag, but also it has to be filled first, so instead of moving everything to RAM-Disk just touching everything so the OS-Caching kicks in is just faster and more convenient.

Great news... Compile time or a clean build? I use similar tooling (older version... :-)). And I'm starting to evaluate what's going on with those new versions.

If you watch the video closely you'll see he's doing a full build for the entire components using a test project.

Comparing compile times is done rarely. I sometimes tried to google some comparisons, but didn't find much.

For a typical 1,5 MLOC project my clean build times are sitting around 40 seconds.

I think that's pretty good, but I don't think I have a way to improve it much. Without writing a compiler from scratch I think 10 seconds are out of reach for me...

Do u think your company will consider cloud compiler if this is x5 faster? There issues such as latency, delta synchronizing, and tool versioning. But its doable.

If u build such a service (pun intended!), the issues are probably cost and security.

Improvements in build-time are very valuable to me. But I'm not sure if a cloud would help me much. Synching can easily eat up 10s. Also my tools are very unique (including a parser that I wrote myself).

To be faster than local a cloud would have to be massively overclocked - and I can already reach good results locally.

For actual improvements I need a massive improvement in compiler technology (last time I looked there were just too many single-threaded bottlenecks in my build process). Nothing a cloud can solve for me.

Security is one issue - but hackers will most likely only get confused when they try to understand what is going on - also costs I usually don't like...

I don't know about China, but the whole science around COVID seems to have a really strong cultural component that before was totally unfamiliar to me.

When looking at some German Epidemiologist blog I found something like: "Next thing on the list is to proof that government measures worked"

I would have expected something like: "I'm looking at data - and want to find out what helps"

That keyboard was fantastic. I hope the PinePhone Keyboard will be able to reach this level.

I once took one of these online-tests for spotting deep fakes. By marking anything that has reflections in the eyes as fake I got only 1 answer wrong (the real guy there looked really strange).