Randy Simons

@RandySimons
33 Followers
29 Following
236 Posts
My open source projectshttps://codeberg.org/randysimons
Show threadRandy Simons2d ago

@msxwiki

Well, it could have been :)

MSX2: :https://webmsx.org/?DISK=https://owncloud.randysimons.nl/public.php/dav/files/3yJpJEmwT59zTHw

MSX2+: https://webmsx.org/?DISK=https://owncloud.randysimons.nl/public.php/dav/files/xSCXk8tALYqsXJa

#MSX

WebMSX - The online MSX emulator

Play MSX2+ games in your browser, phone or tablet!

Show threadRandy Simons2d ago
@SamLeLuxo @hardpenguin13 I believe that "protecting the user" is more of a side effect. I.e. an excuse for the real reason: more control over the platform.
Show threadRandy Simons2d ago

@SamLeLuxo @hardpenguin13 Until it becomes 2 steps. Then none, because it is no longer an option.

I don't want a generic computing device, like a smartphone, that doesn't do what I, the owner, tell it to do.

Randy Simons4d ago

@stasdigi Als ik https://www.rvo.nl/onderwerpen/recreatief-vissen-zoutwater goed begrijp dan zou ik mijn vangst *moeten* registreren met een app als ik recreatief in zoutwater zou vissen? En dat die apps alleen voor Amerikaanse besturingssystemen beschikbaar zijn?

Ik heb het Europese #SailfishOS (Ja, een zoutwatervis. Had ik dat ook moeten registreren?) besturingssysteem op mij telefoon. Hoe zou ik dan te werk moeten gaan?

#eu #appdwang

Recreatief vissen in kustwateren, zeegebied en Visserijzone

Voor recreatief vissen in de kustwateren, het zeegebied en de Visserijzone gelden er bepaalde regels. Vanaf 10 januari 2026 moeten recreatieve vissers in de EU ook bepaalde vangsten in een mobiele app registreren. Wilt u recreatief vissen in de kustwateren, het zeegebied of de Visserijzone? Hier zijn regels voor. Bijvoorbeeld voor de vistuigen die u gebruikt. Ook gebruikt u de vis alleen voor uzelf en verkoopt u deze dus niet.

RVO.nl
Show threadRandy Simons4d ago
@masimalmi @jolla And their code repositories for #sailfishos are still on GitHub. 😕
Randy Simons5d ago

RE: https://mastodon.social/@thany/116244778756409673

We've learned that without sanity, there can be no peace.

Show threadRandy SimonsMar 15

@fosserytech @ennenine I've daily driving SailfishOS since it inception in 2013. It is Linux, so you can flex that terminal on it as well, root access and all. I've recently made a tool in Go (which compiles to native binaries). Well, that ARM64 Linux build of that tool Just Works on my XA2 running SailfishOS.

It has its wreaths. Don't expect full iOS/Android-level polish. The browser, while being Firefox-based, is lagging in development. Thus I use Firefox for Android as main browser instead.

Show threadRandy SimonsMar 14

@silentexception All MSX1 had (more or less) the same 32KiB ROM. It was a standard, after all. The spec required at least 8KiB of RAM, but 64KiB was quite common. For BASIC, anything more than 32KiB didn't really matter, it wasn't used.

Perhaps that's my biggest gripe with MSX BASIC, especially apparent in the later systems: you got ~28KiB to work with, even less with diskdrive enabled,, regardless the amount of RAM installed. MSX2 added `CALL MEMINI`, but that sucked.

Show threadRandy SimonsMar 14

@silentexception From what I've read is that (almost) all is 8080 code, from their earlier BASIC versions. Perhaps MS could have optimized a bit by using the extra Z80 instructions. Not sure if that would (or even could) be enough to squeeze in better pattern support.

But for the MSX2 bitmap modes they did properly give BASIC access to many of the hardware accelerated features of the V9938, supported pages, interlace, YAE/YJK (MSX2+). I had lots of fun with it.

Show threadRandy SimonsMar 13

@silentexception I loved how well the BASIC implementation could tap into the graphical capabilities of the #MSX, especially on the #v9938 of #MSX2 and up.

Support for the pattern modes of the TMS9918 (SCREEN 1 and 2) of the MSX1 was, in retrospect, less well developed. I guess the 32KiB ROM was full.