debazel
debazel on Hacker News
Because joining group A means you will soon be out of a job once group B out competes group A.
The side effect of this is also that the value of software itself has never been lower, so starting a new software business isn't very attractive in today's market.
If you did that you would also have to provide the timestamp every time you wanted to look up an ID, and now we're back to UUIDv7 again.
It doesn’t have anything to do with indexing more than one thing.
The issue with truly random IDs is that inserts are scattered throughout the B-tree index, which cause page splits, fragmentation, and poor cache locality. Using a timestamp prefix makes new IDs sequential, so inserts tend to land near the end of the index, which avoid all the B-tree trashing and improve write performance.
Sanctions force them to treat you terrible, it is the intended effect of sanctions.
Look at the fuel cap, the green part of the front wheel, or the vertical frame split behind the fuel cap. AVIF smooth the details out too much.
Why do you think YubiKey would be an allowed option? Sites will require Google/Apple password manager and use this as a proxy to prevent bot accounts.
What do you do when Apple ban your Apple account?
> any tool that becomes more powerful tends to become more specialised and expensive to operate,
Isn't that exactly what is different about AI automation? AI is more generalized and cheaper to operate.
Any time big corp implements strong sandboxing they'll inevitably put the user inside of the sandbox.
If AI continues to improve at the current rate for 40 years then there is unlikely to be such a thing as a career.
Manual labor and trades is likely to be one of the last things to go, so the whole "dropout of school and go into trades" crowd may have been more correct than ever, though their original reasoning was not.
You can’t really do that with PNG today either, because of all the PNG optimizers that quantize images before encoding them to PNG for better compression.
> They definitely play them to connect with others who play the same game.
Once anyone can generate any game, movie, or artwork they can imagine with a simple prompt, this shared experience will disappear along with it. The amount of content available will fragment the space so much we'll eventually lose the shared experience and novelty that brings enjoyment and fulfillment from these activities in the first place.
Pointless comparison as you the user still have full control over all of that on Linux.
Yes, but what I'm saying is that it is much easier to put a limit on the read_file tool or the http tool rather than sandboxing your whole environment.
You only really need to sandbox when you provide access to tools that are almost impossible to filter correctly, such as a bash tool or a tool for arbitrary code execution.
It is really easy to restrict and contain an AI agent as long as you don't give it access to a terminal. If you only give it tools to read files and access the internet, then it is much easier to just restrict the tools themselves rather than setting up a whole isolated sandbox.
ARC's harness is just straight up broken. No serious harness removes reasoning context between each step. Not only does this significantly lower performance over all reasoning LLMs, but it also increase cost as you destroy the cache on every turn. Tossing the oldest entry when context fills up instead of using compaction is equally bad with the same issues.
Not possible, says phone number is invalid.
Is it really anymore dangerous than having minimum wage workers serving as fall guys for approving prompts they have no understanding over?
It did it during the installation process.
And that's not a joke, I made the mistake of installing this on my Windows machine just to test it out quickly last week.
It created 2 new users and then assigned new NTFS permissions for every single file under my user directory to them. This of course wrecked havoc, ssh refused to work, several applications refusing to start and a ton of permission errors. It did this without even a warning in the background and it also does not undo any of it when you uninstall it.
It took around 3 hours to fix it by updating ~10 million NTFS permissions for every single file under my user directory.
We're not that far off. But it will not just be for AI, but all software. Mobile OSes has already normalized the expectation that you don't control what can run on your own devices.
I'm far from an image rendering expert myself, but I don't think there is a single root cause here. I don't doubt the partial decoding would affect the final result just as the scaling algorithm itself, so in the end it's going to be a combination of it all.
The reason I believe the scaling algorithm is contributing more in your particular example, is because it looks almost exactly like a classic B/W comparison between a sharp ringing heavy algorithm and a more blurry one.
For reference here is a quick comparison between Lanczos/Bilinear I threw together: https://twinlens.app/compare?share=40973d84a174
It would be interesting to see how your example would look if you used colors instead, where the ringing artifacts become a lot more obvious. Like this one: https://twinlens.app/compare?share=8fb890a5820e
Chrome and Firefox uses two different scaling algorithms that is probably contributing a lot more to this difference. Chrome is more blurry in general while Firefox is sharper but has slightly more ringing artifacts. Personally I prefer the Firefox version.
Why is it replacing true/false with T/F? true/false is already 1 token in all tokenizer I've seen. Even worse is replacing null with ∅. ∅ is a special unicode symbol that takes up 2 tokens compared to the 1 token for null...
On Windows over allocating virtual memory (commit charge) is still bad. Unlike on Linux, once the total commit charge hits your physical RAM limit + SWAP limit, Windows will start crashing your applications and refuse to allocate more virtual memory, even if that memory has not been touched yet.
This is also why it is very important to have plenty of SWAP space on Windows, even if you have 64 GiB+ of memory. Because applications love to over allocate commit charge.
I've been using this DeepSeek model the whole day today after building with 5.6 Luna extensively over the last week and I would disagree, at least for Rust + OpenGL.
DeepSeek just spend almost 2 hours trying to figure out why terrain textures were not working. It tried everything over and over again, it even had reference code for meshes on how to setup the rendering with materials, and it could just not do it.
I finally gave up and gave it to GPT-5.6 Luna instead, and figure out in a single prompt after 20 seconds, that the terrain mesh was being initialized with None in the material slot.
Other tasks it has managed to figure out at least, but it is significantly slower than GPT-5.6 Luna and it requires a lot more iterations.
(Both were set to high reasoning)
Users complained that we were non-compliant with EU regulations due to the missing cookie banner.
Because of the legal wording of these support tickets, the support team would often raise them to dev or legal as well, and since this is a non-revenue driving part of our business (the reason we don't track in the first place) we decided to just put up a cookie banner explaining why we don't need a cookie banner.
One of our sites that don't use any kind of tracking or cookies other then a site preference cookie, got so many complaints that we had to put up a cookie banner that simply says "we do not use any tracking cookies"...