Sunday, November 22, 2026

More Grab Bag

It feels like it has been a while since I last said anything here. It's the end of the year, and while things are ``winding down'' in some ways, my jadedness has gone up in others, even as I am partaking in the ``hobby to my hobby'' in terms of performing for flute choirs at various concerts.

Today's going to be a grab bag, because why not?

------

I not-so-recently revamped how I provided access to the Python source patches to make them work on Cygwin. I used to provide a lot more versions than what I have now, but did away with all that because of some recent fast updates from the Python Foundation with respect to fixing up the Python interpreter for all the new exploits that are coming at a geometric rate. Realistically with Python 3.14 series of patches, we won't need to worry about this for quite a while, and all the older patch-releases are just garbage anyway, so keeping them is really bad in terms of presentation; and thus, I chucked it all out.

On a semi-related note, I did a bit more tweaking with my 5×10 and 7×13 pixel fonts. With the help of GPT-6, I've discovered some irregularities with the corresponding .fd source files, and have fixed them (nothing too nefarious---it was silly things like not-quite-correct numbers of rows, or wrong widths for the text-based bitmap definitions), which I then fixed.

The other thing I did was to also do some tweaks between the two font faces so that they look like they might be from the same family (they sort of are). This was where I discovered an important principle that I don't think that I had explicitly made a note of: at smaller and smaller grid sizes, the relative position of a symbol can be more discriminative than one might expect. The particular situation where this turned up was with respect to , versus ., and ; versus :. In the old set up, they were sharing the same ``top height'' for the first active pixel for 7×13; I then updated the 5×10 to match that since that one had the , and ; actually sitting one pixel lower. After I did the change, I immediately regretted it---it was damn bloody impossible to determine ,/. or ;/: when they were next to each other. This was not so obvious most of the time only because the contextual clues often meant that it was usually the case that one of the two characters are more likely to show up than the other, for instance, if I were writing a C/C++ program, it was highly unlikely that : would be showing up. Putting them back to back though, it was obviously harder to tell apart.

And one of the core principles behind these custom tiny pixel fonts was to ensure that characters can be easily told apart from each other.

I reverted the change, and made the 7×13 one now have that funny different in height. I also updated the 5×10 font to use the much more aggressive { and } characters that I first saw in Intel One Mono.

...which naturally segues into the other thing that I had done with my website---I updated the Intel One Mono font there with the latest release. I don't think that the new features in this release are directly relevant to what I have, but it usually never hurts to update things where available. I know that GNU Unifont has a new version that supports Unicode 18+, but ah... the update of that is substantially more involved, what with the need to break up the .woff2 files into different blocks to reduce the download of too big a file when only a small number of glyphs are used.

------

I've been experimenting on and off with GPT-6 these days, getting it to tackle some hobbyist programming tasks that I wanted to do, but knew that it was too tedious to actually spend time doing them. Among the first was revamping the machine player's capability to the Game of Boxes, an old pencil-and-paper game that I enjoyed playing when I was a kid some decades ago. GPT-6 took a really ramshackle machine-playing algorithm and build it up to something that would actually make me sweat hard when playing it. It did so through iterating [very quickly] on the various strategies that I thought was interesting but found too tedious to code, and it was definitely an interesting hybrid approach to programming.

Another project I worked on with GPT-6 was the fixing of a very old (circa 2002) QBasic graphics library I wrote called FMODEX.BAS. The key idea was to make use of mode 12h, the highest resolution available in QBasic at that time with a whopping 640×480 resolution together with a RGGB 2×2 super-pixel dithering scheme combined with tasteful selection of 16-colour attributes out of the 262,144 possible colours available from VGA hardware (6-bit per channel of RGB), to create an effective 320×240 display with 6×11×6=396 colours, which has more colours than the classic mode 13h screen, more pixels (320×240 versus 320×200), not to mention also providing a more ``natural'' colour specification abstraction via RGB channels than the more complicated 256-colour attributes scheme used in mode 13h (this one encodes first the traditional 16-colour attribute scheme using 1-bit colour channels (16), then a grayscale ramp (16), followed by a colour cube for the remaining colours (too lazy to figure out how that works out for this post)).

