Increasingly flake.nix is present in good repos. Zillions of packages are available. But yes, you will need to learn and sometimes File System Hierarchy assumptions need to be worked around. The rewards however, dominate the (few) inconveniences once you know your way around.
The funny thing is that textbook economics has all of the answers about why laissez-faire market economics doesn't work as a foundation for economic policy. It's almost as if it's never been about making good policy and always about doing whatever is best for big businesses and the small number of wealthy people who stand to gain the most from minimizing consumer surplus.
totally. In fact the current monopoly-coddling dispensation is antithetical to market economics, which clearly espouses real competition. It's kinda been coopted and hijacked.
The periscope style vector CRTs use in the arcade Battlezone were a claustrophobia and panic-inducing experience. Glowy unpixellated 3d, narrow field of vision. Unforgettably cool.
With a new agentic-lashup tearing across the internet every week, pointing the way to "gradient descent" software development, any purchasing manager worth their salt is going to ask some serious questions about their enormous SaaS bill before committing to another expensive long term contract. It follows that valuations must decline. Even if only because risks to moats have increased, but also because it makes sense to negotiate hard on pricing when there's fear in your counterparty.
Preposterous. Have you ever worked for a company as a programmer or for that matter as a manager? They don't just replace products ad hoc. There's an enormous amount of due diligence that goes into any new software product - making sure it fits the company, that it's secure, that it works properly... I recently worked at a small startup who spent on sales force @ $100,000 a year. I said you know what we could do this ourselves and you know what they said as every company I've ever said that to says? "We don't want to support it. We need to cover our ass. Everybody knows how to use this"
Personally I find it extremely rare that I need to do this given Polars expressions are so comprehensive, including when.then.otherwise when all else fails.
That one has a bit more friction than pandas because the return schema requirement -- pandas let's you get away with this bad practice.
It also does batches when you declare scalar outputs, but you can't control the batch size, which usually isn't an issue, but I've run into situations where it is.
because method chaining in Polars is much more composable and ergonomic than SQL once the pipeline gets complex which makes it superior in an exploratory "data wrangling" environment.
reply