fancyfredbot
Joined 9 years ago
Joined 9 years ago
What is easier to change than people's opinions, is the two party political system which tends to resolve such questions to one of the two extremes based on one side achieving a tiny majority, rather than to the average which is usually a lot more sensible.
Realistically they need to 3x their revenue to pay for their compute. While that's plausible, I'm not convinced that it can all come from developers. Many many developers are already using Claude. I think they need consumer, or some other market too.
It didn't even occur to me that it was saying republicans and democrats are the same. That's just ridiculous ;-)
Edit: To clarify there's good evidence that people overestimate the degree to which people on the other side of the political divide hold extreme views by about a factor of two. We genuinely are less different than we think. It's not necessary for people to be the same for this to be true.
To be fair tether hasn't actually lost billions of dollars yet, whereas banks absolutely have. Overall though I don't feel inclined to trust most stable coins. The cryptography protects your virtual currency but the governance is what protects the assets backing them, and the governance looks weak.
The spec on your GitHub says: "Two simultaneously-live resizable values never share a stack."
So I surely can't have a dynamic array of dynamic arrays share a single stack? That's an unbounded number of resizeable values sharing a stack?
You could make it work on a single stack but that would involve having non-contiguous memory for each inner array since you can add to any array in any order.
The spec implies that we need one stack per element of the outer dynamic array which would let you have contiguous memory for each inner array, but you wouldn't know how many stacks you needed at compile time.
I'm a bit confused about how you could decide the number of stacks at compile time. I can see you could see how many arrays are lexically in scope. However if the code puts one dynamic array inside another dynamic array I can get to an unbounded number of total stacks without ever needing more than two in lexical scope at once. Do you also add stacks at runtime? Like a stack of stacks?
How are you deciding how many stacks to use?