The main issue that I had was that for some reason, I wasn't getting the correct green levels. The green channel had twice as many pixels per super pixel than the red and blue channels, and by right, it should have better gradation, but I wasn't getting it. Worse, it was uneven enough that I was getting green tinges at high enough saturation of the green channel too, which pissed me off some 24 years ago.

And GPT-6 solved it for me. Check out the after renders for RGB versus CMY.
Wonderful isn't it? No point showing the before, because it was just dumb.

``But MT, why? Why such a stupid useless library?''

Because, believe it or not, doing such small projects of uselessness is one of the best ways to learn something inside out. I mean, is it useful? Hell no. But is it fun? Yes while I was doing it to learn something, in this case I was learning a lot about VGA registers, the math for fast low-level primitives of things like straight lines and circles (hi Bresenham!), Bezier curves, ways to exploit the provided QBasic regular mode 12h drawing primitives to speed up what runs in the interpreter (like using bit masks to draw four lines using the high-speed primitives to draw a super-pixel line).

Such energy is also part of the reason of one of the latest projects that I was smacking with GPT-6---the arbitrary precision uncertainty-aware propagation math library. The core tenet is based on what I had learnt from experimental physics a long time ago---each measurement has its own uncertainty, measurements should not be reported at a higher precision than what their uncertainty can show, and assuming that uncertainties are independent and first order, we can propagate them throughout computations through careful use of the Euclidean norm over the first order partial derivatives.

Now to be clear, I had written all these stuff a long while back, roughly when I first added the masses to my music instruments page. The role that GPT-6 played in this endeavour was improving the code base, and extending the math library to be more robust in the face of increasing nonsense that I was throwing at it.

For starters, it improved the differentiation needed through implementing dual numbers, something that I had learnt of recently through a Numberphile video---this was a project that I wanted to start earlier, separately from the uncertainty propagation, as an extension of Python's Decimal class---this was in lieu of the then central/left/right difference methods that I had implemented before. Then it added a decorator to provide analytical derivatives to improve the accuracy of the error propagation mechanism through reducing uncertainty propagation from the numerical methods.

After that was a steady drive under my probing/prodding/egging to update my Maclaurin/Taylor expansions of various functions to be faster and more accurate, before culminating into implementing some seriously difficult libm functions (staring at you, lgamma()!).

It was a fruitful cooperation. GPT-6 was damn good at coming up with various approaches the way a technically inclined hyperfocused individual could, but that could not move things without my constant cussing it out for spending stupendous efforts on doing something really useless. It got to the point that our ln() function was effectively faster than the built in ln() function, which tickles me to no end. Between GPT-6 and I, we've gotten this error-propagating arbitrary precision math library to complete computations for most of its functions (at 10,000-digit precision) to be at most tens of seconds. Some of the cranky things that GPT-6 did that I would take time to do include:
  • Schema-respecting, lazy tangent number on-disk caching system;
  • Creating deliberate branches for special cases;
  • Much tighter domain checks before expensive computations are done;
  • Using heavily [mathematically] refactored terms in the Maclaurin/Taylor series to speed things up; and
  • Try all versions of asymptotic expansions that may work better.
Again, to be fair, it is not as though GPT-6 magically came up with all these---I had to actually cuss it out to get to where we were.

``But MT, mpmath exists, so why are you wasting time?''

Again, the part of learning by doing overrides whether something ``has been done before'' or not. Yes, I end up with a nice math library that is also capable of propagating uncertainty, but the real value of this entire exercise is the literal experience on the limits/abilities of GPT-6 using a pure chat-only interface.

Will I release this library? At this point, I'm not sure. Unlike FMODEX.BAS, which is clearly a useless museum piece at this point, this library might actually be useful to someone out there. Yet at some fundamental level, since it has a lot of GPT-6 generated code, is it truly my code to release, despite me being the progenitor of the idea to do this entire nonsense in the first place? I don't know just yet.

