For the people in the comments stating that this is just fluff for voters, that may be true. But consider that this memo has another target audience: Investors, Banks, and VCs.
I know that many people in those spaces are investing in AI precisely because they believe that should their AI investments fail, the industry will be bailed out by the federal government. Getting AI to be seen favorably by the administration and putting AI within civic government systems and inside defense contracts is a pretty big push towards that outcome.
The CFTC, since Trump, has become entirely corrupt. Note that the proliferation of sports gambling in prediction markets, which is explicitly illegal, largely exists because the CFTC refuses to enforce their own legal mandate against Kalshi and Polymarket.
It’s actually worse; when states try to shut down sports betting in prediction markets, the CFTC fights on behalf of Kalshi with the reasoning that only the federal government has the mandate to regular futures and prediction markets. And then they refuse to regulate!
The CFTC is supposed to have 5 chairs, with no more than 3 in the same party. The administration has gotten around this rule by simply removing 4 of the commissioners and then refusing to appoint replacements. In effect, the CFTC has only 1 republican chair and no opposite party representation. The level of corruption is staggering.
> sports gambling in prediction markets, which is explicitly illegal
It’s a bit more complicated than that. The CFTC argues that under Dodd-Frank any bet on a future event that can have economic consequences is regulated by the CFTC.
It’s a bit silly because this obviously wasn’t the intention of the legislation, and it would also mean anyone betting outside a CFTC regulated exchange is in illegality. But it’s valid enough that The case will probably go to the Supreme Court.
> The CFTC is supposed to have 5 chairs, with no more than 3 in the same party.
Of course it's a policy that helps the two-party system become further entrenched. It should be no more than 2 from the same party. (Not that it matters given the fact only one is appointed, but still.)
It’s actually really easy to make models that can predict “will the market move up or down in the next X microseconds” that score above 50% accuracy. It’s just that there are so many ways to do it that overfitting is practically guaranteed and most models don’t work when actually trading against the market, which reacts to you. Doing those trades well requires more understanding of the underlying mechanisms, not to mention access to data sources that the public simply doesn’t have.
The decision to default to the streaming engine is really interesting. My intuition is that this would be slower than other data frame operations that are more parallelizable with batch processing, because streaming engines necessarily process rows sequentially. Is my intuition off/am I overestimating how much auto-parallelization polars does?
Streaming here has a different meaning than perhaps what you're used to. It's not referring to online processing where you maintain aggregates/state while an endless stream of data comes in.
The name was chosen early on to contrast with the old execution model, which was essentially all-data-in-memory, column-at-a-time. That engine still exists, we use it as a fallback mechanism for things that aren't supported yet in the new engine (or if you explicitly ask for `engine="in-memory"`).
The new execution model first constructs a computational graph of nodes which communicate in streams of in-cache batches (morsels) of data, meaning the full dataset will never be held in memory if not necessary. This was called the streaming engine for that reason in an early prototype and the name stuck. In hindsight I do admit the naming choice is somewhat confusing.
Well... once my recent work on out-of-core lands the batch could be on disk when we run out of memory budget ;)
But no, that's not what I meant. I meant that the batch is meant to be of a size that fits in your CPU cache. This can be a huge throughput improvement as each bit of data stays in cache as it moves from data source to sink.
Compare this to column-at-a-time execution: by the time you start the next operation on this column the start of the column will be out of cache again, meaning you operate at RAM speed (or worse, disk speed) rather than cache speed.
I think you’ll also find that the best way to strongly pressure companies to do something is by law. The work that Right to Repair advocates have been doing across the industry is fantastic.
It was (my) main takeaway and I wanted it to be evident in the headline. I didn’t want to bury the lede; I’ll uneditorialize it because it seems it’s causing some fighting in the comments and I don’t really want to instigate anything, more just warn people using the distro. I don’t think it’ll reach the people who need to be warned if it’s not evident that there’s an issue from the start.
Appreciate it! Editorialised is fine but the post is mostly about the development practices leading to bugs & the lack of awareness of how dangerous that is, not about the current absolute number of security holes if that makes sense.
I know that many people in those spaces are investing in AI precisely because they believe that should their AI investments fail, the industry will be bailed out by the federal government. Getting AI to be seen favorably by the administration and putting AI within civic government systems and inside defense contracts is a pretty big push towards that outcome.