> Yeah it would be pretty fucked up if the current administration pushed something that's bad for the US government but very good for some billionaires.
It's both parties--and it's been this way since the end of the cold war. There's no longer a need to say we're better than the alternative. The dems cancelled student debt--a gift to both debtors in the investor class. Harris's campaign trail housing push was also a gift to the investor class. And the Fed printed $9T while dems were in office.
My point was everything the dems do to help out the poor also has the side effect of helping out the investor class. They say they help out the poor, and they do, but they also keep the plutocrats plutocratic.
Loosening up zoning laws to allow for much greater supply of housing. Blue states don't do this because it would be bad for the investor class who's owns real estate.
In states where there are looser zoning laws and more housing is built, who invests in and profits more from the new construction, the investor class or the poor?
A "compiler" to solve the issues the library created, awesome. It doesn't solve many re-renders tho, as React re-render full components, not only the HTML/Text Nodes that changed.
Maybe somebody doesn't like me. My two most recent posts (3 months apart) were flagged. As far as flagged materials go, I find them both pretty much within bounds for HN.
Pretty much anything with Trump in the title is going to get flagged as this community really dislikes content that tends to devolve into a flamewar. It is a bit strange that your other post about MS AI data centers was flagged, though.
A use case where we reached for Clickhouse years ago at an old job was for streaming music royalty reporting. Days of runtime on our beefy MySQL cluster, minutes of runtime in a very naively optimized Clickhouse server. And sampling wasn't an option because rightholders like the exactly correct amount of money per stream instead of some approximation of the right amount of money :)
There's nothing Clickhouse does that other OLAP DBs can't do, but the killer feature for us was just how trivially easy it was to replicate InnoDB data into Clickhouse and get great general performance out of the box. It was a very accessible option for a bunch of Rails developers who were moonlighting as DBAs in a small company.
> I feel sorry for people with budget phones who now have to battle with these PoW systems and think LLM scrapers will win this one, with everyone else suffering a worse browsing experience.
I dunno. How much work do you really need in PoW systems to make the scrapers go after easier targets? My guess is not so much that you impair a human's UX. And if you do, then you have not fine-tuned your PoW algo, or you have very determined adversaries / scrapers.
As has been stated multiple times in this thread and basically any thread involving conversation on the topic, a PoW with a negligible cost (either of time/money/pain-in-the-ass factor) will not impact end users, but will affect LLM scrapers due to the scales involved.
The problem is trying to create a PoW that actually fits that model, is economical to implement, and can't easily be gamed.
But saying "any" seems to imply that it's a theoretical impossibility ("any machine that moves will encounter friction and lose energy to heat conversion, ergo perpetual motion machines are impossible"), when in fact it's a theoretical possibility, just not yet a practical reality.
It's both parties--and it's been this way since the end of the cold war. There's no longer a need to say we're better than the alternative. The dems cancelled student debt--a gift to both debtors in the investor class. Harris's campaign trail housing push was also a gift to the investor class. And the Fed printed $9T while dems were in office.
reply