That all said and done, GPT-6 (and by extension, some of the larger language models that one can have access to) is pretty useful as a tool. It appears smart, a tad smarmy, and has the level of hyperfocus that I would normally attribute to the carefree fourteen-year-old archetype in my usual preaching. But it is not exactly great at direction---it still needs a firm enough hand to point its energies in the direction to proceed. I have not gone down the path of orchestrating agents to do work, mostly because I still do not trust the full delegation of direction and decision-making to these tools just yet, and partly because I have not created the necessary conditions where an ``agentic approach'' is preferable over me using the LLMs solely as standalone-ish tools. I still think that at some fundamental level, we should be having more locally-run LLMs to allow better peering into the metaphoric minds of these tools, as well as having better resilience against when the LLM-providing companies will start turning the thumbscrews once they have a monopoly.

Will I then make it a policy to ``simi sai also AI''? No; I'd never take any single tool and claim it as the one universal thing that everyone needs to use, my job notwithstanding. ``The best tool for the job, if possible, or just a good enough tool for the job where applicable''---that is my motto.

------

And that's about all I want to talk about for now. We're already going past the usual 800-word length (it's about 1.9k+ according to Q10), and I think as a blog in a modern era, this is too damned long. Till the next update then.v

Monday, November 09, 2026

Weekend Flute Hero

And so, the long weekend slowly comes to a close, and work will begin anew in a few short hours.

Over the weekend, I played with the King's Flute Choir at the Flutes in the Forest concert on 2026-11-07T19:30+08, held at Esplanade Recital Studio on The Big Flute. It was a magical performance---unlike the first time that I played there (and with the KFC), there was definitely less stiffness as I have known these folks a little more, and the repertoire was definitely better felt than before, and all in all, I had a wonderful time.

There were also more folks whom I know who bought tickets to come watch the concert, and they spanned from work, to church, and even to TGCO, though how many from the last group was very uncertain, what with many taking opportunity of the ``natural'' long weekend that came from an extra off-day due to Deepavali being on a Sunday to head out of country.

On Sunday, I made my way to the Autumn Flute Festival held at SOTA Gallery by MusicGear and Band World friends. It's an almost annual event where exhibitors from around the region swing by with their flutes, piccolos, and related accessories to show off the latest gear that is available for flute folk, while Muramatsu, Miyazawa, and Sankyo flute technicians do light servicing for the flutes in the background. It's a format that has been happening for at least ten years now, and I have made several friends among the exhibitors. The AFF usually runs for two days, and I'm almost always there for both days, but this time round, I could only go for the second because of the KFC performance on the first. One good thing that came out of that was that the exhibitors were also present at the performance itself, which gave some cool ice-breaking conversations for the new folks whom I've not met before---I was pretty hard to miss, considering that I played The Big Flute, while also having a bald crown.

Anyway, one of the more interesting things that happened during the AFF was from Churaoto Kobo Josef Co., Ltd. Their CEO, Mr Yukio Nakamura, was present (with his wife, I think), and when I was trying out their DARAUMA headjoint (it looks like a traditional cut headjoint, but with an additional channel carved after the blowing edge to allow the air stream to cut much deeper without dealing with the traditional mass of the wall in the way---think of how the Pneumo Pro looks like for a better visualisation) on the hibari Series piccolo, he made a comment that I was a very good player---because I was playing stupid high notes very softly, and with super clean staccato, the kind of playing that I would normally do on a bangdi or even a xiaodi. It was quite pleasant to hear that comment from him---I think this was probably among the first times that Josef has had a presence at the AFF. Maybe they will come again. Oh, and I shared with them about the ``Oval-8'' rings that I was using to prevent my pinkies from locking up.

The other interesting thing was also associated with Josef---their piccolo cleaning flags were at least 1.5 inches longer than the standard Valentino piccolo cleaning flag(!). This means that with that, I could easily swab out Stella (Nagahara MINI) without having to disassemble her!

But they didn't sell it loose like that, and I am now seriously considering having a longer screw-on handle rod machined. It has gotten to the point that I am staring pretty intently at Mitutoyo's fastener tread gauges to figure out the tapping needed.

I met Mr Guo (GUO Music Instrument Company) once more, and he was showing me his prototype PHONIC crown for the contrabass flute. It looked really cool, but I didn't bring The Big Flute down during my trip to AFF because I was just tired and wanted to just enjoy the fair without lugging too much luggage. It can be a really good upgrade to The Big Flute to enhance articulation through damping out the excess noise/standing waves after the motive force (i.e. the airstream) is removed.

I then went on to have dinner at Five Guys, walking from SOTA Gallery to Plaza Singapura, only to walk back to SOTA to take the bus back home.

And as for today, I just slept in, and spent much of the day catching up on my various YouTube videos, before deciding to write this entry.

That's one of two major flute performances done. The next one will be with AFE JB, and on 2026-11-29... which leaves something like another three-ish weeks left for rehearsals. And then, that's probably the last of the performances for this year, unless I get directly involved in this year's Christmas event under Music Ministry (hard to say at this point).

Sadly, I am having a weird-ass tension headache on my left side, so I'm just going to call it a day for all major activities, and just turn in for the night.

Till the next update, I suppose.

Sunday, November 01, 2026

counter_game Has Been Released Upon the Unsuspecting World!

Today, I bring you: counter_game, the most simplified of idle games that I can come up with that is still somewhat meaningful.

The premise is simple: increment a 64-bit unsigned integer counter, one at a time.

And that's it.

It's fun because it is hilariously straightforward in terms of what it seeks to do. No funny multipliers, no annoying precision-loss when double-precision floating point numbers are inevitably used (staring at you, Cookie Clicker). Just good old fashioned incrementing of an integer variable.

What's really interesting are two things.

The first, is that modern CPUs are scary fast, even without taking into consideration that there are multiple cores per CPU. On a thermally limited machine that is Eileen-III, I am consistently seeing 5e+09-ish increments per second, while on a machine that does not have that limitation (i.e. running in an air-conditioned room), I had seen 7.4e+09 increments per second.

That's actually more than the burst clock speed of 5.5 GHz to 6.1 GHz that is common these days.

And yet, it still takes decades to truly rollover all 264 different values of the counter.

The second, is the iterations that I had went through to fixing the code up. The original code was written a few months ago, and its requirements were more or less the same as what I had released---increment a large unsigned integer counter in as tight a loop as possible, but have a means of keeping track of the work to resume later on somehow. And maybe have some simple output that is user-triggered to avoid the penalty of doing I/O for something that is ``obviously'' CPU bound.

Oh, and avoid the compiler from optimising away the ``obviously'' do-nothing increment loop.

I started with C99, and wrote something very similar to what I currently have, with the following major differences:
  1. The counter was originally of type static volatile uint64_t, which was because...
  2. ...the original signal handler was doing the actual saving of state, which meant that volatile was needed to tell the compiler to not optimise away what is effectively a ``do-nothing tight loop'' to the compiler; and
  3. I had to resort to some GCC extension of locale to enable thousands separators for the ludicrously large integers because I was too lazy to write my own C99-compliant version.
Reading the current code base should reveal that these things that I talked about were no longer there.

What happened?

Well, I chucked it into GPT-6 to see what the LLM could suggest as code improvements, and through to and fro, managed to converge to the current released version.

The only thing that wasn't really suggested by the LLM was the removal of that volatile specifier---with the signal handler only setting some atomic signal outside of the tight loop, and the logic for the I/O pushed into the tight loop but guarded by a signal comparison, the volatile storage class was no longer needed since the counter variable was in scope for both increment, and reference for the purposes of doing I/O.

For the confused, volatile tells the C99-compiler that a particular variable should be assumed to be backed by memory, which means that when optimising/generating code, the register-only optimisation is not allowed; all references to the volatile variable must load the value from the memory, and subsequently written back, without assuming/keeping the value based on what is in the register.

That change dramatically sped up the increment rate by more than 10-fold, since each increment no longer needed to go through the entire memory hierarchy of L*-caches before reaching RAM.

So with my foray into using LLM for support in software programming, what do I feel? Honestly, it isn't too bad, but to be fair, this is merely about improving an existing program that does something pretty simple---it is not a multi-file project with the full backing documentation of user requirements, project specifications, and everything else under the sun.

As a tool, it is fine for this case, but in some future post, I might talk about another different programming project that I had GPT-6 assist me. Spoiler: that one was a doozy, even though the outcome is still better than what I would do myself.

The key thing to take away is that using these tools really does make me lazier in some ways, and more hardworking in others. Yes, I wouldn't set out to write my own custom C99-compliant code to output the large integers in groups of six digits due to how annoying it was, but with the LLM yelling at me often enough about ``hur hur you claim C99 compliance but you're using GNU extensions you dumbass'' was enough to start the skeleton of that code, and have the GPT-6 finish it up.

``MT, what's the purpose of counter_game then?''

It's an idle game where a counter is diligently incremented one at a time by the CPU without funny modifiers, exponentiation shenanigans, and bad floating point numbers. That's its purpose. It can also act as a low-resource single-thread (not core since I do not put in non-C99-compliant CPU affinity setting code) performance tester for a computer that runs Cygwin/Linux, at least on the dimension of incrementing a register.

I think that's as pithy a response as I have.

Till the next update.

Friday, October 30, 2026

I've Been Drinking [Again]

I have been drinking. Not much, just Tsingtao beer at the nearest 辣不辣 near where I stay. So I'm sloshed.

And let me tell you something---if you don't ``own'' the platform that you are making your expressions on, you will forever be at the mercy of whatever [retrospective] rulings that said platform chooses to enforce, and more importantly, you basically have no recourse whatsoever.

Recently there has been an ```updated'' Blogger terms and conditions that basically says that they can take you down if they find you offensive for any reason. Note that I said ``you'', not ``your content''. Maybe I'm sloshed and have shitty-ass memory, but let this be a warning to those who are still sleeping---unless you ``own'' the platform that you are making your expression on, be prepared to be at the mercy of whatever policies that the platform may have, which they are very likely to happily retroactively apply without your ``consent''.

``Consent'' is scare-quoted as thus because the platform provide has a much stronger power over you than you over the platform, which makes the idea of consent almost comical---as if you saying ``no'' is sufficient for the platform to backtrack from their fuckery.

If you believe in this kind of shit, I have a bridge to sell you in the Sahara.

But what's my point, you might ask. I'm sloshed---does it mean that anything that I'm willing to say here has to have a point? If yes, then damn you place more value on my cognitive powers when sloshed than I do; whether or not it is well-deserved notwithstanding.

But yeah, that's something to take note about. This also means that this twenty-year-old blog has a significantly high chance of being nuked from orbit if there should come a day where the sensibilities of the Blogger owner decides that throwing one too many fucks into the write up is of sufficiently immoral behaviour that everything just needs to be nuked from orbit.

If you ask me right now what I think, I'd just say ``I haven't the foggiest clue.''

I think that's about it. I cannot bring myself to talk more drivel here.

Saturday, October 24, 2026

Ramblings on a Saturday in Between Keeping Myself Sane

There's a weird side effect of modern [pop?] culture that makes me raise my metaphorical eyebrow: despite being a species from class Mammalia, literally named by humans after the literal milk-producing breast which is a discriminative characteristic for this entire class of vertebrates, we get damn antsy about talking about breasts as a whole.

Why?

The sexualisation of [human] breasts cannot be the only reason---I suspect it is less about the sexualisation, and more about the implied obsession when a human body part primarily meant for feeding the young gets brought into [everyday ``polite''] conversation.

I mean, unless you are a parent, it is easy to see how ``breasts'' is not exactly on the top ten list of topics in casual conversation. Where the posterior probability of that being a legitimate conversationn gets higher, it is usually due to someone wearing some garment or posturing themselves in a way that draws attention to their breasts, and under those circumstances, modern ``sensibilities'' of ``morality'' kick in, and the conversation briefly veers into that direction, before snapping back to something that obviously diverts attention away from the breasts.

Me? I don't really care about the sexualisation as a whole. I'm more of an aesthete on such matters. It is less about the size and shape of the breasts alone, and more about the overall contribution to the beauty of the femme aesthetic. To me, big boobs, small boobs don't matter as much, so long that if someone is presenting as femme, their overall aesthetics should match that of a femme, and more importantly as a man, they ought to have some boobs that outsize my moob-less chest. Frankly, it is quite hard for me to claim that someone is femme-presenting if they are at best androgenous-looking, with non-existent secondary sex characteristics. I'm not saying that every part of the femme-presenting person needs to conform to stereotypical ``woman'' characteristics, but they need to at least match what they claim to be presenting for the most part, be it in appearance, or behaviour.

But that's a declaration of personal preference, not an assault on whatever identity anyone wants to have. That a person thinks they are femme-presenting while I disagree due to my own personal preference simultaneously is a world state that can exist, and as long as neither of us are forcing either of us to conform to the other person's perspective; I think we can agree to disagree and carry on with life.

After all, why should I care how someone presents themselves from a sexual/gender identity when that particular dimension isn't something that I usually give a damn about? I'm more interested in the way they carry themselves, and while looks are always among the first things that anyone sees from the get-go, the pre-frontal cortex learns to suppress all initial monkey-brain judgement until more evidence and information is obtained.

That said, boobs are still pretty, and seeing them on a nice (sensu behaviour, not necessarily just looks) lady is always a treat. I say this earnestly and without any other intent.

Honestly, I wasn't intending to talk about boobs today... but I suppose it is just an effect of seeing too many ``social media posts'' recently that triggered me into thinking more along these lines.

------

What I really want to talk about is the idea of obsolescence. I think part of the bargain we strike in social contracts with a society of people at large is the idea that to be a part of the society, we must remain relevant. But what ``counts'' as being relevant within a society is not a well-defined property; in many ways, it is tautological: one is relevant in society if there is a societal need for you, sensu your skills, your existence, or your resources. The tautology comes because the dependence stipulated in in the ``need'' is defined relative to society: the need for your skills only if your skills are relevant to what society needs, the need for your existence if your existence is relevant to what society needs, the need for your resources if your resources are relevant to what society needs.

Under a much smaller unit of society, like a family, or even tribe/village, relevance is a mix of material and spiritual. Material contributions of the able-bodied are almost always considered relevant, while the wisdom and sometimes knowledge of the elders can be seen a spiritual relevance that gives the family/tribe/village its sense of identity and coherence, while the relevance of children can be a mix of both material (future material contributors after maturing), and spiritual (a representation of renewal of the family/tribe/village).

But what happens when one's society is conurbation-scaled? How can two million people demonstrate their relevance?

My answer is, they cannot, not least in a direct way. Modern society's demonstration of relevance is through the very business-oriented concept of demonstrating value, and that usually means converting whatever it is that one can provide into some kind of fungible currency, usually in the concept of ``dollars''. That is the case not because currency is truly fungible, but that modern societies are primarily economic wealth generators first, before they are social wealth ones.

In other words, ``GDP go up'' trumps ``people are excellent to each other''.

This is where obsolescence comes to play. I don't think that any person can be truly obsolete if we consider the relational nature between people. Can one really say that grandpa is obsolete as grandpa just because he got older? There may be a case to be made if dementia is taken into account, but that's only if we make a more narrow definition of how a ``person'' is not the meat-bag in front of you, but is just what that meat-bag remembers/thinks. Grandpa may not be fully ``here'' ``up there'' if he is demented, but at no time can any reasonable person truly claim that grandpa is obsolete as grandpa.

From a ``GDP go up'' perspective? Always possible. One can be the best damned vacuum tube transistor engineer of all time, but in 2026, if that is all you have going for you, you are deemed obsolete.

I think that there's a catch here though. Society may have a way of declaring that someone is obsolete primarily through the market mechanism, but the definition of the market itself is tautological---it is always possible to ``make'' your own damn market. Only a handful of die-hards had believed strongly in vinyl records ever since it was invented in the late nineteenth century and mass-produced throughout the twentieth century, with the said records declared obsolete once the compact disc was invented. And yet we see a new resurgence in this right now in the mid-2020s, and it is all due to market making.

Thus at some fundamental level, whether or not something is obsolete is not a fate that society alone can declare; there is a certain amount of individual free-will so to speak to usher in renewed uses/responses to what was said to be obsolete.

Combining this with my helical hypothesis of the world happenings (I'm not sure if I had talked about this here before, but for sure I have been expounding this in meat-space), I don't think that ``obsolescence'' is a permanent feature.

As long as we keep thinking, and acting on what we think, we'll never truly die.

Saturday, October 17, 2026

A Short Blurb

I should really update the habit of mostly writing here when things are going/have gone south, but then again, the more I spend time ``documenting'' what happens in life, the less time I have to spend on the actual living.

A true dilemma, indeed.

The haze in SIN city has gotten to the point of sheer ridiculousness---I know because I'm coughing like some TB patient with all these stupid particulate material trapped in my lungs and what-not. The hill that I have to climb daily while getting my ass to work? Recently, just a third up, I found myself being breathless, and coughing my lungs out.

It was bad.

I had to skip out on rehearsal with AFE JB yesterday to rest up. I also had to skip out on TGCO rehearsals this evening for more of the same. I have been chugging Chinese liquorice root tea for the whole of yesterday and bits of today, in a bid to keep the throat from being too annoyed from all the coughing.

And that's about it for how I'm feeling physically.

Mentally, I'm a mess. Long story short: work.

No more details will be forthcoming on that.

Till the next update, perhaps.

Wednesday, October 07, 2026

``Darkness Will Fade Away...''

Back in June, I wondered if IRyS's sololive had a cinema live-viewing.

Yes, there was! And I was there!
I ran out of leave for this year, having taken the remaining of them for these two months' of Fridays for AFE JB rehearsals, but had some off-in-lieu from the Astana work trip that I could expend.

Best use of 1/2-day off-in-lieu in a damn while.

I love IRyS's singing, and she sang a whole damn lot throughout the concert yesterday. It was banger after banger after banger---you can catch the free preview on YouTube:

Yes, she looks sexy, but that's not the point! The singing is absolute fire, and that was what really drew me to her all those years ago when she first made her debut as the first EN member after the hololive -Myth- ladies.

I had a great time, even though it was a Tuesday, and I had to take a bus down towards the city even as it is getting locked down in preparation for the F1 Night Race.

The best part was when she sang the final song for the night, Caesura of Despair. All night, she was swapping between her 3D concert outfits, but for this, she went back to her default outfit, and with that, a whole montage of five years of singing and other streaming activities.
It was powerfully moving---I cried. This was a girl whom I had watch through the years, and had culminated into this sololive.

Ina and Kiara's concert didn't evoke as strong feelings as IRyS's for some reason. Maybe it's because IRyS was in many ways more orphaned than the other girls in the overall hololive scene---she debuted solo originally as a VSinger in the English branch, but that eventually went away. The original Project: HOPE VSinger project went away when the original director was ousted due to... shall we say unlikeability by the talents. Then there was a period where IRyS's original design had to be redone to better fit the live2D aesthetic necessary as a VTuber and later on, 3D models. And being a solo debutante meant that for quite a while, her place among the hololive EN ladies had been fluid, good in the sense of expanded horizons, but bad in the sense of a lack of a ``generation'' to consistently have support for.

It took her a while to get to here today. While she's not as OG as the hololive -Myth- ladies, she was the in-between before hololive -Council- was a thing. Eventually, she found her place among all the friends, even creating stronger links with the JP holomems.

And she has won the heart of the IRyStocracts with her great singing, YabaIRyS tendencies, and general goofiness that made her endearing; diva-esque singing without being an insufferable diva.

I don't think I feel qualified enough to heap on more praises on IRyS. Suffice to say, that concert was magical in a different way from Drawn to Dawn and Serendipity.

Now, allow me to re-listen to her music once again, and re-live what I saw last evening. Till the next update.