5,416 karma · joined January 21, 2012
meet.hn/city/us-New-York
Socials: - x.com/pradnelluru
---
This article is closer to category b. But the category a ones are most useful, because they dispel myths one is likely to encounter in real, practical settings. Good examples of category a articles are those about names, times, and addresses.
The distinction is between false knowledge and unknown unknowns, to put it somewhat crudely.
Is that something Akka / RX offer? My quick thought is that they structure code in one binary.
You’re being quite negative about a well-researched article full of info most have never seen. It’s not a crime to write up details that don’t generally affect most people.
A more generous take would be that this article is of primarily historical interest.
ChatGPT is still vastly more popular than other, similar chat bots.
Where is the evidence for this?
a) are fast: they certainly incur the same network cost of a regular request. But more than that, all they do is read two counters, so they're super quick for backends to serve.
b) cheap: they don't do nearly as much work as a "real" request, so the cost of enabling this system is not prohibitive. They simply return two numbers. The probes don't compete with "real" requests for resources.
c) give the load balancer useful information: among all the metrics they could have returned from the backend, the ones they chose led to good prediction outcomes.
One could imagine playing with the metrics used, even using ML to select the best ones, and to adapt them dynamically based on workload and time period.
The more requests you have, the higher the chance one of them hits a tail. So the overall latency a user sees is largely dependent on a) number of requests b) tail latency of each event.
This method improves the tail latency for ALL supported services, in a generic way. That's multiplicative impact across all services, from a user perspective.
Presumably, the number of requests is harder to reduce if they're all required for the business.
It's in everyone's interest for the company to be a sustainable business.
For a few months, it was possible to feel the incredible simultaneity and richness of human lives. Someone biking, another person cooking. Day in one place, night in another place.
It was ahead of its time. And too expensive for Twitter to keep running for too long. But it was a precursor to today's Snapschat's map view and Instagram live streams.
I think we're going to see even fewer site visits as a consequence of AI search engines. The internet's ad-based funding model is going to dry up further, but the impact will be disproportionate. It'll be a few years til we see where the cards land.
There will always be a long tail of niche Windows games (retro + indie especially). But you can capture the Fortnite (evergreen) / Dragon Age (new AAA) audience.
I do find myself running into Claude limits with moderate use. It's been so helpful, saving me hours of debugging some errors w/ OSS products. Totally worth $20/mo.
On the other hand, as long as its actually advancing the Pareto frontier of capability, re-using the same name means everyone gets an upgrade with no switching costs.
Though, all said, Claude still seems to be somewhat of an insider secret. "ChatGPT" has something like 20x the Google traffic of "Claude" or "Anthropic".
https://trends.google.com/trends/explore?date=now%201-d&geo=...
There's always the fear of losing stuff when you're moving objects around so much, too. One less thing to worry about.
The top chart shows which of the three bodies escapes the system given initial starting conditions. The bottom one makes it easier to see patterns by reducing noise. It uses the k-nearest-neighbors algorithm to find the dominant color near each pixel. More than the large pools of stability, what's interesting are the bands of stability - like electromagnetic fields.
I have no idea how one codes this up in a computer, with fixed precision math and all. Numerical methods is a black box for me.
[1]: https://doi.org/10.1051/0004-6361/202449862 [2]: https://www.aanda.org/articles/aa/full_html/2024/09/aa49862-...
I guess much of this is why its hard to use shared libraries in the first place.
I don't know which OSs do this, but I know hypervisors certainly do this across multiple VMs.
In theory, you could extend torrent clients to support archiving some subset of the files. You just tell it to keep around 100 GB of files in a 10 TB torrent. Since the client knows the status of each chunk in the swarm, it can make smart decisions about which chunks to download and seed. Clients already let to set preferences to seed the "least-seeded" chunks. So this isn't so far fetched.
The big problem with this is that it lets you work only with a fixed archive. Torrent files can't be mutated after they are created. So you'd be able to get people to archive a fixed version of a shadow library, but not an evolving one.
In practice, this should be fine enough. If we had high assurance that all the books added to the library before 2022 (or something) were copied in 50 machines, that's quite useful.
Being able to layer deltas on top would be amazing - you could evolve the collection as new books are added.