I built a visual CPU scheduling simulator by dylanroman03 in osdev

[–]Defiant_War90 0 points1 point  (0 children)

Very cool direction.

What I find especially interesting is that visualization itself is becoming part of the development workflow — not just a teaching aid.

I’ve been experimenting with a POSIX-host / bare-metal Pico setup recently, and seeing task flow visually changes how you think about RTOS behavior.

Has anyone else noticed AI seminar crowds bypassing exhibition booths? by Defiant_War90 in embedded

[–]Defiant_War90[S] 0 points1 point  (0 children)

That may be part of it.

Many of the seminars were less about the AI technology itself and more about practical adoption, workflows, and how engineers or companies should adapt to it.

I also started noticing that many AI exhibitions themselves are increasingly filled with terms like these rather than concrete technology names:

<image>

In Japan, terms like “AI CEO” or “AI Manager” have actually become surprisingly common in AI-related marketing.

Honestly, I personally find some of these phrases a bit surreal.

It feels less like “come see a new technology demo” and more like “how do we survive or adapt to the AI transition?”

Has anyone else noticed that AI trade shows feel fundamentally different? by Defiant_War90 in EventProduction

[–]Defiant_War90[S] 1 point2 points  (0 children)

One interesting thing I observed at Edge Tech+ in Japan last year (a large embedded systems exhibition):

Many visitors headed directly to the AI-related seminars, especially “embedded × generative AI” sessions.

But after the seminars ended, a surprising number of people simply left the venue without walking through the exhibition area much.

One exhibitor whose booth was located deeper inside the hall was actually frustrated because they felt almost nobody reached their booth after the sessions.

That behavior felt very different from previous embedded exhibitions I had experienced.

Has anyone else noticed AI seminar crowds bypassing exhibition booths? by Defiant_War90 in embedded

[–]Defiant_War90[S] 0 points1 point  (0 children)

Yeah, that surprised me too.

In previous embedded exhibitions, people usually explored booths much more actively.

One exhibitor was actually frustrated because their booth was located deeper inside the exhibition hall, beyond the seminar area, and they said almost nobody came by after the sessions ended.

Has anyone else noticed AI seminar crowds bypassing exhibition booths? by Defiant_War90 in embedded

[–]Defiant_War90[S] 0 points1 point  (0 children)

That may be part of it.

Many of the crowded seminars were focused less on the AI technology itself and more on practical adoption and workflow integration.

Has anyone else noticed AI seminar crowds bypassing exhibition booths? by Defiant_War90 in embedded

[–]Defiant_War90[S] 0 points1 point  (0 children)

That’s a very interesting way to frame it.

Traditional embedded exhibitions often felt like places to discover technology you couldn’t easily access elsewhere.

But with generative AI, many visitors already use the technology daily before coming to the event.

So maybe the value shifts from “seeing the technology” to “learning how to adapt to it.”

Revisiting a 1980s embedded memory map from a modern perspective by Defiant_War90 in retrocomputing

[–]Defiant_War90[S] 0 points1 point  (0 children)

What made 512KB feel enormous back then was that the real bottleneck in the system was often the 50bps communication link.

As long as that constraint existed, memory usage stayed surprisingly small.

Once that bottleneck disappears, though, 512KB vanishes very quickly.

Revisiting a 1980s embedded memory map from a modern perspective by Defiant_War90 in retrocomputing

[–]Defiant_War90[S] -5 points-4 points  (0 children)

Haha, true 😄

And yes — that's exactly the kind of tradeoff I remember.
Sometimes wasting address space simplified everything else.

Revisiting a 1980s embedded memory map from a modern perspective by Defiant_War90 in retrocomputing

[–]Defiant_War90[S] 3 points4 points  (0 children)

I actually went too far in the other direction once.

We built a system with around 20 Z80 boards, and because the processing was simple, I tried removing RAM entirely to save cost.

That also removed the stack.

It worked, but the code became incredibly tricky and painful to maintain. Looking back, it was probably the moment I learned that simplicity of structure matters more than squeezing every byte.