Notices by Bernie (codewiz@mstdn.io), page 19

There is no "diaries" in the original title, which would have been 日記 (nikki) = day writing

https://jisho.org/word/%E6%97%A5%E8%A8%98

The original title is Kusuriya no Hitorigoto (薬屋のひとりごと).

薬 (kusuri) = drug, medicine
屋 (ya) = shop
ひとり (hitori) = alone
言 (koto) = speech

Together: pharmacy soliloquy.

#japanese #anime

The story follows Maomao, a young pharmacist who works at the Imperial Palace.

She's a very likable #anime protagonist: intelligent, but goofy and a bit insecure. In the first episodes, at least...

I started watching The Apothecary Diaries today, and it's already my favorite #anime series for this season.

I initially thought it was set in the Forbidden City, the palace of the emperor of China in Beijing, but it's actually a fictional country with strong similarities.

@veer66 How about Cpp2? 😏

https://www.youtube.com/watch?v=8U3hl8XMm8c&list=PLHTh1InhhwT7gQEuYznhhvAYTel0qzl72&index=4

Herb Sutter is the chair of the ISO C++ committee, and author of a few books on C++ which I read long ago...

...and he wants to redesign C++ around safety and simplicity. Yes. Unlike previous failed attempts, he actually seems to know how to make this succeed.

With GCC's old-school coding style, it's very easy to call a function with the wrong type of node. My code compiles just fine, but crashes at runtime with my testcase.

I haven't tried, but my change would likely pass the entire GCC testsuite with thousands of tests.

Morale: to speed up software development and eliminate entire classes of bugs, we need abstractions that can be verified at compile-time. Modern C++ incorporates some of these ideas, and Rust is built entirely around them.

@nuncio

A few months ago, I tried fixing a bug in one of GCC's optimization passes.

GCC was originally written in C and is now compiled in C++ mode, but mostly remains a C-style codebase.

I understand the bug and I have some idea of what should be done to fix it, but all my attempts failed with crashes or ICEs 😞

@nuncio

@nuncio That's *always* the case when you work on a large codebase: no human can write one million lines of code on their own, and established projects such as Chrome, Firefox, Android, Linux and GCC are multiple millions of lines written by thousands of people over decades.

That "Caution wet floor" sign over the pool of blood is a nice touch 😂

#linuxgaming #amdgpu #doom2016 #doom

#Doom2016 has all the satanic elements that we've come to expect from the Doom series. I'm not disappointed 👍

#linuxgaming #amdgpu

@mbo77 You're right, I was.

But I suspect the required OS updates played a major role in slowing down the product. Small batches of A1222+ have been manufactured and distributed to developers several years ago.

There's also an ongoing legal dispute around who owns the rights to distribute AmigaOS 4 beyond the "Final Edition".

@nuncio That's in the eye of the beholder: I find modern C++ much more readable than old-school C/C++ with void* and casts everywhere.

And by "readable", I actually mean: being able to verify that it works correctly, without leaking resources, stepping off the bounds of arrays, using uninitialized objects, etc.

@uhrmann Sure, anyone who is starting a new project today would be better served by #Rust than C++23.

But Stroustrup is addressing the context of a large existing codebase. He claims that considerable gains are possible by simply adopting modern C++ and enforcing "safety profiles" with static analyzers.

To which, I don't disagree: I see horrifying C++ code every day at work, and more being added to the pile.

@bjonte There's one major issue: the NXP P1022 lacks the classic PowerPC FPU. Its replacement, the SPE, requires recompiling applications with different compiler flags OR software emulation (slow) OR hot-patching (tricky).

This is likely one of the main reasons for the delays.

https://www.nxp.com/docs/en/fact-sheet/QP1022FS.pdf

Bjarne Stroustrup on delivering safe C++:

"First of all, we have to get people who are not up-to-date on C++ become up-to-date".

https://www.youtube.com/watch?v=I8UvQKvOSSw&list=PLHTh1InhhwT7gQEuYznhhvAYTel0qzl72&index=1
#programming #cpp #cppcon2023

@mbo77 Well... yeah, it might not have been very active, but year after year there's at least *some* observable software development activity on the PowerPC platform beyond AmigaOS 4.1 FE:
http://wiki.amiga.org/index.php/Enhancer_Software#Releases

It's exciting to see this 38-years-old platform being under active development, with new #Amiga hardware and software being released in 2023 ❤️

I just wish I had more time to contribute.

#amigaos #amiwest #amiwest2023

At the ReAmiga4091 booth, I meet Stefan Reinauer, engineering lead of #Coreboot at Google.

As a side-project, he made a perfect replica of the fantastic 4091 SCSI II host controller. I had the original one and loved it.

There are actually a few enhancements to the software and to the programmable logic arrays which make the fastest Zorro 3 controller a little faster.

They even reprinted the A4091 user manual and the box.

I noticed lots of small usability changes, such as being able to push windows outside the screen border and resize them from any border. These things are a given on modern desktop environments, but the Amiga user interface Intuition was designed 38 years ago, well before Windows 3.1!

The super-detailed release notes of Intuition reveal the dedication of the #AmigaOS kernel team ❤️

The single most interesting addition to #AmigaOS 3.3 is the new console handler WCON, which supports tabbed terminals and more.

#amiga #amigaos