But in any given year I maybe plant a dozen new plants tops. 6 tomato plants and half a dozen other random things.

Old water pipes have been the financial downfall of many suburbs.

Odds are you don't have a lot of heavy fright coming through, so your roads don't need constant replacing. You likely don't have bridges that carry heavy freight, those are a maintenance nightmare.

But once all the buried pipes need replacing, suddenly all the roads need tearing up, and that is expensive.

Sure there is some embedded JS in there as well but ignore that and JSX is thr XHTML comeback story.

Even countries like China have built lots of new car first infrastructure.

Maybe in smaller cities, but I haven't hit a major city on my travels for some time now that wasn't digital payment first.

I also travel a lot and have visited many places where walking around is just not possible.

Cash is dead in many places. Stores all around me have "cash not accepted" signs.

For many Americans walking is dead. Sad but true. Cities got designed or redesigned to be car first.

Amazon put numerous types of stores out of business. There are entire categories of products that can now only be bought online.

A recent update crashed in the middle and left me running an incorrect kernel for my GPU drivers, if I had of rebooted I'd have been hosed. Thankfully Claude caught it before that happened (steam games refused to run) and fixed me up.

In related news - not a fan of flat pack.

Building simple guns out of pipes never was hard. Jury is still out if it is more or less work than getting a 3d printer working.

When the initial Muse launch happened, my first reaction was "wow this sounds familiar."

Now the HW side of things is announced.

To be fair, this is all obvious stuff that should be done. The key is who can pull it off. It has been pointed out many types that technically Muse is nothing new, some combination of Gemini products can already do it. The counterpoint being that packaging and branding make a product.

I am kind of sad that desktop computer use ended up being the way to go instead of hooking into mobile phones. Mobile phones allow for a lot more potential integrations with day to day life, plenty of services now days are (sadly) only available through a mobile app.

Meta was genius in coming up with a new name and offering Muse for free to start. They can upsell you once you see the value. Meanwhile I have 3 existing Google subscriptions to different services and from what I can tell, paying for one of the all in one subscriptions that includes Gemini would cost me a lot more.

My random blog was highly ranked for a fair number of technical topics.

Heck it has proactively asked me if I wanted it to tear apart APKs that remote control some HW I have.

People working on cortex m series chips still static alloc though. :D

Them and game programmers. Also the HFT people from my understanding.

The latter two are due to latency concerns.

Still though, it is something that I think more engineers should try out once or twice. Thinking about how buffers actually need to be is a useful exercise.

The tldr is you had to preallocate a struct with anything you wanted captured ahead of time.

Dynamic memory management is a performance enhancement. It lets you more efficiently utilize memory vs static allocation at the cost of, well, lots of types of bugs.

You can always preallocate MAX_NUM_ELEMENTS * SIZE_OF_OBJECT for all your arrays. If someone tries to send you more objects then you have buffer space for you just reject the request.

Latency sensitive programs already do this, since memory allocation is rarely deterministic (although it can be in .NET and other similar languages). Likewise a bunch of destructors going off when an object is freed in C++ also takes a, practically, non-deterministic amount of time. (Really well profiles and controlled programs can make this deterministic if allocation patterns are always identical, but that is rarely the case.)

Of course having fixed sized buffers means you have to have protocols that are aware of size limitations. Most protocols now days assume infinite memory. Everything just fails, badly, when memory does run out.

After having worked in embedded for awhile I grew to deeply appreciate planning around memory limits. Really everyone should be doing it but almost nobody is.

It isn't some new idea, he just didn't follow all the rules doing it!

As a brief reminder to readers at home, in a theoretically perfect free market, profit trends towards 0 as competition increases.