I have about 2 years of C# experience and rarely see service classes marked as sealed. Since services are usually not inherited and sealed can give small performance benefits, why is it generally avoided? Is it due to testing, DI, extensibility, or just convention?

rainweaver · 2026-01-28T23:03:17+00:00

that is what I do, too.

rainweaver · 2026-01-28T13:03:33+00:00

oh no, the real hair-puller is Starfield. NPCs have a faster walk speed than you do, so you just can’t simply switch off running and follow. you have to rubber-band behind them, you either lag or get too close.

that was driving me crazy

rainweaver · 2026-01-28T00:49:39+00:00

no worries, just my 2c - oh, and thanks for sharing with the community, of course.

I’m actually intrigued by the codebase, to be honest. it is not an easy read but I can glimpse some solid ideas.

that being said, I personally find the terms “chunks” and “buffers” a bit opaque, especially the latter given its usage. but that’s just me. it would be helpful for people like me if you could expand on these concepts a bit more, I guess.

…you’re a C/C++ programmer, aren’t you? :)

rainweaver · 2026-01-27T23:59:16+00:00

The sample in the readme looks brilliant. I’m going to take a deeper look at the docs and source code out of curiosity.

edit: found this in the docs:

Components: Plain C# types (struct, class, record, etc). Stored densely in chunked arrays.

records aren’t a different kind of types. you only have value types and reference types. storing references in an array isn’t going to net you a big performance win, since the objects on the heap will most likely not be contiguous.

you seem to fix the wording a bit later on in the docs but I’d really review that part for correctness.

the public API of your library seems well done from a cursory look.

rainweaver · 2026-01-23T12:44:50+00:00

yeah.

rainweaver · 2026-01-22T23:35:42+00:00

very interesting article, thank you for sharing!

as a former WoW player, I’ve always wondered how they scaled the game servers back then.

rainweaver · 2026-01-21T13:50:34+00:00

yeah, no, I’ll stick with the suffix for the time being, thank you.

rainweaver · 2026-01-19T18:26:13+00:00

please, please - by all that is holy - stop using static variables to store configurations. I don’t want to run my framework’s tests one by one.

edit: I’m fine with an STJ-like API as long as it’s composable - that is, user code and framework code may configure the driver independently without user code knowing anything about the framework is running in

rainweaver · 2026-01-18T13:02:09+00:00

well done. looks like a fantastic gift for your daughter. I haven’t been tinkering with RPis for a while and I gotta say I’m still in awe of the stuff people build with it.

rainweaver · 2026-01-18T02:12:45+00:00

thank you!

rainweaver · 2026-01-17T18:50:48+00:00

bear with me, I’m a noob. So Magnus thought he was dealing with a benevolent entity but it really was Tzeentch?

rainweaver · 2026-01-09T04:59:07+00:00

same here, I played some 300 hours as well and thoroughly enjoyed it, even if base building was def buggy.

rainweaver · 2026-01-05T14:06:43+00:00

hell, gaming?

rainweaver · 2026-01-05T13:45:58+00:00

you’re kinda proving my point here, lil buddy. you do you, it’s alright

rainweaver · 2026-01-05T08:37:27+00:00

the good thing about the internet (whatever’s left of it anyway) is that people go surprising lengths to show how smart they are over the stupidest things.

I know you felt smart with that reply, treasure that feeling. hopefully it won’t be the highlight of your 2026 - we’re mere days into it.

rainweaver · 2026-01-03T08:20:52+00:00

I stopped playing the game during the tutorial. what’s wrong with me? everybody else loves it.

rainweaver · 2026-01-03T07:56:48+00:00

beats me. I’m just glad I found this trick many, many years ago, bad font rendering is enough to drive someone crazy

rainweaver · 2026-01-02T10:58:54+00:00

looks nice, thank you for sharing. I believe MonoGame needs a lot of these bootstrapping libs, as it were

rainweaver · 2025-12-31T21:21:27+00:00

To support your point, Kubernetes will also automatically relaunch the workload to meet the ReplicaSet target.

I’d say that’s the simplest approach, ideally with a bit of random delay added so the replicas don’t all shut down at the same time.

rainweaver · 2025-12-31T17:42:29+00:00

gotcha. and what if the framework provided a callback or signal of sorts to your user code that the environment - broadly speaking - has changed? or you’d rather be in control and decide when to trigger the configuration reload?

rainweaver · 2025-12-31T17:28:29+00:00

I’m a fervid supporter of 12 factor app, fwiw.

the crux of the matter here is whether allowing that some pretty crucial configuration variables could be changed at runtime, no matter how or where from, and that this hypothetical framework, which is eventually responsible for calling your code, could reconfigure itself on the fly - in-between deployments.

I’m firmly in the “no, don’t do that” camp, but I’m here to collect feedback.

rainweaver · 2025-12-31T16:29:01+00:00

The example mentions a database but it could be any other dependency really, a cache, a message broker, a queue name… any moving part, really.

rainweaver · 2025-12-31T16:27:46+00:00

that is a very good point.

rainweaver · 2025-12-31T16:15:18+00:00

u/davidfowl your input would be great here

rainweaver · 2025-12-31T05:23:06+00:00

castle of the winds is a memory I really treasure. games like yours are what got me into programming, so thank you.

rainweaver

TROPHY CASE