I'm a car fan, so I'd rather reward drivers for optimal behaviors vs broad car-reductions. I'll probably turn out to be on the wrong side, but maybe we'll find a good compromise.
That being said, it's hard to fault them for trying to monetize some dimensions that are not well supplied by the public, and that companies work to acquire. Still, I agree, it's disappointing.
While default osm data is great, I've been very impressed with the partnership/collective of Overture Maps data. It's osm + esri/tomtom + corporate processing/funding.
Every time I read a piece from Nieman, it reminds me both of how much we've lost in journalism, but also that there's always hope to swing the pendulum back towards truth (well, more truthiness).
Very handy. My math education would have gone much better if my notes weren't full of "lambda is the half stickman; sigma is upside down Q or broken E" and other really silly things
Interesting that it's not a direct "you should" but an omniscient 3rd person perspective "Claude should".
Also full of "can" and "should" phrases: feels both passive and subjunctive as wishes, vs strict commands (I guess these are better termed “modals”, but not an expert)
With some of the newest 3.x changes like copy-on-write, I find pandas getting quite verbose now as well.
In a world where AI is writing the code, I guess I shouldn't complain, but when I am discovering something the ai of choice yet again missed, both pandas and polars still feel verbose and lacking sugar.
Much like X, it's what you choose to use it for. Papers are posted, approaches are debated, and loose groups form to align. It's easy to scroll past the pandering, but there is useful stuff in the dross.
But agreed, it is getting harder and harder to dig to the gems.
I find this court response confusing, but an alt pov: Amazon wants to block _other people_ from using my ID (say, to watch prime video or access prime shipping or discounts). They can extend that logic to suggest that an "agent", with agency, is the same issue: it's just "another person".
And we've seen the continual push against "Bots" who act without agency, but are seen to abuse systems as they act as "more than a person".
But I think we'll see the usual outcome: the barrier has to be upheld, so the folks behind the barrier can exert a toll on access.
> If joins are necessary, we learned to consider breaking down the query and move complex join logic to the application layer instead.
We often try to leverage the power of the DB to optimize joins on our behalf to avoid having to create them. At a certain point, I guess you wind up having to pull this back to your layer to optimize "the one job" of the database.
I jest, but only slightly. We don't just want to persist data, but link it for different purposes, the "relational" part of RDBMS. Good to know there's still room to grow here, for PostgreSQL and the DB industry.