HN user
I've been impressed by ollama running locally for my work, involving grouping short text snippets by semantic meaning, using embeddings, as well as summarization tasks. Depending on your needs, a local GPU can sometimes beat the cloud. (I get no failures and consistent response times with no extra bill.) Obviously YMMV, and not ideal for scaling up unless you love hardware.
The trick is to already know how to use regexes to make searching the manpages easier! But you really have to nail down the rules for escaping when you want to search for perl's gnarliest sigil magic.
Clearly the US needs a constitutional amendment to preserve the right to keep and bear AI tools. Then we can arm the victims of AI tools with their own AI tools, for self-defense. If we're lucky, AI will send its AI thoughts and AI prayers in carefully calculated quantities.
The article is well-written and I even learned a few things. I'm glad for Nikhil's persistence troubleshooting it and fixing the bug upstream. Thanks, Nikhil!
Training computers on human stupidity has got to be infinitely scalable, by induction.
If only they passed the inverse law requiring gas and coal plants to buy renewable power to reduce their pollution impact. This raises the question, why should a power generator be required to purchase external power? Isn't that the job of the grid operator, not the generation companies? It sounds like the state grid operator is trying to put their own burden onto renewable generators, rather than manage their portfolio directly. Who actually is responsible for balancing the grid? The state? ERCOT? Individual generators? Nobody? How does this compare to other grids?
What is the minimum resident RAM size per individual active unique series? Or what's a typical RSS RAM size for 10 or 100 million unique active series? How does unlimited cardinality avoid RAM exhaustion in this version?
absolutely true. imagine porting a decade or more of code for only the promised benefit of a more "pure" language. asyncio is nice, but excluding it and enhanced generator syntax from 2.7+ is >policy<, not engineering. python 3 is bootheel style top-down engineering >management<, not good engineering. The BFDL is fallible. Placeholder looks like a great Python 2.8+ to me. Runs all my old code and gives me new syntax, without rejiggering the stdlib for purity's sake? Twist my arm.
embed a cpython interpreter into the Go runtime as an embedded interpreter?
sorted() is widely used, adding will extend coverage considerably.