However, they don't need the same heatsinking as linear supplies, so they're less expensive in that regard. If designing an optimal heatsink (which has the second order effect of determining what else around the part will heat up because of the regulator) is a lot of work, then maybe the NRE will be the same. But overall linear regulators are fewer and simpler components so the BoM cost is a lot lower.

1. Some Dutch homes seem to have X amps of service

2. Some of those want Y amps, where Y > X

3. That upgrade is taking time and the servicers are asking for patience

I don't see the link to solar?

My bigger point was that no malloc should be called "stack allocated" or some other more technically correct term. That tells me "hey if you run this code and something goes haywire, check your stack isn't corrupted" because 9 times out of ten for me that's the problem.

1. .text size without clarifying the architecture, flags, and compiler is meaningless unless it's all rodata (and it's not)

2. Saying it takes 0 .bss and .data just means it allocates everything elsewhere and that can be helpful to know. Of course in compilation that'll also be dependent on how and for what it's built. To say it's zero alloc is incorrect or at best misleading. Here's a line of code that allocates a ton of stuff on the stack: https://github.com/wolfSSL/wolfCOSE/blob/b90b34abcba90aa7b8a... (previously pointed to another line but it was diluting my thesis). Anyone in embedded who's had to increase stack size to use a fancy function knows what I'm talking about. I'm looking at you, sscanf. Some of this code will allocate hundreds if not low thousands of bytes onto the stack. Which is maybe fine but don't say it's zero alloc just because it's all on the stack.

2) good. The more people who are in the city the more actual sales tax and other revenue is generated.