pragma_x

As someone who has never used MCP, or allowed an AI to directly talk to APIs, putting something between a model and a service just seems like common sense. If nothing else, it presents an opportunity to tightly control what the AI is allowed to do with external services, especially if the MCP code is outside of the AI's context. I would go as far as to say it's a necessary security measure.

What I find amusing about moving compute to a RAM bank is it _almost_ resembles where we were with ISA-based extended RAM back in the 1980's. Some cards featured a CPU that took over the whole system and/or functioned like an upgrade. Others were a "computer on a card" that provided other features. I think this goes to show how cyclic tech can be. So, something like Samsung's invention here might have gained traction, as overcoming the slow PC ISA bus would have been a huge accelerator, kind of like where we are now.

> Could anyone enlighten me as to why to use Obsidian in one's daily life ?

My handwriting has degraded from consistent keyboard use over the last 30 years. Obisidan has replaced my paper notebooks, mostly because of this. However, it is handy to be able to mesh those notes with hyperlinks, LLM output snippets, quotes from other sources, embedded images, etc. Doing all of those other things would be laborious to impossible with paper.

This still happens with full shadow-casts and everything. Look around, and look to bigger cities if you're living somewhere out of the way. If there isn't a troupe near you that does this regularly, you may have more luck closer to Halloween.

Yikes. I've tried accupuncture. It _can_ work wonders for pain. But as a cure-all? Total quackery. Sorry your friend was approached like that in a time of need.

What's old is new again. We'll be buying cartridges for AI capabilities on future architectures.

> A small drawback is that just isn’t readily available on developer’s machines (unlike bash and make)

Looking back, this was usually a substantial stumbling block for adoption of new tooling. Things have changed. All one has to do is look at what JS programmers will go through to scratch build entire toolchains on the back of npm. IMO, the bar has been moved up to allow _some_ installation friction rather than none.

IMO, if the tool is a solid improvement and installation is a one-liner, use it and promote it loudly so it continues to get support.

Same here. This part got me:

> The whale itself has never been sighted: it has only been heard via hydrophones, but its call has been detected since the late 1980s in a pattern that matches the migration of the blue whale and the fin whale. Those species call at 10 to 39 Hz and 20 Hz respectively.

So not only lonely, but sings in a falsetto by whale standards; a weirdo. A lonely fellow with a distinctly high-pitched voice.

I was wondering about this. I wonder if there are insurance products to close this gap? Or maybe some banks offer accounts with different kinds of purchase protection.

I'm with you. While I'm no fan of the risk involved with missing a CC payment, there's a mountain of difference between credit and debit when it comes to fraud. It's literally you trying to get your money back (debit) versus some giant corporation trying to get _its_ money back (credit).

This is huge, thank you.

Since you're using HTMX, I have to ask: do you have any tips or idioms for composing complex forms and UI without things getting out of hand? I love the approach, but I'm having a bad time figuring out where the ideal balance is between too few or too many HTMX-replaced areas in a page. Thanks.

> I used fixed point math which optimized well.

I feel like the idea of fixed-point is under-utilized and very under appreciated. There are loads of applications where this is a better choice, let alone more performant.

Just a guess: if you want to scale a sprite at anything less than a whole ratio (e.g. 1.5, 0.7, etc), you have to choose pixels to drop out and pixels to repeat , on some pattern that looks good. There are going to be scaling ratios that look like a hot mess, especially at a low resolution like 320x240.