With you on this especially because somebody I know asked me to help change their oil and they hadn't even considered there being waste oil to dispose of
I will be trying this ASAP. With the locally hosted models I've run and Gemeni's free no-login results, I've found they love to put in everything the skill here tells it not to. Today one in Python put a lambda that has no arguments to call a function that takes no arguments instead of just passing the function. There's at least one linter that checks for that but still it's a lot of babysitting to get good code.
Just like how Linus from LTT (just trust me bro on the source) said one day he needed a tool (hammer?) so he walked into the hardware store, found what looked like a hammer, and bought it. End of journey. And then he finally realized how a regular person buys tech. Most people do not care, do not know they should care, and do not care enough to know if they should care enough.
I think I agree but currently it's analysis paralysis. Just had a huge repair bill come in for the car and to be blunt if I could supplement its daily wear and tear I'd appreciate it, so the fire under me is starting to get lit.
Yes for a few reasons: more components, more noise filtering needed for sensitive devices, and more design theory and analysis is needed. A linear supply is nothing more than a high current op-amp. A switching supply requires understanding currents in the time domain to choose or design the right inductor. It's just more.
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.
I think you've missed that all generators have upfront cost. That's why the monetary payoff time for installing solar is non-zero. Versus a backup generator you're paying 2-3x the cost upfront. And yes we know the running cost is almost 0, the maintenance is almost nothing, etc etc, but I could see that argument not holding as much water as we need it to.
Sadly worktrees do some stuff with the git folder that's made one development environment we inherited incompatible. Something about the .git folder not being a fully real .git folder maybe
Best I can tell they've taken down whatever it was, but most likely flux left some ways to get data out of their system that shouldn't have been and Adafruit leveraged that. Could have been in a good way like exposing false claims of architecture or security, or a bad way like revealing proprietary information on how the platform worked or looking at other peoples' projects (more than just seeing they could do that). If the blog doesn't come back up, I'll kinda assume they did something bad. I don't have sources but I've heard adafruit isn't the sweetest fruit in the tree...
My viewpoint has always been that if there's enough demand, it'll get built regardless of tax breaks. But once one place cracks even the tiniest bit, it all falls apart. Apes together strong.
Yes but there has to be a reason why the nightmare scenario existed. For example in the article it was because the author had hubris over 20+ years of the pump never failing. It's a good admission of cause. I certainly can't blame them for it. They also admit they didn't have a backup plan packed. It's a humble article if you see through all the anger. Your scenario was caused by trying to do the right thing and it was still wrong. Again, great reason. Was the other commenter exhausted and overslept before the trip? We don't know. Did somebody steal their supplies? Did they fall in a vat of toxic waste? All we know is that they were on a trip with no packed way to increase blood sugar and I think we all agree that's not the expected plan. But they also say they're usually very good at feeling their blood sugar and were bait-and-switched by the trip organizer, so it's not unreasonable to assume they assumed they could catch anything early and just go buy something. Which isn't really a plan, again as we learned from the article.
But it puts sizeable arrays on the stack. That's not really better since instead of an out of memory exception it'll just corrupt the stack of on the majority of embedded implementations that don't have hardware stack protection in use or available.
I think your experience on 8 bit is just fine. Imagine, if you will, that your 8 bit micro has 2 kB of RAM, such as the famous atmega328p of the Arduino UNO. Sure the compiler might put it into a register, but it might not. It most certainly won't put where later in the code they define 3 66 byte arrays on the stack, but that's maybe ok. The question is: how do you preallocate the stack safely? How do you know exactly what your usage is without overflowing the stack and wreaking havoc? Maybe you profile the code with debug on and it's X bytes, then in release mode it's Y because register packing. This effects all code, but it's something we need to be cognizant of when we're trying to maximize the 2 kB. It's easy to throw kilobytes of stack around on desktop. Megabytes even. I've done gigabytes before for quick and dirty stuff. But on deeply embedded 8 bits, you don't want to be doing that.
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.
This seems like a solved problem for those who care to solve it. Weigh product on intake, weigh on outflow or some other constant displacement pump solution. I've seen How It's Made and those factories have it down to a science without a guessbot at the wheel.
I've seen tofu go down in price in recent years. It's incredible. I think my local store is doing a block of extra firm for under $1.50? It used to be $2
2 things of notice in the readme as recently I've been in the efficient binary communication hunt:
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.
Even not a cancer treatment. Even if the original seller was an uber wealthy and healthy individual, if they can't get what's legally theirs without as little as "I want it back" (contract permitting, which I think here it does), that's a problem.
1) A bit of hyperbole on my part but consider that minimum wages and other worker benefits have worked like this for a long time. They tend to ramp up.
2) good. The more people who are in the city the more actual sales tax and other revenue is generated.
Probably the least complicated tax law. Increase taxes to increase revenue. Makes sense. Align valuations with reality while maintaining relatively constant absolute tax dollar amounts. Also makes sense. It's really not that hard.
^^^ when I tell people tangential to the field that the latest pi needs considerations of cooling solutions and a beefy power supply (no more just any old micro usb cable into any old usb port), they're astonished. It was a "microcontroller" you could program in Python with a friendly Linux environment and is now an expensive, power hungry, hot computer with a microcontroller hanging off of it
Think of it like this: telegraphs are the hot new thing. The more you send, the more modern and relevant your company. No more Pony Express. You can either have employees sending 1-2 a day. Or, 100 per day. Wow so advanced, so modern, invest now.
Ah. Good fact check. I swapped the numbers on minimum community service hours to graduate high school and this. But I think my point still stands that you can't just walk in and take the test
I very much do not believe them, but I don't have much to base that on other than that now there's a company doing a similar thing and projecting much longer timelines. So sadly I'd be joining you