It is "artificial" in the sense that the price is set well below the natural clearing price based on available supply and demand.
HN user
cannonpalms
I guess, in theory, the prior distribution of language would allow for improved performance in some cases, especially where input quality is low.
Is this the kind of thing that retractions are typically issued for, or would it simply be your responsibility to submit a new paper correcting the record? I don't know how these things work. Thanks.
Just a quick shortcut
The canonical solution in this space so far is https://github.com/Dicklesworthstone/agentic_coding_flywheel..., and I would bet that this tool is just a paid version of the same, or worse, just a paid wrapper
Just don't open a comment with
You're absolutely right!
And you're good
I believe this was the original thread.
Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API) | https://news.ycombinator.com/item?id=46661308
I doubt the equities analysts would appreciate this as much as a tech nerd would. It'd be seen as a step backwards and evidence of having no clue which way the world is heading.
So long as (fast/optimal) real-time access to new data is not a concern, you can introduce compaction to solve both problems.
You left behind a script clearly written by your LLM tool that patched some problems in your code. It's undeniable.
I'm all for using the tools available, but I don't understand lying about it.
https://github.com/whispem/minikv/blob/main/fix_ci_complete....
You're absolutely right(em dash)
Hilarious
Those whiteboarding sessions and discussions used to serve as useful opportunities for context building. Where will that context be built within the cycle now? During a production incident?
This is just a layer of emotion on top of raw capitalism. And it will always prove to be a lie when push comes to shove.
Time-to-market favors chromium. It's also by far the most commonly used engine for headless browsing, creating lots of useful prior art.
Google's AI overview regularly hallucinates or gets the answer wrong. Obviously if you're going to run inference on every search from billions of users, it has to be a very cheap model.
You can already do what you're looking for by reading the browser cache as new data is cached. This would allow you to see the site as it was loaded originally, instead of simply fetching an updated view from a URL. The data layout for the cache in Firefox and Chrome is available online.
The unfortunate reality is that, depending on your personal preferences, "most modern games" require such a ring 0 anti-cheat. Any game that has a matchmaking mode with a competitive option requires a rootkit.
As an aside, I recently found Riot Games' Vanguard installed on my Linux ESP partition... after having installed the game on my windows partition. It rooted every OS it could find mounted. Incredible.
I've found the latency of /compact makes it unusable. Perhaps this is just the result of my waiting until I have 0% context remaining.
Fun fact, a large chunk of context is reserved for compaction. When you are shown that you have "0% context remaining," it's actually like 30% remaining that's reserved for compaction.
And yet, for some reason I feel like 50% of the time, compaction fails because it runs out of context or hits (non-rate) API limits.
I wonder how well a sentence or two in CLAUDE.md, saying to search the local project for examples of similar use cases or use of internal libraries, would work.
CC uses very little system resources.
The insert function is very unidiomatic. Instead of defining a cmp closure, you would typically implement Ord and friends.
TIL of `docker commit`. What is the use case for this command? Quick debugging or something, to share with a coworker?
The field is nascent. The bar is not static.
For standard signals--no, but for real-time signals, yes. The latter are still a portability issue, though.
Can you provide more information (or links) about that billing model you describe?
The incentive structure behind paying by the search has diminishing returns, as I see it. You need the results to be of a high enough quality to drive the user to want to run another search with you. Beyond that point, though, in the absence of a direct competitor, where is the incentive for you to continue improving search result quality? M
It would probably hurt more than help, by way of retention metrics.
You mean the substrate of our entire economic engine? I think that's a bit dramatic.
why publish this?
New versions of Akira and any other ransomware are constantly being developed. This code is specific to a certain version of the malware.
As noted in the article, it also requires:
1. An extremely capable sysadmin 2. A bunch of GPU capacity 3. That the timestamps be brute-forced separately
So it's not exactly a turn-key defeat of Akira.
It sounds like a Staff title may be in play, although it wasn't made clear whether this would be a promotion.
Restricting config to static values removes quite a bit of the value of config, in my opinion.
Yes, logic should live in code, but very often that logic needs to behave differently depending on some piece of (inherently variable, not static) configuration.
Random examples (written from the perspective of personified code): - How many threads should I use? - On which port should I serve metrics? - Which retry strategy should I use?