B Corps allow the board to weigh things besides shareholder value. That's a meaningful distinction.
The idea is that shareholder primacy isn't compatible with everything every corporation wants to do, so having a board that's protected from lawsuits when they put things above shareholders is a useful thing and B Corps offer that.
The board can, for example, reject a "superior" takeover bid without fear of lawsuits from shareholders pissed off they didn't get the biggest payday available. A typical C Corp's board MUST take the highest offer, and not doing so WILL get them sued. That means if GoodGuy B Corp is about to be taken over by BadGuy Inc., the GoodGuy board can say "No, they're not compatible with the public benefit mission we incorporated under so we're not going to accept their offer." That's actually really useful.
No GoodGuy B Corp would still need to fear lawsuits in that situation and PBC or not they would be able rejecting that decision. If they get sued there is a good chance they can defend the decision.
Listen I bought six Retina displays, I don't also have money for a new Mac. Of course I'm going to complain about the lack of Thunderbolt daisy chaining after my frivolous expenses come home to roost.
Even the slower ones are more like a Wii U, which is perfectly capable of everything a set-top box needs to do. Really, the hardware acceleration does all of the heavy lifting, and the processor only needs to render text and coordinate what to composite.
It's the bloat of the software layer on top that's slowing things down.
A 1st-generation Chromecast only has 512 MB pf RAM and a dual-core 1.2 GHz processor, and it can handle video streaming just fine. Building an interface on top of that doesn't take a lot of resources, if the underlying layers aren't bloated. With current Android/iOS development, they very much are.
Yes this is a waste of time. It’s actually a hard engineering problem! There are very few engineers who build for TV compared to desktop or mobile. The challenges are totally different. There are still some good human-written articles out there.
From Claude docs: Planning is most useful when you’re uncertain about the approach, when the change modifies multiple files, or when you’re unfamiliar with the code being modified. If this isn't true, skip the plan.
reply