Andrew (LinuxJedi) Hutchings

It may have been overkill, but I took the datasheet of the Philips tube used in the Commodore 1084 monitor and used it to recalculate the angles of the CRT shader in Copperline. This is almost ready to be included in the next release. #Amiga

An Amiga in your browser tab: Copperline 0.12.0 released today! Now with a WebAssembly build, big-box A3000/A4000 support, SCSI CD-ROM drives, and writable host folders. Boot one now at https://copperline.dev/try #Amiga Big thanks to Nicolas Ramz for optimising the AROS ROM, this optimised version is now bundled in 0.12.0 (and the online build) and is significantly faster booting the Amiga.

Copperline #Amiga emulator 0.8.0 has been released, and this is one for those who prefer GUIs to command line. There is now a launcher that appears if you do not use command line options. https://copperline.dev/

@raymaccarthy a translation step adds extra complexity and reduces portability. wolfSSL’s predecessor (yaSSL) was written in C++. That was around 20 years ago. C++ is not very mature in yet embedded world anyway, and sometimes we are dealing with compilers from the 90s. It is also a lot easier to hire good C engineers than languages such as Ada.

@codewiz@mstdn.io not so much forgot, more like deliberately didn't shout out about it. There were so many demo regressions in it that I was expecting a lot of bug reports. I'm focusing on fixing it up for 0.11.0 and making a lot of noise about that with the features of both releases.

@dmho it would have been used for SPAG. Possibly to enhance the text. The main work on that post was done by an engineer called David.

@raymaccarthy we have been doing this a very long time, we know what we are doing. Unfortunately, what we do may not align with everyone’s core beliefs about how things work. Many of our engineers are like me, have decades of experience developing core internet infrastructure projects. We also hire where talent is, not where is geographically convenient.

@RealGene @raymaccarthy also, I’ve seen some embedded platforms with some really junk C++ compilers.

@glipari we actually have engineers that came from cryptography into embedded and embedded into cryptography. I have an extensive general engineering background, including embedded and have had to learn the cryptography side.

@goedelchen I’ve seen a lot of people say PHP is dead too. But it still used in a large percentage of the web.

@iron_bug many thanks! We do have kernel crypto and can replace the underlying crypto engines for the other major crypto libraries. Although for the latter part there is not 100% coverage yet. So far it only covers what our FIPS customers have needed.

@iron_bug that is kinda essential for us. We have to compile for platforms where we only have KBytes of flash and RAM to work in. So, we can cut down to exactly what the user needs.

@kasperd yes it can, we have a Rust bindings wrapper to do exactly that.

@thejpster for us the wolfCrypt core is the most important higher risk part for this argument. This is our core cryptographic engine. X509 parsing is in the next layer up (wolfSSL itself), but that makes calls back to the wolfCrypt engine to do the parsing. So, you could take wolfCrypt and implement X509 in Rust on top if you wanted (we have wrappers to help with that)

@codewiz@mstdn.io I’m on several of them and I have my own channel on https://discord.gg/tsAbuAfqf9